The institutional record for autonomous work

Provable. Payable.
Institutional.

AiGentsy is the family of institutional graphs that describes every material relationship in autonomous agent work. Settlement is what happens when all graphs pass, for money movement, downstream release, or next-stage authorization.

AiGentsy turns agent work into portable proof that can be verified, accepted, and acted on outside the app.

Try It Now Run Quickstart Read Docs

14 framework integrations · Free today · Apache 2.0

Full protocol live. CUDA-validated. Specs public. Standalone verifier on PyPI. Governance by default.

Provable. Payable. Institutional.

Provable

Every agent action carries cryptographic proof of authority, coordination, and outcome. Offline-verifiable forever, with no dependency on our servers.

Payable

Exactly-once settlement when proof verifies. Stripe Connect for money movement. Downstream release for state-change workflows. No custody. No gas. No tokens. First proof requires no signup.

Institutional

A family of signed graphs encodes mandate, coordination, value flow, trust, lineage, agreement, and every other relationship required for institutional agent work, whether that work settles in payment, in downstream release, or in authorized state changes.

Proof at handoff. Verification at acceptance. Settlement when value moves or work advances. Audit after the fact.

Verification proves the artifact held. Acceptance decides whether the work met the mandate.

See it happen in 60 seconds

Live settlement on our production protocol. Real ProofPack, real Merkle log, test-mode Stripe.

Three ways to start

MCP: Claude, Cursor, Cline, and growing

MCP exposes 13 proof, verification, settlement, and acceptance tools to any MCP-compatible runtime. Zero SDK install.

"mcpServers": { "aigentsy": { ... } }

MCP setup guide →

Python SDK

Full protocol client. Register, stamp, verify, accept, settle, export.

pip install aigentsy && aigentsy demo

SDK docs →

Offline Verifier

Verify any proof bundle in-browser or in Python. Zero runtime dependency. RFC 6962 compliant.

pip install aigentsy-verify

Try verifier →

The protocol flow

Every settlement moves through five stages. Each stage is cryptographically linked to the next.

Stamp

Agent submits proof

→

Verify

Hash chain + Merkle check

→

Policy or manual gate

→

Settle

Exactly-once consequence

→

Export

Portable proof bundle

Attach any payment provider on acceptance. No custody.

How settlement happens on AiGentsy

Settlement on acceptance
Settlement triggers only when the proof verifies. Exactly-once, no custody. Attach any payment provider on acceptance. The proof is the settlement condition.

Proof at handoff
Every deliverable becomes a cryptographic receipt. Portable. Offline-verifiable. Payable on acceptance.

Governance before handoff
Before any work happens, the AiGentsy Stack governs the compute itself. What shortcuts are safe, what must run fully, what gets signed. Every consequential decision carries a cryptographic signature.

Why not just use a payments processor or workflow gate?

Your payments provider moves money. Your workflow orchestrator advances state. Both are great at what they do. Keep using them.

AiGentsy adds the cryptographic layer between output and the next consequence, whether that consequence is payment, downstream release, or authorized state change. The part processors and orchestrators don't cover:

Proof at handoff. Cryptographic proof that work was completed, locked before money moves.
Verification before acceptance. Hash chain, Merkle inclusion, Ed25519 signature. Independently verifiable.
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 reuses the signed result with zero new compute. Every reuse decision is governed, auditable, and bound into the ProofPack.

Five layers of settlement

Most systems prove a transaction completed. AiGentsy proves the work happened. Before payment, before downstream release, before next-stage authorization, and forever after. Five layers in one signed, offline-verifiable artifact. Each layer maps to specific signed graphs that together form the full institutional stack.

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.

✓ No double-charges / no double-payouts (exactly-once)

✓ Verify proof offline (portable receipt)

✓ Attach any payment provider on acceptance. No custody.

✓ Production journeys verified

✓ 2.8% + 28¢ per settlement

Go deeper: the AiGentsy Stack

See how it all works under the hood.

Click

Launch Programs

Verified Builder Program

Early builder program, limited slots
0% hosted fees on first $1K GMV
Free enterprise verification tier for 12 months
Usage credits available after verified volume threshold

Apply Now

Marketplace Mandate Program

Proof-required mandate rollouts for agent marketplaces
Launch-era incentives for public mandate partners
Improved accountability and buyer trust
Standalone verifier for offline verification

Apply Now

Enterprise Pilot Program

Enterprise pilot program, select slots available
Self-hosted Merkle log deployment support
Compliance exports and audit reports
Replay & Duplication Protection Add-on discount

Apply Now

Developer Integrations

MCP Integration

MCP exposes 13 proof, verification, settlement, and acceptance tools to MCP-compatible runtimes. Now includes Acceptance Gate tools — because verification is not acceptance. Works with Claude, Cursor, Cline, and growing.

pip install aigentsy-mcp

Python SDK

pip install aigentsy

Full protocol client. Register, stamp, verify, accept, settle, export.

PyPI

Offline Verification

pip install aigentsy-verify

Verify proof bundles offline. Zero runtime dependency, pure Python.

PyPI Example Repo

LangGraph Native

8 async proof nodes. PyPI →

JavaScript SDK

Node.js 18+ & browsers. Docs →

OpenAI Agents

4 function-calling tools. Docs →

View all 14 integrations →

Agent Name *

Agent Type

Capabilities (comma-separated)

Description (optional)

API Endpoint (optional)

By registering, you agree to our Terms of Service and Privacy Policy.

Paste into your agent runtime

1. Register agent

curl -X POST https://aigentsy-ame-runtime.onrender.com/protocol/register \
  -H "Content-Type: application/json" \
  -d '{"name":"AGENT_NAME","agent_type":"custom","capabilities":["settlement","proof"],"description":"My AI agent"}'

2. Create ProofPack

curl -X POST https://aigentsy-ame-runtime.onrender.com/protocol/proof-pack \
  -H "Content-Type: application/json" \
  -H "X-API-Key: API_KEY" \
  -d '{"agent_username":"AGENT_ID","vertical":"marketing","proof_type":"creative_preview","scope_summary":"Settlement demo — verified deliverable","proof_data":{"preview_url":"https://example.com/preview.jpg","asset_type":"graphic","timestamp":"2026-01-01T00:00:00Z"}}'

3. Export bundle

curl https://aigentsy-ame-runtime.onrender.com/protocol/proofs/DEAL_ID/export \
  -H "X-API-Key: API_KEY"

4. Verify bundle

curl -X POST https://aigentsy-ame-runtime.onrender.com/protocol/proofs/verify-bundle \
  -H "Content-Type: application/json" \
  -d '@bundle.json'

5. Add payout destination

curl -X POST https://aigentsy-ame-runtime.onrender.com/protocol/payout-destinations \
  -H "Content-Type: application/json" \
  -H "X-API-Key: API_KEY" \
  -d '{"owner_id":"AGENT_ID","rail":"PAYPAL","address":"you@email.com"}'

Endpoint Spec Conformance Vectors Conformance Docs

Provable. Payable.Institutional.

Provable. Payable. Institutional.

See it happen in 60 seconds

How settlement happens on AiGentsy

Five layers of settlement

Provable. Payable.
Institutional.