Sell your API to AI agents

Connect your existing API

Start by connecting the API that already provides the capability you want to sell.

In the dashboard, provide the base URL that Mitu should use when sending requests to your API.

https://api.example.com

You do not need to create separate endpoints for AI agents. The same operations you already run can be made available through MCP.

When you connect your API, Mitu provides a signing secret that your backend uses to verify requests sent by Mitu. Keep this secret secure and only use it from your server.

Learn more about Request verification.

Choose what agents can pay for

Choose the API operations that you want AI agents to discover and use.

For example, a company data API might make these capabilities available.

GET   /companies/search
GET   /companies/{domain}
POST  /reports

Each operation becomes an MCP tool. Give each tool a clear name and description so an AI agent can understand what it does and when it should use it.

name: company_profile
method: GET
path: /companies/{domain}
description: Retrieves a structured company profile for a specific domain
when_to_use: Use when you need company information for a known website or email domain
pricing_type: fixed
price: 0.05

If you already maintain an OpenAPI specification, you can import it instead of configuring each operation individually.

Learn more about MCP endpoints.

Set the price

Configure how much an agent should pay to use the operation.

Use fixed pricing when every successful request costs the same amount.

pricing_type: fixed
price: 0.05

Use dynamic pricing when the amount depends on the request. For example, the price of generating a report might depend on its size, the amount of data requested or another value calculated by your application.

With dynamic pricing, your API determines the amount before the paid operation is completed. Mitu then handles the payment before sending the paid request back to your API.

Other supported pricing models can be used for capabilities that need different charging behaviour.

Learn more about Pricing.

Make the capability available to agents

Once the operation is configured, it becomes available as a tool through your MCP.

Customers and other supported users can connect your MCP from compatible AI clients and discover the paid capabilities you have made available.

For example, an agent connected to a company data service might discover tools such as:

search_companies
company_profile
company_report

The tool descriptions and schemas tell the agent what each capability does, what information it requires and when it should be used.

Learn more about MCP tools.

Let Mitu handle the payment

When an agent calls a paid operation, Mitu determines what the agent needs to pay before the operation can be completed.

Mitu handles the supported agent payment flow, including payment requirements and supported protocols such as x402 and MPP. Your API does not need to implement these protocols separately.

Once payment has been confirmed, Mitu sends the paid request to the API operation you configured.

Your responsibility remains the same. Provide the product, data or service that the API operation represents.

Learn more about Agent payments.

Verify the request from Mitu

Before your API processes the paid request, verify that it came from Mitu.

Use the signing secret provided when you connected your API to validate the request signature. This allows your backend to confirm that the request and its payment information were sent through Mitu.

Only fulfil the paid operation after verification succeeds.

The dedicated verification guide covers the request headers, signature format and implementation examples.

See Request verification.

Return your normal response

After the request has been verified, your API handles it using the same business logic it already uses.

For example, an existing company profile endpoint might return:

{
  "name": "Example",
  "domain": "example.com",
  "industry": "Technology",
  "employees": 240
}

You do not need to create an agent-specific response format. Return the response your API normally provides for that operation.

Mitu returns the result to the agent through the MCP request it started.

Track the payment

Payments made for your API capabilities are recorded in your Mitu account. Use payment events to keep your own systems updated when payments are completed or fail.

For production integrations, configure webhooks rather than relying on the dashboard as your only source of payment state.

Your payment records can be associated with the corresponding request so you can reconcile usage, payments and activity in your own systems.

Learn more about Webhooks and Events.