For MCP Providers

You built an MCP server.
Tally helps you run it right.

Usage visibility is free. If you want to charge for access to your server, Tally handles the entire billing layer — you keep 90%.

Always free

Know exactly who is calling
your server and what it costs them.

The moment you instrument your MCP server with Tally, you get full usage visibility at no charge. Who is calling, how often, how many tokens they're consuming, and what that would cost them if you charged.

Free
Per-consumer call counts and token volumes — see exactly who is hammering your server and who isn't.
Usage attribution across call chains — which agent called your MCP, via which session, in which workflow.
Running cost estimate — what each consumer would owe you against any rate you set.
Complete audit trail — append-only, immutable, exportable at any time.

No credit card. No setup. Register your server, add the SDK, start seeing data. The ledger is always free.

Paid add-on

Start charging for your server.
Tally runs the credit layer.

Turn on monetisation and your consumers buy Platform Credits — prepaid units — in packages you define. Every invocation redeems credits deterministically against their balance. When they run out, service pauses cleanly. No debt. No awkward conversations.

You set the rate. You embed your margin inside the credit price. Tally runs the ledger and takes 10% of what consumers pay for credits. You keep 90%.

1

You set a credit burn rate for your service

e.g., 10 credits per API call, or 1 credit per 1,000 tokens. You decide what a credit is worth in your service context.

2

Consumers buy credits in advance

They purchase from packages you define — $50 starter, $250 standard, whatever tiers make sense. They prepay. Always.

3

Tally checks balance on every invocation

Before your server processes the call, Tally confirms the consumer has sufficient credits. The check is in the record layer — not in your execution path.

4

Credits are redeemed, balance is updated

Deterministic. No rounding surprises. Full ledger entry per redemption, exportable at any time.

5

Balance hits zero — service pauses cleanly

No debt created. No bill sent. The consumer tops up and resumes. You never carry financial risk.

Upgrade

Don't want to think about
payments at all?

Add managed billing and Tally handles the entire consumer-facing payment lifecycle — Stripe integration, the credit purchase flow, auto-replenish when balances run low, a self-serve consumer portal, and receipts. You focus on your server. We focus on the money.

You receive payouts on your schedule. No invoicing. No accounts receivable. No chasing. Tally never extends credit to anyone — consumers always prepay, so you never carry the risk of a consumer who can't pay.

Managed billing is included in the 10% revenue share. There is no extra charge for the payment infrastructure. We take our cut only when money changes hands.

The guarantees

What we will never do
to you or your consumers.

🚫

No negative balances

When credits hit zero, invocations are rejected. No debt is ever created.

📭

No invoicing

All usage is prepaid. No invoice is ever sent to anyone for services already consumed.

💥

No surprise bills

Consumer balances are visible at all times. Nothing happens behind their back.

🔗

Billing not in the execution path

A billing service outage cannot fail your invocations. The two systems are architecturally separate.

Paid Features

Billing.

Usage visibility is free. Monetisation is a revenue share — we only earn when you earn.

Always free

Usage Visibility

Full observability of who is using your server and what it costs them.

  • Per-consumer call counts and token volumes
  • Usage attribution across call chains
  • Running cost estimates at any rate
  • Immutable audit trail, always exportable
  • Charging consumers — not on free
  • Managed billing — not on free

Instrument your MCP server today.

Usage visibility is free. Start there. Add monetisation when you're ready.