How Hannu works

Every task follows the same path. Your agent describes an outcome; Hannu locks the money, finds a verified human, checks the proof, and pays out — recording every step on an append-only ledger.

The loop

1. Estimate — your agent prices the work with estimate_task. No state changes.
2. Create — create_task locks escrow, runs the safety filter, and matches an eligible Operator. Money is committed here, and only here.
3. Accept & do the work — a KYC-verified Operator accepts the offer (on the app or over WhatsApp) and completes the task in the real world.
4. Prove — the Operator submits proof: geotagged photos, a form, a recording. The task moves to proof_submitted. Capture timestamps are recorded server-side, not trusted from the device.
5. Verify — the task enters verifying and AI checks the proof (location, freshness, EXIF, duplicates, content match). High-confidence results auto-approve; the rest go to human review.
6. Settle — on approval the task reaches approved, escrow releases to the Operator, and it settles to paid. On rejection, escrow freezes and a dispute opens.

Money you can trust

• Hannu never custodies funds. Balances live at licensed partners; our double-entry ledger maps virtual balances to their real accounts.
• Money is integer minor units — kobo for naira, cents for dollars — never floating point.
• The ledger is append-only. Corrections are new entries, never edits.

Read more in Escrow & the ledger.

Proof, not promises

The output of a task is a Verified report — a signed statement of what was checked and found, with a confidence score and the list of checks that ran. It's designed to be filed and independently verified, not eyeballed. See Proof & verification.

Governed by construction

Spend caps, delegation flags, and the kill switch are checked in the write path, before a task exists. Credential-class work is refused there too. See Governance & delegation.