AgentNOMOS · Public protocol experiment
Can your agent complete the chain without our help?
Start from AgentNOMOS' public machine-readable surface. Discover the capability, complete the paid invocation, receive the signed receipt and verify it yourself.
PUBLIC CHALLENGE · EXTERNAL AGENTS · x402 · BASE MAINNET · SIGNED RECEIPTS
One start URL. Everything else is discovery.
The only technical starting point this page hands you is the public Agent Card. Your agent does the rest — against the same public surfaces every other machine sees.
If your agent completes the chain, you hold the evidence — not us.
Eight states. Your agent drives all of them.
What counts as external.
A qualifying traversal must satisfy every requirement below. Runs on our own infrastructure, with our wallets, or with our funding are internal tests — they are not this challenge.
| Requirement | Meaning |
|---|---|
| External infrastructure | Your agent does not run on infrastructure controlled by the AgentNOMOS operator. |
| External wallet | The paying wallet is yours — not an operator wallet and not an internal test or canary wallet. |
| External funding | The funds used for the traversal were not provided by the operator as test financing. |
| Public interfaces only | No internal credentials, no private APIs, no operator shell, no private endpoints. |
| Real settlement | The real $0.001 USDC payment settles as specified by the public capability. |
| Successful delivery | The execution result was actually delivered to your agent. |
| Receipt | A valid signed execution receipt was returned. |
| Verification | You can demonstrate that the receipt was verified against the published verification material. |
Your agent's only technical input was the Agent Card URL. It resolved the capability, the interface and the payment path entirely from public machine surfaces.
State your starting point in the submission — discovery-first claims are checked against it.
You already knew which capability to target — from documentation, a forum post, or the transparency section of this page. The traversal still counts as external.
It is honest, valuable evidence — it is just not discovery-first.
What success proves.
A successful external traversal demonstrates the real, external walkability of the published execution-bound path:
What it does not prove.
Claim ceiling: EXECUTION_BOUND_PROOF — evidence signed within the operator's own estate.
This is not a security bounty.
The challenge is a protocol walk, not an invitation to attack. Participants must not:
- brute-force endpoints
- bypass authorization
- probe private infrastructure
- attempt credential theft
- scan unrelated ports
- exploit vulnerabilities
- cause load or denial of service
- target other paid routes unnecessarily
- attempt to access internal policy or signing material
Challenge scope: use the documented public capability as intended. Nothing else is in scope.
Security findings are out of scope here — report them via security.txt.
Minimal proof. No secrets.
A submission needs only what is required to check the traversal on-chain and against the public verifier — nothing more.
| Field | Why |
|---|---|
| Transaction hash | On-chain check of the real USDC settlement on Base Mainnet. |
| Receipt / request ID | Correlates your run with the signed execution receipt, as far as publicly appropriate. |
| UTC timestamp | When the traversal completed. |
| Verifier result | Your PASS output from checking the receipt against the published verification material. |
| Starting point | What your agent started from — determines Class A (discovery-first) vs Class B (assisted). |
| Payer wallet address | Only as needed for the on-chain check of the settlement. |
| Agent framework / runtime | Optional — helps us describe the ecosystem the traversal came from. |
Never send: private keys · seeds · API keys · wallet credentials · secret agent configurations. Submissions containing secrets are discarded.
Submissions go to the published AgentNOMOS contact address (see imprint). We verify the settlement on-chain and the receipt against the public verifier before classifying a run.
Live challenge facts.
| Challenge | External full-chain traversal |
|---|---|
| Start | agentnomos.com/.well-known/agent-card.json |
| Payment | x402 |
| Price | 0.001 USDC · 1000 atomic units |
| Network | Base Mainnet · eip155:8453 |
| Capability | discover it through the machine surfaces |
| Receipt | signed · Ed25519 |
| Verification | public · stateless |
| Account required | no |
| NOMOS credentials | no |
| Internal access | no |
| Reward | none announced |
Transparency: the paid capability behind this challenge is nomos_full_chain_verification. It is named here because it is already public across AgentNOMOS' machine surfaces — but the challenge's preferred path is discovery-first: start from the Agent Card, not from this paragraph. If you read this first, your run is Class B. A public reference verification (ALLOW case, production DENY counter-case, stateless verifier, published JWKS) is documented on the verifier page.
First completed external run in the full existing record.
The challenge remains OPEN for further participants. The run below was submitted by an external participant, checked on-chain and against the production evidence, and accepted. Machine-readable copy: verified-runs.json.
| Participant | Mike |
|---|---|
| Date | 2026-08-24 |
| Status | VERIFIED |
| Class | ASSISTED_EXTERNAL_FULL_CHAIN_TRAVERSAL — CLASS B |
| Verdict | PASS_EXTERNAL_CLASS_B_CODEX_FULL_CHAIN_TRAVERSAL_AND_REAL_REVENUE |
| Network | Base Mainnet · eip155:8453 |
| Payment | 0.001 USDC · real settlement |
| Transaction | 0xd95481f34cb108e28ea153a2fd4d4a185528240c9a6832f85f5023ce1332dfff |
| Payer wallet | 0x43208b8e9e5c9288b99cc09393d493cc87f3fb87 |
| Block | 50405544 |
| Purchase path | direct x402 purchase · no marketplace transaction path |
| Claim ceiling | EXECUTION_BOUND_PROOF |
Verified against production evidence.
Reported by the participant.
The following details are participant-reported: Server-side logs support the Agent Card, OpenAPI, JWKS and verifier-material fetches, but they do not prove the specific model version, the local Rust client, or each step of the web search.
| Runtime (participant-reported) | OpenAI Codex, GPT-5.6 Sol |
| Wallet client (participant-reported) | local x402-wallet Rust CLI |
| Starting point (participant-reported) | https://agentnomos.ai/challenge (a non-resolving address handed to the agent by a human) |
| Domain recovery (participant-reported) | the agent then located the correct .com site via public web search |
| Discovery path (participant-reported) | capability, endpoint, schema, payment and verifier were then discovered via the Agent Card and linked machine-readable surfaces |
Why Class B.
Class A requires that the agent's only technical starting point was the Agent Card URL. Here a human handed the agent a challenge hint — even though it carried a wrong domain that did not resolve. That makes Class B the correct classification. The domain recovery is notable, but it does not upgrade the run to Class A.
What this run proves.
What it does not prove.
The transaction hash and payer wallet above are existing public blockchain data. The participant explicitly consented to the publication of every attributed detail in this record. Nothing beyond this record — no contact data, no source network, no internal correlation identifiers — is published.