Let AI agents buy from you
Make your existing commerce experience available to AI agents without building a separate store, booking system or order flow for agents.
Your existing API remains responsible for your products, services, prices, availability, customer rules, orders, bookings and fulfilment. You choose which operations agents can use, and Mitu makes those capabilities available through MCP.
When payment is required, Mitu handles the agent payment flow before sending the paid request to your API.
Keep current prices, inventory, availability, taxes, fees and transaction totals in your existing system. AI agents use your tools to retrieve this information when they need it rather than relying on information stored in the AI client.
Before you begin
You need a Mitu account, an existing commerce API that Mitu can reach and the API operations an agent needs to complete the experience you want to support.
For example, a restaurant might already have operations for viewing its menu, checking a delivery area, creating an order and retrieving the order afterwards.
A booking business might instead provide availability, booking and booking-status operations. You do not need to follow a specific API structure. Use the API and business logic you already have.
Connect your commerce API
Start by connecting the API that already powers your commerce experience.
In the dashboard, provide the base URL that Mitu should use when sending requests to your API.
You do not need to create separate endpoints for AI agents. The same operations that serve your website or application can also 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.
Learn more about Request verification.
Choose the commerce operations agents can use
Choose the operations an AI agent needs to complete the customer journey you want to support.
Different businesses will expose different capabilities.
Each operation becomes an MCP tool. Give each tool a clear description and schema so an AI agent can understand what it does and when it should use it.
Only make operations available when they are useful to an agent. Internal operations that an agent should never call do not need to become tools.
Learn more about MCP endpoints.
Choose which operations require a customer
Decide which capabilities require the agent to act on behalf of a customer who already has an account with your business.
Public capabilities such as browsing a menu, searching products or checking general availability may not require customer authentication.
Operations that use saved addresses, customer-specific pricing, loyalty benefits, account history or other private information will usually require an identified customer.
You can configure authentication for each operation.
Use customer keys when you want to provision customer access yourself. Use OAuth when customers should sign in with the account they already have with your product.
Learn more in Connect customer accounts.
Keep commerce information in your system
Your existing system should continue to determine what can be purchased and how much it costs.
When an agent needs a product, menu, available room, appointment slot or other information, it retrieves the current information through the tools you have made available.
The same applies to transaction totals. Your backend remains responsible for calculating the final amount using the rules you already apply to other channels.
This can cover product prices, quantities, taxes, delivery charges, service fees, discounts and any other values that affect the transaction.
Do not place information that changes frequently inside tool descriptions. Let the agent retrieve the current information from your API when it needs it.
Configure payment for the transaction
Choose how the transaction operation should be priced.
Fixed pricing works when the amount is known in advance and does not change between transactions.
Dynamic pricing works when your application needs to calculate the amount from the transaction. This is common for orders, bookings and reservations where the final amount depends on the items, dates, quantities, fees or other information supplied with the request.
With dynamic pricing, your backend determines the amount and Mitu handles the payment before the paid transaction is sent to your API for fulfilment.
Learn more about Pricing.
Let agents use your commerce experience
Once your tools are available through MCP, customers can connect your product from a supported AI client.
An agent can use the tools you provided to complete the same journey a customer would normally complete through your website or application.
For example, a customer could ask:
The agent can use your menu to find the requested items, check whether the saved address is serviceable and use your order operation to request the transaction.
For another business, the same journey could involve searching available rooms before creating a booking or checking appointment availability before scheduling a service.
Your API remains responsible for validating every request using the same business rules it already applies.
Let Mitu handle the payment
When the transaction requires payment, Mitu handles the payment flow with the AI agent.
Your business does not need to implement separate integrations for x402, MPP or other supported agent payment methods. Mitu handles the payment requirement and confirms payment before the paid request is sent to your API.
Agent Wallets are also not required for customers to buy from you. They are an optional way to give your own customers wallets that their AI agents can use to make payments on their behalf.
Learn more about Agent payments.
Verify the request from Mitu
Before creating the order, booking, reservation or appointment, verify that the request came from Mitu.
Use the signing secret provided when you connected your API to validate the request signature. Only process and fulfil the transaction after verification succeeds.
Your application should continue validating the transaction itself as well. Check availability, quantities, customer eligibility and any other business rules that normally apply before creating the transaction.
See Request verification for the verification process and implementation examples.
Create the transaction and return your response
After verification succeeds, process the request using your existing business logic.
Your API does not need to return a special response for AI agents. Return the same order, booking, reservation or appointment response that your application already uses.
For example:
Mitu returns the result to the agent, allowing it to confirm the outcome to the customer.
Use stable transaction identifiers and clear statuses so the agent can retrieve the transaction again when the customer asks for an update.
Track payments and transactions
Use webhooks to keep your systems updated as payment activity occurs.
Payment events can be associated with the corresponding transaction in your system so you can reconcile payments with orders, bookings, reservations or appointments.
Your own system should remain responsible for the lifecycle of the transaction after it has been created, including fulfilment, status changes and cancellations.
Your commerce experience is available to AI agents
AI agents can now use the products and services you already provide without your business maintaining a separate commerce system for them.
Your system continues to control your catalogue, availability, prices, customers, transaction rules and fulfilment. Mitu provides the agent-facing connection and handles agent payments before verified paid requests reach your API.
You can use the same approach for retail purchases, food orders, hotel bookings, appointments, reservations and other commerce experiences built on your existing APIs.