Niches · Payment & monetisation platforms

Look up payments, balances and transactions

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
8companies, fit with a limit
27companies carry the tag
8share of the category's work
2first-hand accounts

What counts as done

Matching records returned with ids, amounts, status and dates, across every account the operator connected, from read-only calls with a read-only key.

How agents ask for it: did the customer pay, show last week's payments, what is our balance, find the charge for this email

Does the job, with a limit 9

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.

ListingWhy
Circle Gateway Nanopayments BB
Circle Technology Services, LLC
searchTransfers and getTransferById return each transfer with status (completed, failed) for reconciliation. This covers the seller's Gateway transfers only, and no read-only key scope was found. source
Lago C
Get Lago Corp.
list_payments, list_invoices, list_fees and a read-only SQL analytics tool return records, but one organisation per key and no read-only key on the free edition. source
Metronome B
Stripe, LLC
Invoices list with status and tokens can be scoped read-only or sandbox-only, but scoping needs a support request and payments themselves sit with the processor. source
Nevermined API + MCP B
Nevermined AG
list_payments, payment_summary, get_budget and wallet_balance read the buyer's Router ledger without moving money, but this is one account's buyer ledger, not merchant records across connected accounts. source
Orb BB
Orb, Inc.
list_invoices and fetch_invoice return status and amounts under a read-scoped key, but one key reaches one account and card payments themselves sit with Stripe or Adyen. source
Paid C
Agent Paid Limited
Invoices list by API and the MCP server runs with the person's organisation role, so viewers get read-only access; one organisation per connection and payment records stay in Stripe. source
PayPal MCP server C
PayPal, Inc.
list_transaction, get_order, get_merchant_insights and list_invoices return records, but each server runs on one account's access token and no read-only mode or scope is documented; the remote OAuth path was failing (acc-10). source
Stripe API + MCP AA
Stripe, LLC
stripe_api_read covers charges, payment intents, balance and refunds, OAuth can grant several live accounts (issue 358 closed as supported), and agent API keys carry only chosen permissions. The open live-account greyed-out report (acc-06) can stop an OAuth connection reaching live data. source
Tempo BB
Tempo Labs Inc.
Transfers are public chain data, and the reconciliation guide points to the Tempo API, Goldsky or Allium for matching by account. The API reference was not opened this run, and its versioning page says endpoints may change. source

Couldn't check 1

The docs were closed to us, or silent. These carry no mark either way.

ListingWhy
Payman Genie MCP D
Payman AI, Inc.
Docs host unreachable; the README says only that read-only access is a self-service grant, not what ask_genie can query.

Doesn't do this job 6

Listings in the category that do something else, with the reason.

ListingWhy
Adyen MCP server B
Adyen N.V.
No tool lists or searches payments or balances; reads cover session results, payment link status, merchant accounts, terminals, webhooks and users. source
ATXP E
Circuit & Chisel, Inc.
Usage and earnings are viewed in the account portal; no payment search API for merchant accounts was found. source
Crossmint API + Docs MCP B
Crossmint, Inc.
No merchant payment search across accounts; wallet activity is per wallet. source
FluxA AgentMarket D
FluxA Technology Pte. Ltd.
Only the buyer's own Balance ledger is readable; no merchant payment search. source
Skyfire API + MCP E
Skyfire Systems Inc.
Token and charge details are inspected in the dashboard; no payment search API across merchant accounts was found. source
TermiX AACP F
TermiX
No merchant payment search across accounts. source

What stops agents finishing

  • one account per OAuth session
  • connection fails before any read

Around it

Before: chat.user-question. After: spreadsheets.write-rows, payment-platforms.refund-and-dispute.

Where this comes from

Weight 8 of 100 in Payment & monetisation platforms: 2 of 23 accounts (acc-10, acc-15); likely under-reported, since read questions rarely produce issues

The same as data: /api/v1/use-cases/payment-platforms.look-up-payments.json, or the MCP tool get_use_case with id payment-platforms.look-up-payments. Other jobs in this category: /api/v1/niches?category=payment-platforms.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

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.