What it costs

You pay when you get paid.

1%

of payment volume, on top of Stripe’s fee. Nothing until money moves.

Free to start

No setup fee, no minimum volume.

Sandbox, always free

Test with sample data, no time limit.

Build it with us

Pricing design, protocol work and custom builds, scoped per project.

Apps · Host-distributed AI

Get paid wherever AI runs.

Turn your API or your MCP server into a tool inside Claude, ChatGPT, or Cursor and get paid every time it's used.

Live today  ·  Works with Stripe  ·  Claude, ChatGPT, Cursor, and more
See it work inside Claude · product walkthrough
An API or an MCP server, priced, called, and paid, start to finish.

Your users, and their agents, are getting real work done inside AI.
Now you can be paid, right there.

No redirect, no checkout page, no plan wall, the payment is embedded in the work.

Get paid where your users are
  • Claude
  • ChatGPT
  • Cursor
  • Antigravity
900M+

weekly active users on ChatGPT alone

OpenAI, Feb 2026
2.5B+

prompts sent every single day

OpenAI, 2026
XX%

of agent traffic already hits APIs and tools like yours

Placeholder, source pending
Placeholder headline

Here's how it works.

The same four steps, whichever path you choose.

Step 01 · CONNECT

Connect.

One line of code for your API. Paste a URL for your MCP server. Either way, it's a few lines, and it's live everywhere the same day.

// Paste your hosted proxy URL into any MCP client
// Zero code changes, auth, checkout, and paywalls are handled for you

https://mcp.solvapay.com/proxy/your-server-id
› npm install @solvapay/server

// Protect an endpoint
import { createSolvaPay } from '@solvapay/server';
const solvaPay = createSolvaPay();
const payable = solvaPay.payable({});
app.post('/agent/chat', payable.http(handler));
// Every action runs through a REST API underneath
// call it directly to wire SolvaPay into anything

› curl -X POST https://api.solvapay.com/v1/ui/webhooks/{endpointId}/test \\
  -H "Authorization: Bearer $TOKEN"
› npx solvapay init

// Scaffolds your project, authenticates your account,
// and writes your secret key to .env
White glove

Need help setting this up?

Use our white-glove service, and we'll do the connection part for you.

Book a call
Step 02 · SET A PRICE

Your pricing is part of your product now.

The more ways someone can pay you, subscription, usage, credits, hybrid, the more revenue streams you can add without rebuilding anything.

Image or video slot · pricing models
Image slot

One-time

A single charge for a single thing, a concert ticket, a one-off report, a single call with no ongoing relationship. Not a layer to stack, a standalone transaction.

Image slot

Subscriptions

Set monthly or annual plans with clear limits your customers already understand. Familiar, predictable, easy to sell to a buyer who wants a fixed number.

Image slot

Usage-based

Charge per call, per token, or per outcome, whatever unit maps to the value you actually deliver. Scales exactly with how your product gets used.

Image slot

Credits

Sell prepaid credit packs that draw down per action. Customers buy once and spend as they go, no surprise bills at the end of the month.

Image slot

Hybrid

Layer usage on top of a subscription, or credits on top of a plan. Mix models on one product without extra engineering every time pricing changes.

Step 03 · GET USED

Full visibility and control

Whoever, or whatever, is using you, it doesn't get metered or trusted without being attributed first. Every customer, every product, every plan, everything they do, visible in a dashboard you can see, or right in your AI workflow.

Learn more about the platform
Image or video slot · live event feed in the Console
Step 04 · GET PAID

Get paid.

Same mechanism, whichever path you picked. Checkout, refunds, revenue: all of it visible the moment it happens.

Your data

Get paid on every API call.

One call or one million, each one identified, metered, and billed the same way.

Your product

Get paid on every tool call.

Whether the agent's inside Claude, ChatGPT, or Cursor, your MCP server gets paid the same, per call, automatically.

Image or video slot · settlement, start to finish

See how much you can earn inside AI.

A rough estimate, based on call volume and price per call.

Estimated monthly revenue
$1,000
50,000 calls at $0.02
50,000
$0.02

Illustrative only, not a guarantee. Your real numbers depend on your product, your price, and your users.

Watch your revenue grow

Getting paid is day one. The rest is growth.

Image or video slot · the dashboard
01

Your data is fully protected

Your API and your MCP server run on your own data. SolvaPay is the payment layer that sits on top, we never touch your data.

02

Gate by plan

Expose different endpoints or tools depending on what tier someone's on.

03

Block the scrapers

The same metering that bills legitimate use blocks unmetered, anonymous scraping.

04

Turn your MCP into a funnel

New signups and upgrades, inside the AI itself.

05

Stay ahead of new protocols

MCP is shipping. A2A, ACP, AP2 get picked up automatically as they land.

06

Free until you earn

1% plus Stripe's processing fee. No setup, no monthly minimum. You don't pay until you get paid.

07

No migration, no lock-in

You're adding a rail, not moving your business. Remove it as easily as you added it.

08

Sandbox, always free

Sample data, no real transactions, no cost, no time limit. Go live when you're ready, not before.

  • You're solving a problem for me. You're helping me do that transaction in a smooth way without me having to build that system. You're saving me time and money.
    Rodrigo Graviz
    CEO, MyTelescope
  • We'd deliberately avoided building a chat interface because it's expensive to run. This collaboration lets our power users access our analysis and data, and pay for it easily through SolvaPay.
    Vilhelm Niklasson
    CRO, Quanor

Get paid on every call.
Whichever one you build.

API, MCP, or both. One integration, live this week.

Talk to the team

Frequently /asked questions

Before you dig in

Yes, this one's for your engineering team, it's a code integration on your API or MCP server. If you don't have engineering resources yet, talk to us, we can help.

Either fork works on its own. You don't need both.

In most cases, yes, this adds a new way to get paid on top of what exists. The details can depend on which host your MCP server runs on, we'll walk through your specific setup on a call.

For your engineers

Claude, ChatGPT, Cursor, Antigravity, and any MCP-compatible host.

We run an RFC 9728-compliant OAuth server with Dynamic Client Registration.

Stripe today. Adyen, Mollie, instant bank rails, and A2A settlement are on the roadmap.

Programmatic, via the SolvaPay API or your dashboard.