{
  "listings": [
    {
      "slug": "ack-pay",
      "name": "ACK-Pay (Agent Commerce Kit)",
      "company": "Catena Labs, Inc.",
      "grade": "D",
      "fit": "caveat",
      "why": "Receipts are W3C Verifiable Credentials signed by a Receipt Service and verifiable offline against its DID. The docs show an Ed25519Signature2020 proof while the verifier accepts only JwtProof2020 (acc-24, open), and there are no settlement status codes or idempotency key.",
      "source": "https://www.agentcommercekit.com/ack-pay/receipt-verification.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/ack-pay"
    },
    {
      "slug": "l402",
      "name": "L402",
      "company": "Lightning Labs, Inc.",
      "grade": "C",
      "fit": "caveat",
      "why": "The preimage proves payment to anyone (sha256 matches the payment hash), and lnget caches tokens per domain so a later call reuses the paid credential. Handling of an in-flight or timed-out Lightning payment before retrying is not documented.",
      "source": "https://github.com/lightninglabs/L402/blob/master/protocol-specification.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/l402"
    },
    {
      "slug": "mpp",
      "name": "Machine Payments Protocol (MPP)",
      "company": "Tempo and Stripe",
      "grade": "A",
      "fit": "caveat",
      "why": "Payment proofs MUST be single-use, concurrent requests with one credential MUST settle once, and Payment-Receipt carries status, method, timestamp and a tx hash or invoice reference. Receipts exist only on success, and Idempotency-Key for paid POSTs is a SHOULD, so a lookup before re-paying depends on the server.",
      "source": "https://github.com/tempoxyz/mpp-specs/blob/main/specs/core/draft-httpauth-payment-01.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/mpp"
    },
    {
      "slug": "x402",
      "name": "x402",
      "company": "x402, a Series of LF Projects, LLC",
      "grade": "A",
      "fit": "caveat",
      "why": "SettleResponse carries success, errorReason and the transaction hash, settlement_pending is non-terminal with the broadcast hash required, and the payment-identifier extension is an idempotency key. The extension is optional, and facilitator-unavailability semantics are undefined (acc-25).",
      "source": "https://github.com/x402-foundation/x402/blob/main/specs/x402-specification-v2.md",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/x402"
    }
  ],
  "marks": "yes: the docs show it does the job as the success test says. caveat: it does the job with a limit an agent should know. no: it doesn't do this job. unchecked: we couldn't read it.",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "useCase": {
    "accounts": 3,
    "after": [
      "agent-observability.cost-report",
      "accounting.record-expense"
    ],
    "area": "payments",
    "asks": [
      "did that payment go through",
      "retry without paying twice",
      "show me the receipts for this run",
      "prove I paid for this"
    ],
    "before": [
      "pay-per-call.pay-and-retry"
    ],
    "blockers": [
      "no idempotency key or replay rule, so a sequential retry pays twice",
      "receipt format in docs differs from what the verifier accepts"
    ],
    "capabilities": [
      "payments.protocol",
      "payments.x402",
      "payments.lightning"
    ],
    "category": "pay-per-call",
    "categoryName": "Pay-per-call protocols",
    "checked": "2026-11-15",
    "companies": {
      "fit": 0,
      "fitWithLimit": 4,
      "tagged": 24
    },
    "competition": "none",
    "fits": null,
    "fitsWithLimit": [
      "ack-pay",
      "l402",
      "mpp",
      "x402"
    ],
    "id": "pay-per-call.settle-and-prove",
    "listings": {
      "caveat": 4,
      "no": 0,
      "notRead": 0,
      "tagged": 27,
      "unchecked": 0,
      "yes": 0
    },
    "name": "Confirm a payment settled, recover an unknown outcome and keep a receipt",
    "status": "draft",
    "success": "The agent can tell from documented fields whether the payment settled, look it up by transaction or idempotency key before paying again, and keep a receipt a third party can verify (transaction hash, preimage or signed credential).",
    "url": "https://www.anchorterminal.com/api/v1/use-cases/pay-per-call.settle-and-prove.json",
    "weight": 12,
    "weightBasis": "3 of 25 accounts (acc-17, acc-24, acc-25), two of them implementer issues; set low because few users report reaching this step"
  }
}
