Verify it yourself

A payment receipt proves that money moved. NOMOS is built to prove more: publicly testable continuity from represented intent through authorization and execution to a signed, verifiable receipt and resulting outcome. On this page you can check that claim on your own machine, for free, in about two minutes — no wallet, no account, no contact with our servers beyond downloading four public files.

The product in 30 seconds

AgentNOMOS (by FeedOracle Technologies) is a governance layer for autonomous agent actions. Before a machine action runs, NOMOS binds together: the represented intent, the selected capability, the offer (price/terms), current security evidence, the authorization decision, the actual execution, an Ed25519-signed execution receipt, and the outcome. The result is one connected evidence chain — so a refusal is as auditable as an approval, and a receipt binds far more than a payment.

There are four distinct surfaces. Do not confuse them:

The live paid capability

Path 1 — Free offline verification (start here)

We publish two reference evidence bundles from production — one ALLOW (a real settled $0.001 execution) and one DENY (a real production refusal, HTTP 403 TASK_FIT_MISMATCH, where only the append-only refusal store advanced and every execution counter stayed at zero) — together with a stateless ~300-line Python verifier (stdlib; the cryptography package only for the Ed25519 check).

curl -sO https://agentnomos.com/proof/full-chain/allow-reference.json
curl -sO https://agentnomos.com/proof/full-chain/deny-reference.json
curl -sO https://agentnomos.com/proof/full-chain/nomos_repro_verify.py
curl -s  https://feedoracle.io/.well-known/nomos-execution-jwks.json -o jwks.json

python3 nomos_repro_verify.py --allow allow-reference.json \
                              --deny  deny-reference.json  \
                              --jwks  jwks.json

Expected final line:

21 checks: 21 PASS, 0 FAIL, 0 NOT_RUN

The checks recompute the intent digest, the capability/offer/evidence bindings, the receipt digest over verbatim JSON number lexemes, and the Ed25519 receipt signature against the public JWKS. The settlement transaction in the ALLOW bundle is a normal USDC transfer on Base — inspect it on any public Base explorer. Full methodology, including which fields are cryptographically verifiable, deterministically recomputable, or operator-attested: verify.md. Tamper with any bound byte and the verifier fails closed — that is the point.

Path 2 — Optional live paid verification

If you want your own receipt rather than our reference one: any x402-capable client can call the endpoint above. You pay $0.001 USDC on Base, receive the result of one governed read-only action, and can verify the returned receipt against the same public JWKS with the same verifier logic. The first un-paid POST simply returns the HTTP 402 payment requirements — that alone shows you the offer terms without paying.

The Trust Chain (canonical model)

The NOMOS Machine Economy Trust Chain is eleven stages, S0–S10. In plain terms, one governed action passes through:

1. Discovery & identity — who is asking, and which published capability is addressed
2. Represented intent — a digest-bound intent document naming capability, action, route, purpose and constraints
3. Offer — the priced terms the caller accepted (x402)
4. Security evidence — current, freshness-gated evidence about the executing estate, an input to authorization (fail-closed)
5. Authorization — an admission decision that can ALLOW or DENY; a DENY is recorded evidence, not a dropped request
6. Execution — the actual bounded action
7. Signed receipt — Ed25519-signed, binding payment, intent, offer, admission, execution and response bytes
8. Outcome & governance context — the result and its append-only stores

What this proves — and what it does not

The claim boundary

NOMOS proves continuity from the represented intent onward. It does not prove that the represented intent was the correct interpretation of the human's underlying meaning.

Everything published on this surface carries the claim ceiling execution-bound proof: it is evidence about what this operator's estate executed and signed, machine-checkable by you — not an independent audit, not a certification, and not a claim of external adoption. Signed offers and receipts as concepts are not our invention — x402 and neighboring protocols already define offer/receipt primitives. What NOMOS adds is the governed binding across intent, capability, offer, security evidence, authorization, execution, receipt and outcome.

How it composes with existing protocols

These are interoperability descriptions, not endorsements by any protocol organization.

Security & responsible disclosure

Security contact and policy: /.well-known/security.txt. If you find a way to make a verifier pass on tampered evidence, or any boundary violation, we want to hear it — and we will document failed external tests as openly as passed ones.