Verify what AgentTrust did.

AgentTrust ships every paid agent request as a signed receipt + a hash-chained audit entry + an offline-verifiable proof bundle. This page tells you exactly what is verifiable today, what is not claimed, and how to verify the rest yourself.

What this proves

• The public sandbox is live and reachable.
• The console flow (session → workspace → provider → endpoint → curl) is live.
• Every successful 200 carries an X-AgentTrust-Receipt-Id header that points at an Ed25519-signed canonical receipt.
• Receipts can be verified two ways: (a) offline via the gateway public key + canonical JSON sha256, (b) on-chain by the deployed Anchor program at FWdCDkFnexcJrMMhzfPLuBnX3RaFS8zoaqxCsMLxvw9Z on Solana mainnet — the program reads the Ed25519SigVerify sysvar instruction and validates the receipt signature in a single transaction.
• Proof bundles verify offline against the published gateway public key.
• External verification is complete across four real third-party lanes, see the lane composition on the security model page.

What this does not prove

• Enterprise GA. Not claimed.
• Production billing. Not launched.
• Real customer pilot. Not yet completed.
• Customer logos, testimonials, traction. Not claimed.
• SOC 2 / ISO 27001 / HIPAA / PCI / Okta / Entra / Google SAML / SCIM 2.0 official certification. Not claimed.

Live verification commands

Run these in your own terminal. They hit the live public sandbox; they do not require credentials.

1. Liveness probe

curl -i https://sandbox.aisthetic.services/live
# → 200 OK { "ok": true, "service": "agenttrust-api", ... }

2. Self-serve sandbox status

curl -s https://sandbox.aisthetic.services/v1/self-serve/sandbox/status
# → bounded JSON, schema agenttrust.self_serve_sandbox_status.v2

3. 401 → 402 → 200 + signed receipt

/g/aisthetic/probe is the canonical public path. /g/demo/data and /g/sandbox/data remain as backward-compat aliases that route to the same sandbox provider.

# 1) no identity → 401
curl -i -X POST https://sandbox.aisthetic.services/g/sandbox/data

# 2) sandbox identity, no proof → 402
curl -i -X POST https://sandbox.aisthetic.services/g/sandbox/data \
  -H "X-AgentTrust-Wallet-Address: 0xSANDBOX" \
  -H "X-AgentTrust-Signature-Scheme: sandbox" \
  -H "X-AgentTrust-Principal: did:web:sandbox.aisthetic.services"

# 3) sandbox identity + sandbox proof → 200 + receipt
curl -i -X POST https://sandbox.aisthetic.services/g/sandbox/data \
  -H "X-AgentTrust-Wallet-Address: 0xSANDBOX" \
  -H "X-AgentTrust-Signature-Scheme: sandbox" \
  -H "X-AgentTrust-Principal: did:web:sandbox.aisthetic.services" \
  -H "X-AgentTrust-Sandbox-Proof: demo-paid"
# → 200 OK
# X-AgentTrust-Receipt-Id: rcp_<placeholder>

Proof surfaces

How to verify

Five independent verification paths, pick the one that fits your trust posture:

1. Verify a receipt in your browser. Paste any AgentTrust receipt JSON; WebCrypto Ed25519 runs entirely client-side. The pasted receipt never leaves the browser.
2. Browse the public sandbox provider. Recent signed receipts list, embed-snippet, and a click-through to per-receipt detail at /r?id=<receipt-id>.
3. Read the mainnet canary proof. First real x402 settlement on Base mainnet: 0.01 USDC, verify-first invariant, signed receipt, hash-only fingerprints mirror the operator artefact pack 1:1.
4. Run the gateway flow yourself. The 401 → 402 → 200 + receipt sequence above is the canonical proof-of-life for the gateway.
5. Verify the dataroom bundle. Request the signed dataroom; run pnpm dataroom:verify <path-to-extracted-bundle> against the recipient’s copy. Checksums must all match.

Machine-readable posture

For programmable consumers, the same canonical posture literals this page surfaces ship as a bounded JSON endpoint:

curl -s https://sandbox.aisthetic.services/v1/status | jq .
# → bounded JSON, schema agenttrust.public_status.v1
# components.publicSandbox = "live"
# components.mainnetCanary = "passed"
# components.externalVerification = "complete"
# components.publicBilling = "not_launched"
# ...

For a human-readable mirror of the same JSON plus a live runtime probe (Postgres / Redis / webhook receiver reachability), see /status.

How proof reaches the workbench

Sandbox proof is not just an explainer. The Provider Workbench at app.aisthetic.services/proof-ledger renders real session-scoped audit events for the four self-serve setup actions and surfaces a per-receipt verifier that fetches the public /v1/receipts/:id endpoint and links to the offline Ed25519 verifier at /verify. The chain is: endpoint → request → receipt → proof → audit, reachable from inside the workbench, not just described here.

Current public-beta status

• Provider Workbench is ready. Open the Workbench at app.aisthetic.services and create your first agent-facing endpoint in five steps.
• Sandbox resources are durable. Workspace, provider, and endpoint records persist across browser refreshes and Fly machine restarts. Reset cleanly via the console.
• External verification is complete. Four lanes round-trip against real third-party tenants. See /security for the lane composition.
• Custom domain is live. The console is served at app.aisthetic.services over HTTPS.

What we deliberately do not claim

• Enterprise pilot has not started.
• Enterprise GA is not claimed.
• No paid plan launched. No billing rail integrated.
• No real customer pilot completed. No revenue, no logos, no benchmarks.
• No SOC 2, ISO 27001, HIPAA, PCI, Okta, Entra, Google SAML, or SCIM 2.0 official certification.