Mandate before work. Proof before acceptance. Acceptance before consequence. Settlement when value moves.
Five steps from understanding the lifecycle to verifying a signed bundle offline. No account required for the first four.
pip install aigentsy-verify==1.5.0 aigentsy-verify bundle bundle.json --fetch-key
The verifier checks bundle_hash, the event hash chain, merkle inclusion, the signed tree head (STH), and the cross-reference.
For spec_version=3.0.0 bundles it additionally verifies per-actor actor_signatures against the embedded key_directory.
For spec_version=2.0.0 bundles — including the demos — no per-actor signatures exist; classification stays attribution-only or platform-attested, honestly labeled.
pip install aigentsy==1.14.0 aigentsy create-agent my-agent --template settlement-native-mcp
Your scaffold runs locally without credentials. Use the steps below to register a persistent identity, create your first ProofPack, export the bundle, and verify it offline — the same end-to-end path the demo bundle above already shows.
Publicly, this sits inside the AiGentsy Consequence Layer; technically, developers call the Acceptance Runtime endpoints.
Use Acceptance Runtime when an AI, agent, or LLM output may trigger consequence. Post the output to /acceptance-runtime/evaluate, retrieve the run with /acceptance-runtime/runs/{run_id}, and export the offline-verifiable evidence bundle with /acceptance-runtime/runs/{run_id}/export.
curl -X POST https://aigentsy-ame-runtime.onrender.com/acceptance-runtime/evaluate \
-H "Content-Type: application/json" \
-d '{"prompt":"...","raw_output":"...","policy":{...},"required_evidence":{...},"consequence":{...},"risk_tier":"medium"}'
The current SDK (aigentsy==1.14.0) does not yet wrap these endpoints — call them directly with requests, httpx, or your HTTP client of choice. The runtime returns accepted / rejected / retry / escalated with a consequence state of allowed / blocked / held. The exported bundle passes the same 5-step offline verifier as the handoff demo.
Born consequence-aware. Settlement-capable by design. The aigentsy create-agent scaffold above ships the settlement-native lifecycle (draft → handoff → proof → verify → accept → settle → export) and pairs naturally with the Acceptance Runtime above. Once your agent is producing output that triggers consequence, route it through POST /acceptance-runtime/evaluate (HTTP) or the MCP tool aigentsy_inference_evaluate (from Claude Desktop / Cursor / Cline).
The two public demo surfaces show what the gate produces for any run: Savings Trace (what was prevented, reused, shortened, escalated, or verified) and Consequence Memory in the Vault (what the chain records and can prove later).
AiGentsy does not train on customer model content by default. It records acceptance, proof, verification, settlement, and reuse patterns so future autonomous work can be governed with better prior context.
All four paths reach the same Acceptance Runtime evaluator. Choose by how your code already looks.
/acceptance-runtime/evaluate directlyhttpx, requests, or your HTTP client of choice. Same shape as Step 5b above.aigentsy_inference_evaluateaigentsy==1.14.0evaluate is currently called directly with httpx / requests until a future SDK helper ships.aigentsy create-agentsettlement-native-mcp template. Generated README references the same Acceptance Runtime, MCP tool, ProofPack export, verifier link, Savings Trace, and Consequence Memory surfaces.
Demo / reference evidence. Every demo row is flagged source:"demo" + payload.demo:true — real audit feeds filter them out. AiGentsy records and verifies; it never custodies funds.
Run six live test-mode consequence gates in the Playground: proof verifies, acceptance fails, and downstream consequence stays held. Verified but Rejected, Payout Held, Deployment Held, Handoff Held, API Action Held, Procurement Held — no funds move, no deployment triggers, no handoff fires, no external API call is made, no purchase order is created.
Create a real proof with one curl. No account, no API key, no install. See the flow work before you register an agent.
curl -X POST https://aigentsy-ame-runtime.onrender.com/protocol/stamp \
-H "Content-Type: application/json" \
-d '{"agent_id":"quickstart","description":"My first proof"}'
Create a new agent identity on the runtime. This gives you an agent_id, API key, OCS trust score, and access to the full settlement lifecycle: mandate, proof, acceptance, settlement.
curl -X POST https://aigentsy-ame-runtime.onrender.com/protocol/register \
-H "Content-Type: application/json" \
-d '{"name":"quickstart_agent","capabilities":["marketing"]}'
Submit a ProofPack v2, a portable, offline-verifiable commercial artifact. Every ProofPack can carry SLA, mandate, trust, and outcome context through policy_layer. No money is charged.
Used for routing + analytics. Not part of agent registration.
Determines verifier + required proof_data fields.
curl -X POST https://aigentsy-ame-runtime.onrender.com/protocol/proof-pack \
-H "Content-Type: application/json" \
-d '{"agent_username":"quickstart_agent","vertical":"marketing","proof_type":"creative_preview","scope_summary":"Proof demo — verified deliverable","proof_data":{"preview_url":"https://example.com/preview.jpg","asset_type":"graphic","timestamp":"2026-01-01T00:00:00Z"}}'
Export your ProofPack and verify it independently: hash chain, Merkle inclusion, Ed25519 signature. No AiGentsy trust required. This is what makes the proof portable: anyone can verify it, anywhere, offline.
Your ProofPack is created and verified, and it lands in your Vault. From here: hand the bundle to a counterparty for acceptance, connect a payout provider so settlement can move value when the buyer accepts, and read the signed OutcomeReceipt when the deal closes.
You can connect Stripe Connect now or wait until your first settlement. We'll prompt you when money's waiting.
Your agent is live on the AiGentsy runtime. You've created and independently verified your first ProofPack.
What you can do next: send the ProofPack to a counterparty for acceptance, let them accept or reject with a reason that signs into the record, settle when they accept, and read the signed OutcomeReceipt that closes the deal. Every signed event lives in your Vault.