Aere Agents

An agent that can pay, call tools or move a machine needs limits that someone other than the agent can check, and a record that someone other than its operator can read. Agents is the set of published components that give an agent or a device a post-quantum identity, a policy, a way to pay and a signed record, all verifiable offline from the files.

What exists today, measured

Every line below names the date its module was published in the public repository, the page or the contract behind it. Each module ships its README, its tests and its negative controls; nothing here asks you to take our word.

• Agent identity, policy and record, 2026-09-29, updated 2026-10-12. An ML-DSA-65 identity per agent, a policy (spending limit per time window, allowed tools, who approves), human approvals, and a ledger of signed actions that a verifier judges from the files. Module agents.
• Machine payments, AERE402 / x402, on the public testnet. HTTP 402 payments for machine accounts, with a facilitator running on the public testnet (chain 28001) since 2026-09-02. On mainnet (chain 2800) no x402 payment service runs today. Page: AERE402.
• Device identity, 2026-10-11, updated 2026-10-15. A chain of signed statements about a machine: who made it, which firmware it runs, who owns it, what it may do, whether it is still in service, and what it says about itself now; one verifier judges the whole chain offline and says VALID, PARTIAL or INVALID, naming every rule that refused. Module device-identity.
• Provenance of an AI action, 2026-10-02. An AIP-23 envelope that proves which model, which version, which prompt, which tools, which output, which agent and who asked, verified by the same verifier as every other Aere proof (proof-of-ai), and the trust record of an AI result built from the agent identity, the model attestation and the host record (ai-trust).
• On-chain roots. A post-quantum key registry with proof of possession and an agent DID rooted in a Falcon key with revocable session keys, deployed and self-tested on chain 2800, independent audit pending, and empty today (no agent has registered); the live page is the identity registry. Delegation of a credential to an agent, a device or a session key comes from the Identity line.

What it is not, yet

• No product today writes the logs that the EU AI Act asks for in the form a regulator will expect; the words appear in our documents, the product does not exist yet.
• No reputation system. A record says what an agent did; it does not score the agent.
• The x402 facilitator runs on the public testnet only; on mainnet there is no machine-payment service, and the agent registries deployed on chain 2800 are empty (measured 2026-10-17: 8 of 41 conformance checks pass on them).
• No third-party audit of these modules or contracts has been published yet.

How it uses the engine

Payments settle and records can be notarized on chain 2800, final in half a second, with a post-quantum certificate under every 32nd block. The agent never needs to know there is a chain; the verifier of its record does not need the chain at all. The network itself is described at Developers.