AI agents are becoming participants in the digital economy. Connect your business to this new channel: buy or monetize Agent Traffic through x402, with payment per request over HTTP.
Explore our DMEXCO presentation ↗An AI agent asks a connected service for a resource.
MyBestClick’s Agent Traffic offering brings buyers and sellers together around traffic from AI agents using x402. It extends the conversation beyond website ad placements to programmatic requests and paid access between connected systems.
An agent can request a resource, receive payment requirements and complete a supported payment flow before delivery. The resource, price and permitted use are part of the integration agreed between the participating businesses.
x402 is an open payment protocol built around HTTP. It gives services a way to communicate payment requirements and clients a way to pay as part of a request. It supplies the payment mechanism; the connected service defines what is delivered.
This is a separate commercial channel from human ad impressions and clicks. Agent requests should be identified and measured as agent activity, with their own delivery and billing definitions.
Read about the x402 protocol ↗Agree what is being bought or sold, who can access it and how accepted requests will be priced and recorded. Identify the resource, traffic context and technical requirements.
Connect the participating systems to the supported x402 workflow. An agent receives payment requirements, provides the required payment authorization and requests delivery.
Test the connection and verify delivery before scaling. Reconcile accepted requests, payment records and service outcomes using the reporting agreed for the integration.
Bring your use case, intended markets and delivery requirements. We will discuss where Agent Traffic fits your business, which connections are available and what a useful first test should measure.
Set clear objectives for agent activity. A paid request is a different event from a website visit, an ad click or a customer conversion; agree the commercial event before launching.
Discuss buying Agent TrafficExplore whether your platform, resources or existing agent traffic can form a supply connection. Describe what you provide, how requests reach you and the access rules that apply to your inventory or service.
Monetization starts with a suitable integration and agreed terms. We work through the request flow and delivery expectations before you send live activity.
Discuss monetizing Agent TrafficMyBestClick also offers platform connections through an MCP server. The aim is direct communication between platforms so they can exchange traffic. Discuss the operations, permissions and commercial scope of your connection with our team.
Your platform connects with MyBestClick under an agreed scope.
MCP describes the platform connection. x402 describes a payment flow. We present them as separate offerings, so you can start with the product your business needs.
Discuss an MCP connectionA useful first discussion starts with what your system provides or needs, rather than treating every automated request as the same product.
Describe the resource the agent will receive, the system that serves it and the usage you can permit. Explain how a successful response can be distinguished from an empty, incomplete or failed response. Identify the technical owner who can connect access decisions with delivery.
Bring a description of your current request flow and the volume you expect to test. Existing bot visits provide context, but do not by themselves establish a paid x402 connection.
Discuss your agent supply ↗Define the task the agent is performing and what a usable result looks like. Agree which requests the agent may make, how payment authorization is handled in the supported setup and who can stop the test if its behavior differs from the intended scope.
Evaluate the delivered result as well as the paid request count. The business value comes from completing the intended task with an acceptable cost and response.
Discuss your agent use case ↗Identify the operation you want the connected platform to perform, the permissions it needs and the response your own workflow expects. Plan how unsuccessful operations and repeated requests will be handled before connecting live activity.
Keep the communication agreement separate from payment terms. An MCP connection describes the permitted platform interaction; it does not automatically add an x402 payment flow.
Scope an MCP connection ↗Request volume alone cannot explain an agent connection’s result. Agree how to relate an incoming request to its payment record, where applicable, and to the resource or operation that was delivered. This makes failed requests and reporting differences easier to investigate.
Use a limited test to check valid requests, unavailable resources, unsuccessful authorization and repeated attempts. Define what each side will count before evaluating the economics or increasing activity.
Review the broader integration process ↗No. This offering concerns AI agent activity and x402 payment flows. Display, native, popunder, push and video remain separate advertising formats with their own human-facing placements.
No. Monetization requires a supported connection, a defined paid request and agreed commercial terms. Ordinary crawler visits do not automatically become paid traffic.
No. MyBestClick presents x402 Agent Traffic and MCP Connections separately. x402 supports payment over HTTP; the MCP offering connects platforms for direct communication and traffic exchange.
You can discuss an Agent Traffic connection alongside your existing advertising relationship. Its eligibility, integration and measurement are handled separately from standard ad campaigns.
Share your platform or website, whether you want to buy or sell, your intended use case and an overview of your request flow. The team will confirm the available integration, reporting and commercial setup.