Build on MeterCall

Ship fast #

What is MeterCall? #

MeterCall is a universal API gateway for software. Every time your app (or an AI agent acting on your behalf) calls an external service, that call goes through MeterCall. In return you get:

• One contract, 2,000+ providers. Stripe, Twilio, OpenAI, Bloomberg, Notion, Shopify, and everything else — all behind a single JSON envelope.
• Metered billing. Pay per call, per token, per megabyte, or per whatever the module charges.
• Agent-pay. Any client (human or machine) can make a call. When payment is required, we answer 402 Payment Required and your client (or agent wallet) signs a payment header.
• Receipts & audit. Every call produces a signed receipt you can verify.

Your first call #

Every authenticated request uses your API key in the Authorization header. Here is the canonical call:

POST https://metercall.ai/v1/module/stripe-replacement/call
Authorization: Bearer mc_live_abc123...
Content-Type: application/json

{
  "action": "charge",
  "amount": 4900,
  "currency": "usd",
  "source": "tok_visa"
}

Ready to try it? Jump into the quickstart.

Design principles #

• Stateless REST. Every request is self-contained. No sticky sessions.
• JSON everywhere. Request and response bodies are JSON (UTF-8).
• Idempotent writes. All POST endpoints accept an Idempotency-Key header.
• Signed receipts. Every billable call returns an X-Receipt-Sig header (Ed25519) you can verify against our public key at /.well-known/metercall-pubkey.
• 402-first. If your caller has no balance or no key, MeterCall replies with 402 and a WWW-Authenticate: X-Payment header.

Base URL #

https://metercall.ai

All endpoints in this documentation are relative to this host. Testnet modules are available on /v1/test/....

Support #

Need help? hi@metercall.ai for API issues, the builder directory if you want to ship a module and earn revenue share, or GitHub for SDK bugs.