Agent Perception Security Standards Defense Join Waitlist
Agentic Web Active

Agents don't see pixels.
They read your AXTree.
That's a semantic problem.

AI agents like OpenAI Operator, Browser Use, and Manus navigate via the Accessibility Tree — not screenshots. Your site needs semantic HTML, JSON-LD structured data, and cryptographic auth to be visible in the agentic web.

Join Waitlist →
$ npx @sfa/cli init
agent-runtime — mcp handshake

Raw DOM is bloated. The AXTree is the API.

Vision costs too many tokens. DOM parsing exceeds context windows. The Accessibility Tree distills your page into a pure semantic map agents can actually reason over.

Raw DOM parsing Bloated
<div class="sc-AxjAm bqwSGR">
  <div class="sc-AxirZ gKbhqU">
    <div class="css-1dbjc4n r-1awozwy">
      <div role="button" tabindex="0"
        class="css-18t94o4 css-1dbjc4n
        r-42olwf r-sdzlij r-1phboty
        r-rs99b7 r-2yi16 r-1qi8awa">
        <!-- What does this do? -->
        <!-- 120KB of nested divs -->
        <!-- Exceeds LLM context -->
      </div>
    </div>
  </div>
</div>
Accessibility Tree AXTree
navigation "Main Menu"
  link "Products" focused
  link "Pricing"
  link "Documentation"

main
  heading level=1 "Deploy in 30s"
  paragraph "One command to..."
  button "Start Free Trial"
  textbox "Email" required

region "Pricing"
  radiogroup "Plan"
    radio "Pro — $29/mo" checked

The AXTree costs a fraction of the tokens. Use semantic <button>, <nav>, <article> — not styled <div> tags.

Agent Perception

Three ways agents see. Only one scales.

Vision burns tokens. DOM parsing exceeds context windows. The Accessibility Tree is the only perception mode that delivers semantic clarity at minimal cost.

120KB
Avg DOM payload per page
4,200
Tokens per screenshot
~200
Tokens via AXTree

Web accessibility compliance is no longer merely a regulatory issue — it is the literal API through which AI agents navigate the internet.

Make your site agent-ready →

Legacy defense is dead. Crypto auth is the new edge.

Robots.txt is an honor system. User-Agent strings are trivially spoofed. Residential proxies defeat IP blocklists. The only reliable verification is cryptographic.

Legacy Mitigation Obsolete
× robots.txt — honor system since 1994
× User-Agent filtering — one curl flag to spoof
× IP blocklists — defeated by residential proxies
× Global AI toggles — blocks legitimate agents too
× CIDR range checks — false positives lock out users
Web Bot Auth RFC 9421
Ed25519 HTTP Message Signatures
JWKS public key at /.well-known/
Signature-Agent Cards with metadata
Decentralized Agent Registries
Visa TAP & Mastercard Agent Pay ready

Four standards. One agentic stack.

The complete architecture for making your site visible, navigable, and actionable by AI agents.

AXTree Optimization Core

Semantic HTML builds a pristine Accessibility Tree. Use native <button>, <nav>, <article> with ARIA roles — the literal API agents navigate through.

JSON-LD Schema GEO

Structured data in the <head> eliminates AI guessing. Organization, Product, FAQPage, and SpeakableSpecification schemas anchor your brand in knowledge graphs.

llms.txt Standard Context

A Markdown map at your site root. Agents ingest your entire architecture in one request — bypassing HTML bloat, ads, and navigation noise.

WebMCP Protocol Actions

Declare what actions agents can take. Declarative API for forms, Imperative API for complex JS workflows. Deterministic tool execution, zero guessing.

Schema.orgWCAG 2.1RFC 9421 Ed25519JWKSAgent Registries Visa TAPMastercard Agent Pay
Architecture

Five layers. Zero bulk dumps.

Legitimate agents navigate semantically and prove identity with Ed25519 signatures. Mass scrapers hit empty DOM, poisoned payloads, and WAF interdiction.

Strategy

Fragment data behind IntersectionObserver triggers. No full tables in static HTML — require scroll, click, and tab interactions before content renders in the DOM.

Why it works

Consumer agents (OpenAI Operator, Browser Use) navigate sequentially and trigger observers naturally. Bulk scrapers fetch raw HTML and find empty containers.

IntersectionObserver Lazy Loading DOM Fragmentation
Strategy

Track session traversal depth, navigation timing, and request cadence. Legitimate agents visit 3–7 pages at human-like intervals. Scrapers attempt hundreds in milliseconds.

Targeted Inspection

ML-driven baseline analysis detects behavioral anomalies — residential proxy rotation, randomized fingerprints, and unnatural mouse movement patterns.

AWS WAF Bot Control Targeted Inspection Timing Analysis
Honeypot Endpoints

Hidden URLs with zero AXTree semantic value — invisible to humans and well-behaved agents. Any programmatic interaction provides deterministic proof of scraping intent.

Proof-of-Work

Flagged sessions face computationally expensive challenges. LLMs are explicitly trained not to solve CAPTCHAs — the scraper workflow halts completely.

Honeypot Traps Proof-of-Work AXTree Invisible
Web Bot Auth

Verified agents present Ed25519 HTTP Message Signatures (RFC 9421). The server retrieves JWKS public keys and validates identity with mathematical certainty — no IP or User-Agent needed.

Agent Cards

Each verified bot carries a Signature-Agent Card with rate expectations, purpose declarations, and contact metadata. WAF rules auto-configure per-agent rate limits.

RFC 9421 Ed25519 JWKS Registries
Allow

Verified live-retrieval agents (ChatGPT-User, Claude-User, Perplexity-User) — triggered by human prompts, cryptographically signed, semantically navigating.

Block

Mass-training crawlers (GPTBot, ClaudeBot) and unauthorized scrapers. Unverified entities trigger adaptive MFA authentication before any high-risk action proceeds.

Granular WAF Rules Adaptive MFA Agent Classification
AgentShield v1.0 5/5 layers active
Micro-Frontends
Rate-Limiting
Honeypots
API Gateway
Crawl Control

Semantic HTML. Structured data.
Cryptographic auth. One platform.

AXTree optimization, JSON-LD, llms.txt, WebMCP, and Ed25519 verification — deployed in one config. Drop your email for early access.

Free during beta • No credit card required

Open Standards
RFC 9421 Native
AXTree First