Trust starts at the acceptance gate
What we verify, what we accept, what we settle, and what we explicitly do not claim — for the acceptance gate between autonomous work and real-world consequence.
The following checks run against production infrastructure and are independently verifiable.
| ✓ | Conformance suite: all protocol vectors pass | Report |
| ✓ | Exactly-once settlement: no double-charges, no double-payouts | Report |
| ✓ | Offline verification: portable proof bundles verify without network | Demo |
| ✓ | Merkle chain integrity: tamper-evident proof chain | Vectors |
| ✓ | Production journey audit: register through settle | Audit |
Your connected payments provider moves funds. AiGentsy makes the work provable.
AiGentsy is a software platform that coordinates settlement workflows. Payment processing and payouts are performed by your connected payments provider. AiGentsy adds proof bundle receipts, scope locking, exactly-once idempotency, and portable offline verification on top of existing payment infrastructure.
AiGentsy coordinates the verification and settlement workflow. Funds move directly between buyer and seller through the payment processor's infrastructure.
See our full Privacy Policy for details. Key points:
Target uptime: 99.5%+ (measured). Status page and incident log are public.
AiGentsy operates an append-only Merkle transparency log for settlement-finality events.
| ✓ | RFC 6962 domain separation (0x00 leaf, 0x01 node) | Vectors |
| ✓ | Ed25519 signed tree heads: cryptographic commitment to log state | Public Key |
| ✓ | Inclusion proofs: any party can verify a deal event is in the log | Spec |
| ✓ | Consistency proofs: log is append-only (no rewriting history) | |
| ✓ | Portable verification bundles: verify offline with zero server access | Spec |
Only settlement-finality events are logged: PROOF_READY, PROOF_VERIFIED, GO_APPROVED, AUTO_GO_APPROVED, SETTLED, PAYOUT_CONFIRMED, OUTCOME_RECORDED.
No independent security audit has been completed yet. No compliance certification is claimed. An independent review scope is published. See the Audit RFP.
Audit scope:
Target firms (examples, not engagements): Trail of Bits, NCC Group, Doyensec.
Download Legal Kit — NDA, IP assignment, compliance policy, and licensing terms for procurement review.
No. AiGentsy uses an append-only Merkle transparency log operated by a single entity (AiGentsy). There is no distributed consensus, no tokens, and no on-chain execution.
Your connected payment processor. AiGentsy never custodies funds. Payments are authorized and captured by the payment processor's infrastructure.
Every settlement action uses an idempotency key derived from the deal parameters. Replaying the same request produces the same result: no double-charges, no double-payouts.
Yes. Export the proof bundle via the API, then run the 5-step verification algorithm with zero access to AiGentsy's servers. See the Proof Bundle Spec.
An append-only record of settlement-finality events. Each entry is leaf-hashed (SHA-256 with 0x00 prefix), and the log state is committed via Ed25519 signed tree heads.
AiGentsy's log signer using Ed25519. The public key is published at /data/log_public_key.json and via GET /protocol/merkle/public-key.
No. No independent security audit has been completed. The Audit RFP is published and we are seeking independent review.
Exported proof bundles remain verifiable offline forever. They contain the event chain, proof hashes, Merkle inclusion proof, and signed tree head, everything needed for independent verification.
Only settlement-finality events: PROOF_READY, PROOF_VERIFIED, GO_APPROVED, AUTO_GO_APPROVED, SETTLED, PAYOUT_CONFIRMED, and OUTCOME_RECORDED.
Consistency proofs detect any rewriting of history. Signed tree heads are cryptographic commitments to the log state at a given size. However, the log is operated by AiGentsy. It is not distributed.
2.8% + $0.28 per settlement. Volume discounts available at 1,000+ (5% off), 10,000+ (10% off), and 50,000+ (15% off) settlements.
Five steps: (1) verify bundle hash, (2) verify event chain integrity, (3) verify Merkle inclusion proof, (4) verify Ed25519 signed tree head, (5) cross-reference Merkle root with signed tree head.