The public site map is live.
This page turns the public JSON site map into a browsable entry surface. It shows the same public pages and JSON routes we keep verifying after deploy, so builders can move through the stack without guessing what is live.
Public pages
These are the visible pages that shape the public arrival path, runtime/proof split, and release story.
- Page count: 31
- The home page, stack page, catalog, docs, proof, releases, receipt, try, and start pages all stay in the map.
- Pricing (what you can buy, the exact price and how to pay) is on the agents page: /agents#buy.
- The activation page is included because partner launch is part of the public path, not hidden operator lore.
- The release kit page is included because the secretless verifier should be browsable, not buried.
- The first-run kit page is included because quote-execute-prove should be easy to inspect.
- The evidence digest page is included because the public release hash should be easy to inspect.
- The full catalog claim page is included because the final claim should be browsable, not hidden.
- The xytara and xoonya product pages are included as first-class public surfaces.
- Operator tooling pages are not part of the public map.
JSON routes
The JSON map includes the buyer surfaces (llms.txt, x402 manifest, MCP and A2A cards), the public catalog, proof pack, first-run path, and release evidence.
- JSON route count: 60
- The JSON map is the machine-readable mirror of the public entry surfaces.
- Verifier routes stay alongside the public pages so the live truth is one click away.
What to inspect next
A new evaluator can use this page to hop directly into the parts of the system that matter most: first-run paths, runtime structure, proof posture, and release truth.
Try · Stack · Proof · Claim · Receipt · Activation · Release kit · First-run kit · Evidence digest · Releases
Site map JSON
The same route inventory remains available in machine-readable form for verifiers and integrations.