{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/payment-platforms.meter-and-invoice/",
    "json": "https://www.anchorterminal.com/niches/payment-platforms.meter-and-invoice/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/payment-platforms.meter-and-invoice/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/payment-platforms.meter-and-invoice/index.min.md"
  },
  "markdown": "Two or three companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 3 | 1 | 34 | 22 | 5 |\n\n## What counts as done\n\nEach event is counted once (deduplicated by a stable id), the invoice shows the right period and line items for every metered dimension, and current usage can be read back by API.\n\nMeasured, for our own tests: aggregates match the events sent.\n\nHow agents ask for it: bill customers per token; track usage and invoice monthly; add usage-based pricing; how much did this customer use\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Metronome (Stripe, LLC)**: transaction_id deduplicates with a 34-day window, events backdate 34 days, invoices and invoice breakdowns are listed by API and usage is read back by the usage endpoints. The token billing guide (public preview) meters input, cached input, cached write and output tokens.\n- **Orb (Orb, Inc.)**: Per-event idempotency keys stop duplicates within the account grace period, batches take 500 events at 200,000 a minute by default, and subscription usage, costs and upcoming invoices are readable by API and through the MCP server.\n- **Paid (Agent Paid Limited)**: Bulk signals take an idempotencyKey and the response counts ingested, duplicates and voided; meters build on signals, invoices and invoice lines are listed by API, and credit balances, pending consumption and signal summaries read usage back.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Lago (Get Lago Corp.)**: Events deduplicate on transaction_id, batches take 100, filters price one metric per model, and current usage is read by API. On ClickHouse a retry without the same timestamp bills twice, and open issue 771 reports wrong invoice periods after an extended trial (acc-05).\n- **Stripe API + MCP (Stripe, LLC)**: Meter events take a caller identifier, aggregate asynchronously and are read back from meter event summaries. A subscription holds 20 items, which broke per-token billing across models (acc-01), and Stripe's token meter undercounted Anthropic cache tokens and was retired unfixed (acc-02).\n\n- not this job: Adyen MCP server (Adyen N.V.): The server covers Checkout sessions, payment links, modifications and Management reads; it has no usage metering or invoicing.\n- not this job: ATXP (Circuit \u0026 Chisel, Inc.): No usage metering or invoicing for a seller's customers; ATXP charges per call from agent balances.\n- not this job: Circle Gateway Nanopayments (Circle Technology Services, LLC): Per-request payments settled in batches; no usage metering or invoices.\n- not this job: Crossmint API + Docs MCP (Crossmint, Inc.): No usage metering or invoicing product.\n- not this job: FluxA AgentMarket (FluxA Technology Pte. Ltd.): AgentMarket meters its own catalogue calls against a buyer's Balance; it has no usage billing for a seller's customers.\n- not this job: Nevermined API + MCP (Nevermined AG): Nevermined sells payment plans and credits per request; no usage event ingestion with invoices per billing period was found.\n- not this job: Payman Genie MCP (Payman AI, Inc.): The bridge exposes one natural-language tool, ask_genie, acting on the person's own connected finance accounts; nothing for metering a seller's customers.\n- not this job: PayPal MCP server (PayPal, Inc.): Invoices and subscription plans exist, but no usage event ingestion or metered billing tool.\n- not this job: Skyfire API + MCP (Skyfire Systems Inc.): No usage metering or invoices; sellers charge committed tokens.\n- not this job: Tempo (Tempo Labs Inc.): Tempo is a chain; its microtransactions guide leaves usage metering and invoices to the application, with no ingestion or invoice service.\n- not this job: TermiX AACP (TermiX): No usage metering or invoices; orders settle through escrow.\n\n## What stops agents finishing\n\n- events accepted but never aggregated\n- a cap on prices per subscription below the number of metered dimensions\n- cached tokens not counted\n\n## Around it\n\nBefore: inference.log-usage, agent-observability.cost-report. After: accounting.sync-invoice, email.send-invoice.\n\n## Where this comes from\n\nWeight 22 of 100 in Payment \u0026 monetisation platforms: 5 of 23 accounts (acc-01 to acc-05); builders charging for AI usage wrote the most first-hand reports\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/payment-platforms.meter-and-invoice.json, or the MCP tool get_use_case with id payment-platforms.meter-and-invoice. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "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"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Record usage and bill customers for it",
        "url": ""
      }
    ],
    "description": "Record usage and bill customers for it: 3 companies fully do it, 1 with a limit, 34 carry the tag. Every listing in Payment \u0026 monetisation platforms with the reason and a source.",
    "facts": null,
    "h1": "Record usage and bill customers for it",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/payment-platforms.meter-and-invoice/",
    "published": "",
    "section": "agents",
    "title": "Record usage and bill customers for it: who does it | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/payment-platforms.meter-and-invoice/"
  },
  "tokens": {
    "markdown": 1350,
    "slim": 230
  },
  "version": 1
}
