API Meter counts API requests per customer, endpoint and plan, and lets an assistant sign up an API, get ingest snippets and read or export usage.
What you can do
Sign up an API and receive its slug, ingest key, dashboard key and proxy URL
Get copy-paste ingest code for express, hono, fastapi, flask, django, go or curl
Read monthly usage grouped by customer, endpoint or plan, including an agent-traffic bucket
Export billing-ready usage rows as JSON or CSV, at detail or customer level
When to use it
Useful when you want an assistant to set up per-customer request metering for an API and then check or export monthly usage for billing or reporting, without leaving the chat.
Requirements
Remote Streamable HTTP endpoint, or the npm package api-meter-mcp run with npx as a stdio bridge. No OAuth or session. The dashboard key (msd_...) is needed for get_usage and export_usage; it is returned once by create_account.
Before you install
create_account returns an ingest key and a dashboard key shown only once, so store them immediately. The dashboard key grants usage access and should only be given to agents you trust. Signups are limited to 5 per hour per network. AI agent traffic is counted and billed like normal requests. Paid plans are in beta with Stripe test mode.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Surface-ops%2Fapi-meter/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Sign up an API for API Meter (free to 250K requests/month). Returns the slug, ingest key, dashboard key and proxy URL. Keys are shown once: store them. Limited to 5 signups per hour per network.
Copy-paste server code that reports each request (method, route, status, latency, customer, plan) to API Meter. Batched, fail-open, never blocks your API.
Parametersslugframeworkrequired
get_usage
Get usage summary
Monthly (UTC) usage for one API, grouped by customer, endpoint or plan. Includes an agent bucket: requests whose plan label ends in '-agent' (AI agent / bot traffic, counted and billed like any request).
Billing-ready monthly usage rows (same as /api/export): view=detail (customer x plan x method x endpoint) or view=customers. Returns JSON rows, or CSV text with format=csv.
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.