Acceptance gate · not framework, not observability, not payments
The acceptance gate between autonomous work and real-world consequence.
Proof, verification, and settlement for autonomous work. Bring any model. Bring any agent. Use your agent or ours. AiGentsy decides one thing: is this autonomous work allowed to create consequence?
Logs observe. Gates decide.
Mandate before work. Proof before acceptance. Acceptance before consequence. Settlement when value moves.
Each consequential output carries a portable, offline-verifiable artifact.
Payable
Settlement moves only after proof and acceptance. Plug in any provider; no custody.
Institutional
Mandate, proof, acceptance, settlement, lineage — one signed record. Audit whenever needed.
Consequences We Gate
Useful agent work should not trigger consequence until accepted.
Examples of consequences AiGentsy is built to gate include the ones below. The counterparty defines the acceptance standard. AiGentsy enforces it — signs accept or reject — and only then allows the next move.
Acceptance Runtime is live: agent and LLM outputs can now be evaluated, accepted, rejected, retried, escalated, blocked, held, or allowed before they create consequence. Some examples below are surfaced today as live demos; others are integration shapes the protocol is built to gate.
Payout
Money moves
Settlement
Deal closes
Deployment / Release
Code ships
Handoff
Work passes on
Procurement
PO approved
Invoice Approval
AP releases
API Action
Side effect fires
Inventory Movement
Stock moves
Customer Delivery
Asset shipped
Compliance Escalation
Routed to review
Agent Delegation
Downstream picks up
Reputation Update
OCS / score moves
The counterparty defines the acceptance standard. AiGentsy enforces it — signs accept or reject — and only then lets the next move happen.
Together, these functions form the AiGentsy Consequence Layer: Recall what was proven, Accept what is allowed, Prove what happened, Verify the record, and Settle only when consequence is authorized.
Whichever path you start with, every signed event lands in your Vault — the portable, offline-verifiable record of every deal's mandate, proof, acceptance, and settlement. Open the Vault demo for live signed evidence, or jump to Quickstart for a 5-step proof-to-settlement walkthrough. The Trust Console offers a supporting lifecycle narrative for enterprise buyers.
MCP: Claude, Cursor, Cline, and growing
MCP exposes 14 proof, verification, settlement, acceptance, and consequence-middleware tools to any MCP-compatible runtime. Zero SDK install.
Build your agent anywhere. With AiGentsy, it can be born knowing when work needs proof, acceptance, and downstream consequence.
First reference adapter for the Settlement-Native Agent Core. Local scaffold; no network or credentials needed to run. PyPI →
The protocol flow
Six steps. Output never reaches consequence without passing through acceptance.
Output
Agent or framework produces work
Signals
AdapterContract validates typed inputs
Policy
Counterparty defines acceptance
Decision
AiGentsy signs accept / reject
Consequence
Moves on accept; holds on reject
Replay
Artifact verifies offline
Plug in any payment provider on accept. No custody. Replay whenever challenged.
How acceptance moves consequence
Settlement on acceptance Settlement triggers only when proof verifies and the appropriate acceptance gate passes. Exactly-once consequence, no custody.
Proof at handoff Every deliverable becomes a portable, offline-verifiable cryptographic receipt.
Governance before handoff Compute and authority rules are explicit before consequential work advances. Every consequential decision carries a cryptographic signature, bound into the ProofPack.
Per-actor signing where actors enrolled keys Disputes, acceptances, and recorded outcomes can carry independent per-actor Ed25519 signatures — the actor signs their own event with their own key, non-custodially. Opt-in: present where actors enrolled keys, platform-attested where the platform recorded an action on behalf of a labelled actor, attribution-only otherwise. The bundle’s key_directory snapshots the public keys for offline verification.
Why not just use a payments processor or workflow gate?
Your payments provider moves money. Your workflow orchestrator advances state. Keep using them.
AiGentsy adds the cryptographic accountability layer between output and consequence:
Proof at handoff. Cryptographic proof that work was completed, locked before money moves.
Explicit acceptance gate. Nothing gets released, completed, or paid without an auditable accept/reject decision.
Exactly-once settlement. No double-charges, no double-payouts, replay-safe under concurrent automation.
Team-awarded work. Complex jobs get team suggestions with auditable per-agent splits through the same settlement path.
Portable offline verification. Export a proof bundle and verify it without calling any server.
Governance by default. The Governance Layer of the AiGentsy Stack emits signed attestations of every consequential compute decision, bound into the ProofPack.
Tamper-evident without blockchain baggage. RFC 6962 transparency logs anchored to an external timestamp authority. No gas, no tokens, no consensus latency.
ProofPack Reuse. When agents encounter work that prior attested ProofPacks already cover, the system can reuse the signed result without rerunning already-attested work where the prior proof safely applies. Every reuse decision is governed, auditable, and bound into the ProofPack.
Five layers of the gate
Most systems prove a transaction completed. AiGentsy proves the work happened — before payment, release, next-stage authorization, and long after. Five layers in one signed, offline-verifiable artifact.
Settlement Value moves and downstream consequences trigger only when the required proof and acceptance conditions are met.
Formation Intent becomes accepted agreement under clear scope, rights, and constraints.
Execution Work is coordinated, resourced, and proven under the conditions required to complete it.
Governance Compute is governed before handoff, with authority and execution rules made explicit from the start.
Continuity Trust, lineage, and durable organizational identity carry forward across repeated work and evolving agent systems.
MCP exposes 14 proof, verification, settlement, acceptance, and consequence-middleware tools to MCP-compatible runtimes. Now includes Acceptance Gate tools — because verification is not acceptance — and the MCP consequence-middleware tool that lets an agent ask the gate before an output becomes consequence. Works with Claude, Cursor, Cline, and growing.