ElevenLabs, Sept 2026106%of the monthly credit limit, overage billing on
Neon, Oct 2026$93/moon pace from one scheduler, budget was $50
Railway, Oct 20266 pausedprojects stopped by an expired trial
After Mepa80/mindatabase churn, down from 251 a minute
What Mepa8 is
Mepa8 is a vendor cost and health monitor for teams of one to ten people who build on metered APIs. The name stands for Monitor Every Paid API. The 8 is an infinity standing on end, because the watching never stops. You paste a read-only key for each vendor, set a budget, and the board does the rest: cost so far, cost on pace for the month, usage against limits, and the one alert that matters when a number crosses a line.
It exists because the invoices kept winning. In one month our own accounts produced three surprises that no dashboard had flagged, and the incident log tells each one with the real numbers. A monitor that only reads subscription totals would have said “over the limit” and nothing else. Mepa8 says which product, which key, which day.
Three questions, answered on one screen
What is it costing?
Month to date where the vendor's API reports it, the on-pace figure for the full month, and a bar against the budget you set. Receipts fill the gap for vendors with no billing API.
Is it healthy?
Past-due status, usage closing in on a limit, a trial about to end, a deploy that never happened. Each check is written from an outage we actually had.
How do we turn it off?
Every vendor carries its kill recipe and blast radius. Kill is two steps with a single-use token, always reversible, never fired by a machine on its own.
Why the kill switch is two steps
A kill that fires on a single signal is how you take down your own phone lines at 2 a.m. because a usage API hiccupped. Mepa8 proposes first: it shows the blast radius and the exact steps, and issues a token that expires in 10 minutes. A person, or an agent you explicitly authorised, confirms. Every propose, confirm and restore lands in an audit log with who and when. Nothing is deleted by the kill flow, so restore always works.
“No alert, no agent and no schedule may kill a vendor on a single signal.”Mepa8 operating rule, written 2026-10-08
Your AI agent can run it too
Everything the screen does is a JSON call with the same rights, so the agent that spends your money can also watch it. The four calls below are the whole surface: read the board, re-run the checks, propose a kill, confirm it.
curl -s https://app.mepa8.com/api/board | jq '.totals'
curl -s -X POST https://app.mepa8.com/api/run -d '{"by":"agent"}'
curl -s -X POST https://app.mepa8.com/api/kill/propose -d '{"vendor":"heygen","by":"agent"}'
curl -s -X POST https://app.mepa8.com/api/kill/confirm -d '{"vendor":"heygen","token":"…","by":"agent"}'The hosted API opens with the Pro plan. Today Mepa8 runs on our own vendors first; the catalog says which vendors are fully wired and which are watched by receipt.
What it watches today
Twenty-one vendors are on our own board as of October 9, 2026. Four are Full tier, with cost, health and kill all by API: ElevenLabs, Neon, Railway and Cloudflare. Two are Watched: HeyGen and Vonage. The other fifteen are Manual, which means a budget, a kill recipe and an alert, with cost typed in from the receipt until the connector ships. A vendor moves up a tier only after a live test against a real account returns real cost and a kill was proven reversible.
Vendor rates change, so each catalog page links the vendor's own pricing page and says the date it was read. ElevenLabs, for example, sells plans from $6 to $990 a month and bills roughly one credit per character of speech, which is why a 1,000,000-character render shows up as a quarter of a 3.8-million-credit month.
Who it is for
A founder running voice agents on ElevenLabs and Twilio. A two-person shop with a Postgres on Neon, a backend on Railway and a front end on Cloudflare. Anyone who just gave an AI agent the ability to call a metered API in a loop. If your monthly bills come from eight to thirty vendors and nobody can say the total in under an hour, this is the board.
Questions people ask
Does Mepa8 store my vendor API keys?
The registry stores the name of the environment variable that holds a key, never the value. On the hosted plan keys are encrypted at rest, scoped read-only wherever the vendor allows it, and revocable from your side at any time. A vendor row that looks like it contains a secret is refused.
What happens to my vendors if Mepa8 goes down?
Nothing. Mepa8 only reads. Your vendors keep running, your keys keep working, and no kill is ever fired automatically. The only thing you lose during an outage is the alert, which is why the checks run on a schedule from two places on paid plans.
Which vendors are supported?
Twenty-one are on our own board today: four Full (ElevenLabs, Neon, Railway, Cloudflare), two Watched (HeyGen, Vonage) and fifteen Manual. The catalog lists each with its tier and what the tier means. New vendors join after a live test, not before.
How is this different from a cloud cost tool?
Cloud cost tools such as Vantage read AWS, Azure and GCP bills. SaaS spend tools such as Cledara track seat software for finance teams. Mepa8 is for usage-metered API vendors, the ElevenLabs and Neon kind, with a kill switch and an API an agent can drive. Read the pricing page for the comparison.
Sources
- ElevenLabs pricing — read 2026-10-08
- Neon pricing — read 2026-10-09
- Railway pricing — read 2026-10-09
Change log: October 9, 2026 — First published. Numbers come from our own accounts in September and October 2026.