Using an AI agent? Start here
Your coding agent can do the whole setup: find your usage records, write meterproof.yml, run the check and explain the report. Two things stay with you: creating the Stripe key, and confirming any payment.
1. Paste this into your agent
Run it from your app's repository.
Set up meterproof for this repository. Read https://meterproof.vibefrontier.com/llms.txt first.
1. Find where this app records billable usage and how it maps customers to Stripe customer ids.
2. Write meterproof.yml (the generate_config MCP tool or /api/config-template can draft it).
3. Ask me to create a Stripe restricted key with Read on Billing meters, Billing meter events, Prices and Subscriptions, and to export it as STRIPE_API_KEY. Never ask me to paste it here.
4. Run `meterproof check` and explain each problem.
5. Add the scheduled GitHub Action from the docs.
Do not change anything in Stripe.
2. Connect the MCP server (optional)
Remote MCP over Streamable HTTP at https://meterproof.vibefrontier.com/mcp. No sign-in is needed for the setup tools.
claude mcp add --transport http meterproof https://meterproof.vibefrontier.com/mcp
| Tool | What it does | Needs |
|---|---|---|
get_setup_guide | Setup steps and the exact Stripe key permissions | Nothing |
generate_config | Drafts meterproof.yml from your meter id, ledger type, column names and mapping | Nothing |
start_checkout | Returns a Stripe Checkout link for the founding pilot. You open it and pay; the agent never sees card details. | Your email |
get_account | Subscription status and renewal date | Account key |
open_billing_portal | A Stripe billing portal link to update payment or cancel | Account key |
rotate_token | Replaces the account key and revokes the old one | Account key |
3. Or use the REST API
The same operations as plain HTTP, described in /openapi.json:
GET /api/config-template?meter_id=…&ledger=postgres&mapping=csvreturns ameterproof.yml.POST /api/checkoutwith{"email": "…", "source": "agent"}returns a Checkout link for the person to open.GET /api/account,POST /api/billing-portal,POST /api/tokens/rotateandPOST /api/tokens/revoketakeAuthorization: Bearer mp_….
Account keys
After checkout, the welcome page shows an account key once. It lets you or your agent check the subscription and open the billing portal. It can't see your usage data, which never reaches us. Replace it on the account page or with rotate_token; the old key stops working at once.
Rules for agents
- Never ask for or handle a Stripe secret key in chat. The person creates a restricted, read-only key and sets it as an environment variable or CI secret.
- meterproof only reads Stripe. Don't send, cancel or adjust meter events on the person's behalf without asking them first.
- Payments are confirmed by the person on Stripe's own page.
A ready instructions file for Claude and other agents: /agents/SKILL.md.