Welcome to MeterGate, the API marketplace for you and your AI agents

Find APIs, pay per call, and your agent only spends what you allow.

Start for free How it works

The spending cap takes effect before the call, not on the invoice

Per key and period. Once reached, the call does not go through at all — it is not billed afterwards.

The remaining budget is in every response header. An agent that reads it does not run blindly into the cap but stops in time.

Your agent can drive MeterGate directly — via MCP server, subject to the same caps you set on the key.

The response at the cap — real, not staged:

HTTP/1.1 402 Payment Required
X-Budget-Remaining-Cents: 0

{
  "error": "budget_exceeded",
  "retryable": true,
  "retry_at": "2026-09-30T22:00:00.000Z",
  "action_url": "/keys"
}

The timestamp is this installation's real reset time; the error code comes from the same catalog the gateway answers from.

Every billed call ends up on an invoice under § 14 UStG

One invoice per provider, all under § 14 UStG, all from one place — input-tax deductible, instead of twelve foreign receipts your accounting will not accept.

E-invoice per EN 16931: the structured part sits inside the PDF, including an itemised record of every billed call.

From 01.01.2028 the structured format is mandatory for domestic B2B (§ 27 (38) UStG).

The provider never writes an invoice

85 % of revenue, settled by self-billing invoice under § 14 (2) UStG.

The VAT ID is checked against VIES before a product appears in the catalog. Whoever loses it disappears from it — not only at the next settlement.

Document type from the norm: a self-billing invoice.

And yes, there is a catalog

It is usable without an account and stays reachable. What we build on top of it is the brake and the documentation trail.

Browse catalog

Give your agent a spending cap.

Create an account, generate a key, set a spending cap — in minutes, free of charge.

Get started free