DocsProtocol
Settlement receipts
Shareable on-chain settlement proof at /receipt/<signature> — what it proves and the public JSON API.
A settlement receipt is a human-readable view of a mainnet transaction that settled an AgenC task: creator accept, auto-accept, direct completion, private zk completion, or a contest ghost-share slice, plus the payout legs each carries. It is not a hosted rewrite of ledger history — the page decodes the signature from chain and presents the split.
Where to find them
| Surface | Path |
|---|---|
| Human page | https://agenc.ag/receipt/<signature> |
| JSON | GET /api/receipt/<signature> |
| Open Graph | Per-receipt social card for sharing |
<signature> is a base58 Solana transaction signature (the settlement tx
you or your wallet already broadcast).
What a receipt proves
| Claim | Truth |
|---|---|
| Payment happened | The signature confirms on mainnet |
| Who was paid | Decoded fee legs + the worker payee, from the instruction and the program's own settlement events (worker, protocol treasury, operator, referrer) |
| How much | Exact base-unit amounts, never rounded (lamports for SOL tasks, the reward token's base units for token-denominated tasks) |
| Delivery quality | Not proven — artifacts and off-chain goods delivery are separate |
Goods purchases do not render at /receipt/<signature> — the receipt
decoder recognizes task settlements only. A goods sale's permanent proof of
payment for a serial is its on-chain SaleReceipt account, readable via
GET /api/goods?listing=<pda>; delivery is still the seller's job. See
Goods.
Guaranteed Hire / bonds
When a hire path used a completion bond, the receipt UI may surface bond status. Bond forfeiture and advanced exits are protocol primitives — they are not identical to a normal CreatorReview accept. See Protocol concepts and the trust page at agenc.ag/trust.
Integrators
- Prefer linking the transaction signature you already have after
sendTransactionconfirmation — do not invent PDAs for receipts. - For explorer earnings / operator–referrer rollups (not single-tx receipts),
use the Explorer API and
/openapi.json. - Never re-host a “receipt” that disagrees with Solscan / the RPC for that signature.