aater.ai · Frequently Asked Questions
How the observatory works.
Common questions about aater.ai, the Participation State Standard, Pulse telemetry, and AI content classification.
About aater.ai
- What is aater.ai?
- aater.ai is an observability layer for understanding how publicly accessible content may be processed, extracted, and classified by AI systems. It derives structural participation states from observable signals including accessibility, extraction depth, rendering behaviour, attribution signals, and telemetry patterns. aater.ai does not optimise content for rankings or guarantee visibility in external systems.
- What does aater.ai measure?
- aater.ai measures whether publicly accessible content may be reachable by automated systems, may be structurally extractable, may support attribution and citation, may resolve into stable participation states, and may expose structural rendering gaps or observable AI-agent interaction patterns. The system derives classifications from observable technical and structural signals.
- Is aater.ai an SEO tool?
- No. aater.ai does not focus on search rankings, keyword optimisation, backlink analysis, or traditional SEO workflows. The system observes structural participation signals associated with AI retrieval, extraction, attribution, and automated content processing. These are different systems with different requirements.
- How is aater.ai different from AEO (AI Engine Optimisation)?
- aater.ai does not position itself as an AI optimisation platform. The system is designed around observability, structural derivation, telemetry, and participation-state analysis. Rather than attempting to manipulate external AI systems, aater.ai focuses on understanding observable structural conditions associated with automated processing.
- Why does the language on aater.ai sound different from most SaaS platforms?
- Because the platform is designed around observability infrastructure rather than marketing optimisation. The system attempts to describe structural conditions, derivations, and telemetry behaviour precisely without implying guaranteed outcomes. This matters legally and operationally as the product positions toward infrastructure rather than tooling.
- Why does observability matter?
- Automated systems increasingly interact with public web infrastructure independently of traditional search workflows. In many cases, classification, extraction, and attribution processes occur without direct visibility from site operators. aater.ai exists to make portions of those observable structural conditions more legible.
Participation States
- What is a participation state?
- A participation state is a derived structural classification. It represents how a domain may currently resolve across reachability, legibility, attribution, extraction depth, and rendering accessibility. Participation states are observational, not prescriptive. States may shift as site structure, rendering behaviour, or attribution signals evolve.
- What are the five participation states?
- Absent: AI systems cannot access the content — blocked, unreachable, or empty response. Marginal: reachable but structurally insufficient — no heading hierarchy, no extractable claim surface. Capturable: readable but not attributable — AI systems can extract content but will not cite it as a named source. Emerging: all gates pass with moderate authority — citation potential is building. Authoritative: all gates pass at full strength — authorship, schema, and topical coherence confirmed, positioned for extraction and citation.
- What is the Participation State Standard (PSS)?
- The Participation State Standard (PSS) is the derivation framework used by aater.ai to classify domains. It defines three sequential gates — reachability, legibility, authority — and resolves them to one of five participation states. Every classification is tagged with the PSS version that produced it. The current version is PSS v2.1.0.
- Can a participation state change?
- Yes. Participation states are not permanent. Changes to rendering architecture, robots policies, attribution structure, extraction depth, telemetry behaviour, or structural accessibility may affect future derivations. aater.ai observes structural drift — states shift as domains change.
- Is participation state the same as a ranking or score?
- No. Participation state is not a score or ranking. There is no weighted formula or fuzzy weighting. Each gate either passes or fails. The derivation is deterministic — the same domain, the same signals, produces the same state every time.
- Why does aater.ai avoid numeric scoring?
- Numeric scoring systems often imply false precision. aater.ai uses state-based derivation to represent structural conditions more transparently. The system is designed to model observable participation characteristics rather than assign arbitrary optimisation scores.
Classification System
- How does aater.ai classify a website?
- aater.ai fetches the publicly accessible HTML, robots.txt, and HTTP headers of a domain. It evaluates three gates in sequence. Gate 1 (Reachability): DNS resolution, HTTP response, robots.txt policy per AI agent, content completeness. Gate 2 (Legibility): heading structure, named entity density, extractable claim surface. Gate 3 (Authority): byline and author metadata, schema.org markup, publication dates, topical coherence. Failure at any gate terminates evaluation and resolves the participation state immediately.
- What is being classified?
- aater.ai derives classifications from publicly accessible technical and structural signals. These may include server-delivered HTML, rendering accessibility, crawl policies, attribution signals, semantic structure, extraction consistency, and telemetry observations. Classifications are generated automatically.
- Does aater.ai use live crawling?
- aater.ai may perform automated structural analysis against publicly accessible content. The platform is designed around observational derivation rather than content replication or archival storage.
- Does human judgement enter the classification?
- No. Classification is deterministic. No human judgement enters the derivation. The same domain evaluated twice under the same PSS version produces the same participation state.
- Does aater.ai store a copy of website content?
- No. aater.ai stores a structural classification of each site, not a copy of its content. The text sample shown on classification reports is stored temporarily and used only to generate the report. aater.ai does not index, cache, or republish website content.
- Does aater.ai expose its derivation models publicly?
- No. aater.ai publishes high-level methodology and observable principles, but internal derivation systems, telemetry models, verification mechanisms, and classification logic are not fully disclosed. This helps preserve system integrity and reduces adversarial manipulation.
- Does aater.ai guarantee AI visibility or citations?
- No. External AI systems operate independently and continuously evolve. aater.ai does not guarantee indexing, retrieval, citation, attribution, inclusion in AI responses, ranking behaviour, or traffic outcomes. The platform provides observational and structural analysis only.
- Is aater.ai monitoring the entire web?
- No. aater.ai derives observations from participating domains, submitted domains, observable public infrastructure, and telemetry systems associated with deployed observability layers. Coverage evolves continuously.
Pulse Telemetry
- What is Pulse?
- Pulse is aater.ai's telemetry and observability layer. It is a lightweight snippet that installs on any website, browser-side or server-side. Pulse records infrastructure-level interaction signals associated with automated systems accessing publicly available content — including verified agent activity, request frequency, request paths, crawl depth, and derived telemetry signals.
- Does Pulse track human visitors?
- No. Pulse is an observability layer for automated AI agent activity only. Requests identified as human are immediately discarded and are not stored, logged, or analysed. No human session data, cookies, or browser fingerprints are collected through Pulse.
- Which AI agents does Pulse detect?
- Pulse detects known AI crawlers and training agents including GPTBot (OpenAI), ClaudeBot (Anthropic), PerplexityBot, Google-Extended, CCBot, and others. The agent registry is continuously updated as new AI systems are identified. Pulse classifies agents by type — training agents, retrieval agents, and verification systems — based on known User-Agent signatures.
- Can I remove Pulse at any time?
- Yes. Removing the Pulse telemetry layer immediately stops all data collection. There is no lock-in.
- Does aater.ai block AI systems?
- No. aater.ai does not operate as a blocking layer. The platform may surface observable crawl policies, participation constraints, or telemetry conditions associated with automated access. Organisations remain responsible for their own infrastructure and policy decisions.
Positioning
- Does aater.ai replace analytics platforms?
- No. Traditional analytics platforms primarily focus on human visitors, sessions, conversions, and marketing attribution. aater.ai focuses on structural observability and automated-system participation signals. The two serve different purposes and can operate alongside each other.
- What types of organisations use aater.ai?
- aater.ai is designed for publishers, agencies, infrastructure teams, AI-native companies, content platforms, observability-focused organisations, and teams operating publicly accessible knowledge systems.
- Is aater.ai a policy standard?
- aater.ai publishes participation-oriented methodology and observability concepts through the Participation State Standard (PSS). The platform does not claim to define universal standards for AI-system behaviour. External systems remain independent.
- Is aater.ai trying to influence AI systems?
- No. aater.ai focuses on observing and deriving structural conditions associated with automated processing. External AI systems, crawlers, retrieval systems, and model providers operate independently. aater.ai does not control their behaviour.
Data and Privacy
- What data does aater.ai collect about me?
- aater.ai collects your email address (for account authentication via magic link), your workspace name, and the domains you choose to track. For audit runs, aater.ai fetches publicly accessible content from submitted domains. For Pulse, aater.ai processes AI agent request metadata from sites where the telemetry layer is installed. aater.ai also uses PostHog product analytics to understand how the platform is used — page paths and interaction events within the Aater product only, with all form inputs masked and no session recordings. aater.ai does not sell personal data.
- Does aater.ai use cookies for tracking?
- aater.ai uses essential cookies for session authentication and security. We also use PostHog for product analytics, which may use cookies or local storage to maintain session context within the Aater platform. No advertising cookies, cross-site tracking cookies, or third-party profiling cookies are used.
- Is classification data public?
- Participation states for classified domains appear in the aater.ai Participation Ledger, which is publicly accessible. This is structural data about publicly accessible websites — not personal data. Account data, Pulse telemetry, and workspace information are private.
- Can domains opt out of the public ledger?
- Organisations may request removal from public ledger surfaces where applicable. Operational telemetry and infrastructure logs may still be processed where necessary for security, verification, abuse prevention, or lawful operational purposes. Contact founder@aater.ai for removal requests.
Plans and Access
- Is aater.ai free to use?
- The structural audit (classification run) is free for any public domain with no account required. Pulse telemetry, dashboard access, multi-domain monitoring, and historical data require a paid plan. Pricing is available at aater.ai/pricing.
- How do I install Pulse?
- After creating an account and adding a domain, aater.ai generates a single-line image beacon tag. Paste it into your site's HTML before the closing body tag. Pulse activates immediately and begins recording AI agent visits. No additional configuration is required.
- Can agencies use aater.ai for client sites?
- Yes. aater.ai supports multi-domain monitoring and is designed for agencies managing client properties. Agencies deploying aater.ai on client sites are responsible for disclosing usage in their clients' privacy policies.
Resolve your domain
Classification is already occurring. Submit your domain to see where it resolves.
Reveal classification →