OpenMeter MCP. Automate billing and usage tracking for your AI platform.

You use OpenMeter to run usage-based billing logic right through your AI client. It handles the whole customer life cycle—from defining what gets charged to taking the cash. You don't need some clunky dashboard; you just call the tool.

Defining Your System and Resources
When you start, you gotta define what counts as usage. Use create_feature to register a new resource that needs tracking in your billing system. Then, if you’re dealing with multiple entities tied to that feature, use upsert_subjects or delete_subject. The upsert_subjects tool lets you update or add whole batches of subject records at once.

If you gotta fix data or clean up an old entry, call delete_subject by its unique internal key.

Managing Customers and Usage Tracking
To get started with a new user, you hit the gas on billing setup by calling create_customer, which creates that billable record in your metering system. Need to check what a customer's current status is? Just call get_customer using their ID or external key; it pulls all their usage and billing details right up.

The core of tracking is the ingest_event tool: you send raw data—like 150 tokens used or how many API calls were made—and that tool immediately records that specific usage event, keeping your consumption totals accurate. To set hard limits for a customer on a feature, use create_entitlement. This sets up the specific quota or access rights they're allowed.

Billing and Payment Orchestration
When it comes to money, OpenMeter handles all the complexity. You link customers to recurring charges by calling create_subscription, which manages their entire billing cycle. If you need them to pay now for a one-time service or renew immediately, use create_stripe_checkout to start that payment session on Stripe.

These tools manage collecting funds and starting paid subscriptions right from your agent’s workflow. You can also define the specific access rules by calling create_feature first, then linking those rights to an existing customer via create_entitlement. If you need a brand new billing structure or service that wasn't planned for, run through create_feature to register it.

The Workflow in Action
Your agent acts like your dedicated billing specialist. You let the client call get_customer to verify data. Then, when usage happens, you fire off an ingest_event. The system uses that event count and compares it against the limits set up by a prior call to create_entitlement. If everything looks good, you can then initiate the whole payment process with create_stripe_checkout, or if they're on a recurring plan, you trigger create_subscription.