NOMOS does not replace your agent framework. It gives agents a governed way to discover capabilities, verify terms, route to ToolOracle services and understand which actions are allowed. Five steps, all public, all machine-readable — aggregated in /.well-known/connect.json.
Start here on agentnomos.network. Tool and x402 discovery is delegated to the ToolOracle public manifests — agent cards, MCP descriptors, pricing and the full agent directory are machine-readable:
Identity uses W3C DIDs; providers and external agents go through verification gates — not every agent can join without verification. First contact for agents is the natural-language handshake manifest:
Every oracle is a standard MCP server at its own public URL. Point any MCP client at the descriptor or directly at an oracle endpoint — free preview tiers let you test before paying per call:
{
"mcpServers": {
"tooloracle": {
"url": "https://tooloracle.io/.well-known/mcp.json"
},
"nomos-macro": {
"url": "https://tooloracle.io/macro/mcp/"
}
}
}
Per-oracle endpoints follow the pattern https://tooloracle.io/<name>/mcp/ — the full list lives in the agent directory above.
A pilot corridor of six standard read-only oracle products accepts standard x402
payments at the endpoint level: flight ($0.02 / call) and
weather, sport, movie, map, crypto ($0.05 / call).
402 responses advertise accepts[]; agents using x402-fetch / x402-axios send a
signed authorization in the X-PAYMENT header; settlement is verified before the
tool executes. All other routes: discovery is live, standard-x402 rollout is staged —
no public price yet.
Request → 402 Payment Required (accepts[]) → X-PAYMENT response (signed authorization) → verify / settle → backend release only if allowed → governance boundary remains active
NOMOS places agents, tools, prices and evidence sources into governed solution chains: action preflight, compliance signals, decision records and signed receipts. Team & Enterprise Control covers governance, routing, receipts, stack-fit and partner federation; external providers can later join a verified federation model. The public stack stays read-only — no live execution, no signing, no settlement from this surface.