Agent trust & execution-proof infrastructure
Govern AI agents before they act.
Prove what happened after.
AgentNOMOS binds intent, capability, authorization and execution into a cryptographically verifiable receipt — and records the observed outcome separately, related to that receipt but not contained in it.
A2A · MCP · x402 · Signed receipts · Base Mainnet
Capability is easy. Trust is a decision.
AgentNOMOS is the decision layer in between — and the receipt afterwards.
One chain from intent to outcome.
For the governed route cohort, every action passes through the same bound sequence. Each stage is recorded; the signed receipt seals intent through execution and the returned bytes. The outcome is recorded afterwards and is not bound by the receipt.
This eight-step flow is a human-readable projection of the canonical eleven-stage S0–S10 runtime model published in the capability manifest: Intent = S4, Capability = S3, Offer = S5, Security Evidence feeds S0, Authorization = S6, Execution = S7, Signed Receipt = S8, Outcome = S9. Presence (S1), Identity (S2) and Governance (S10) are not drawn. Public verifiability is limited to S3–S8; execution is not outcome.
Four operations. One system.
→ VALID | INVALID
→ PERMIT | DENY
→ bound execution
→ SIGNED RECEIPT
outcome → recorded separately
Don't trust the diagram. Verify the execution.
A real, paid, governed execution — publicly reproducible.
| Capability | nomos_full_chain_verification |
|---|---|
| Network | Base Mainnet · eip155:8453 |
| Price | $0.001 USDC · 1000 atomic |
| Invocation | x402 |
| Verify | stateless / offline — 21/21 PASS |
| Reference | Public ALLOW case · Production DENY case |
| Receipt | signed · Ed25519 |
# Free offline verification — published reference bundles
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.jsonWhat this proves: the bound execution chain and its reproducible references. What it does not claim: third-party audit of our internal policy.
Built for consequential agent actions.
| Context | NOMOS role |
|---|---|
| Agent Payments | Bind authorization to execution — designed to keep payment and execution from drifting apart; each settled call through the chain carries a receipt bound to its authorization. |
| Autonomous Procurement | Preserve mandate through purchase — bind mandate, purchase and execution, and record the outcome separately, so a buying agent can show it was allowed to. |
| Agent Marketplaces | Verify authority before invocation — check capability and authorization before invoking another machine, and hold a receipt afterwards. |
| Regulated Workflows | Attach evidence to consequential action — current evidence and governance before the action runs, not after. |
Machine-discoverable by design.
Agents can discover AgentNOMOS without a human in the loop. Humans start here:
| Interface | Location |
|---|---|
| Docs | agentnomos.xyz/docs ↗ |
| Agent Card (canonical) | agentnomos.network/.well-known/agent-card.json ↗ |
| Capabilities | /.well-known/nomos-capabilities.json |
| MCP | /.well-known/mcp.json |
| x402 | /.well-known/x402.json |
| AI Catalog | /.well-known/ai-catalog.json |
| llms.txt | /llms.txt |
One trust chain. Specialized infrastructure underneath.
These are components of one system — not three products competing for your attention.
AgentNOMOS is trust infrastructure for autonomous machine actions. It connects intent, capability, evidence, authorization, execution and proof so that consequential agent actions remain attributable and verifiable.
Built by FeedOracle Technologies in Germany.
Agents will act autonomously.
Their actions shouldn't become unverifiable.