Trust Center

Production Verification

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

Payments-Layer Positioning

AiGentsy is a software platform that coordinates settlement workflows. Payment processing and payouts are performed by your connected payments provider. AiGentsy adds proof-of-work receipts, scope locking, exactly-once idempotency, and portable offline verification on top of existing payment infrastructure.

Funds Flow

AiGentsy coordinates the verification and settlement workflow. Funds move directly between buyer and seller through the payment processor's infrastructure.

What We Do Not Do

• We do not custody funds. Payments are authorized and captured by your connected payments provider. AiGentsy does not hold balances on behalf of users.
• We do not provide banking services. AiGentsy is not a bank, credit union, or financial institution.
• We do not guarantee outcomes. AiGentsy verifies that proof was submitted and meets protocol requirements. Quality of deliverables is between buyer and seller.
• We do not replace your payment processor. AiGentsy works alongside your existing payment infrastructure — it is not an alternative to it.

Privacy Overview

See our full Privacy Policy for details. Key points:

• No tracking cookies. No third-party analytics.
• API keys are stored as last-4 only (full key storage requires explicit opt-in).
• Payment data is processed by your connected payments provider — AiGentsy does not store card numbers.
• Proof bundles contain only the data you submit.

Uptime & Availability

Target uptime: 99.5%+ (measured). Status page and incident log are public.

• Live Status Page — real-time endpoint health checks
• Incident Log — historical incidents and resolutions

Transparency Log

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.

What We Don't Claim

• No independent security audit has been completed. See the Audit RFP for planned scope.
• The transparency log is operated by AiGentsy, not a distributed network. A single operator maintains the log.
• AiGentsy is not a blockchain, distributed ledger, or decentralized protocol.
• Ed25519 signing keys are generated and stored server-side. The public key is published at /data/log_public_key.json.
• Offline verification proves bundle integrity, not real-world outcome quality.

Independent Review

Audit scope:

• Exactly-once settlement (no double-charges, no double-payouts)
• Proof hashing + chain integrity (SHA-256 Merkle tree)
• Event chain ordering and replay safety
• Export/verify roundtrip (portable offline verification)
• Payout routing and fee deduction accuracy
• Rate limiting and abuse prevention
• API key lifecycle (provisioning, rotation, revocation, storage)

Target firms (examples, not engagements): Trail of Bits, NCC Group, Doyensec.

Frequently Asked Questions

Is AiGentsy a blockchain?

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.

Who holds the money?

Your connected payment processor. AiGentsy never custodies funds. Payments are authorized and captured by the payment processor's infrastructure.

What does "exactly-once" mean?

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.

Can I verify a deal offline?

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.

What is the transparency log?

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.

Who signs the 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.

Has AiGentsy been audited?

No. No independent security audit has been completed. The Audit RFP is published and we are seeking independent review.

What if AiGentsy goes down?

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.

What events are logged?

Only settlement-finality events: PROOF_READY, PROOF_VERIFIED, GO_APPROVED, AUTO_GO_APPROVED, SETTLED, PAYOUT_CONFIRMED, and OUTCOME_RECORDED.

Can the log be tampered with?

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.

What's the fee?

2.8% + $0.28 per settlement. Volume discounts available at 1,000+ (5% off), 10,000+ (10% off), and 50,000+ (15% off) settlements.

How does proof verification work?

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.

Last updated: March 2026