Niches · Payment & monetisation platforms
Record usage and bill customers for it
Two or three companies' docs show a full fit.
What counts as done
Each 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.
Measured, for our own tests: aggregates match the events sent. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: bill customers per token
, track usage and invoice monthly
, add usage-based pricing
, how much did this customer use
Does the job 3
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Metronome B 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. source |
| Orb BB 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. source |
| Paid C 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. source |
Does the job, with a limit 2
It 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.
| Listing | Why |
|---|---|
| Lago C 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). source |
| Stripe API + MCP AA 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). source |
Doesn't do this job 11
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Adyen MCP server B Adyen N.V. | The server covers Checkout sessions, payment links, modifications and Management reads; it has no usage metering or invoicing. source |
| ATXP E Circuit & Chisel, Inc. | No usage metering or invoicing for a seller's customers; ATXP charges per call from agent balances. source |
| Circle Gateway Nanopayments BB Circle Technology Services, LLC | Per-request payments settled in batches; no usage metering or invoices. source |
| Crossmint API + Docs MCP B Crossmint, Inc. | No usage metering or invoicing product. source |
| FluxA AgentMarket D 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. source |
| Nevermined API + MCP B Nevermined AG | Nevermined sells payment plans and credits per request; no usage event ingestion with invoices per billing period was found. source |
| Payman Genie MCP D 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. source |
| PayPal MCP server C PayPal, Inc. | Invoices and subscription plans exist, but no usage event ingestion or metered billing tool. source |
| Skyfire API + MCP E Skyfire Systems Inc. | No usage metering or invoices; sellers charge committed tokens. source |
| Tempo BB Tempo Labs Inc. | Tempo is a chain; its microtransactions guide leaves usage metering and invoices to the application, with no ingestion or invoice service. source |
| TermiX AACP F TermiX | No usage metering or invoices; orders settle through escrow. source |
What stops agents finishing
- events accepted but never aggregated
- a cap on prices per subscription below the number of metered dimensions
- cached tokens not counted
Around it
Before: inference.log-usage, agent-observability.cost-report. After: accounting.sync-invoice, email.send-invoice.
Where this comes from
Weight 22 of 100 in Payment & monetisation platforms: 5 of 23 accounts (acc-01 to acc-05); builders charging for AI usage wrote the most first-hand reports
The same as data: /api/v1/use-cases/payment-platforms.meter-and-invoice.json, or the MCP tool get_use_case with id payment-platforms.meter-and-invoice. Other jobs in this category: /api/v1/niches?category=payment-platforms.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.