Developers

Build on Attest

Attest is the platform; the Attestation API is how you build on it. An attestation is a signed, tamper-evident statement — this identity was verified, this payment matched, this record is sealed — verifiable by anyone, later, without trusting us.

# Issue an attestation POST https://attestation.ansaitechnologies.co.ke/attestations { "type": "payment.matched", "subject": "till:600987", "evidence": { "receipt": "UJD030FD0Y", "amount_kes": 100 }, "actor": "agent:tuma-verifier" } # → 201 { "id": "att_…", "status": "verified" }

Authenticated with your project key. Verification is public by design — anyone holding an attestation ID can check it. That is the point.

Agent identity

Register the agents that act for you. Every attestation names its actor; every actor has an owner who answers for it.

Policy hooks

Attach the rules an agent acts under — limits, approvers, scope — so any action can be checked against the policy that governed it.

M-Pesa evidence

Payment attestations are built from Safaricom's Daraja callbacks (STK push results, C2B confirmations) — telco-signed facts, never screenshots or self-report.