Discover services
An agent wallet pays online services that accept x402. To find them, Keyban keeps a directory of x402 services. You browse it on the dashboard's Services page, where you also authorize the ones your agents may pay. Your agent searches it with its own tools before it pays.
Where the services come from
Keyban copies two public directories of x402 services twice a day, at 6:00 and 18:00, Paris time:
- Coinbase, the directory run by the company that created x402;
- Orthogonal, a gateway that resells the APIs of other providers through x402. Its services show the provider's name followed by "via Orthogonal".
Each service comes with its name, a description, tags, its price, and the networks it accepts payment on. Its price is fixed, variable when it depends on the request, or free.
A Keyban wallet pays only a fixed price in USDC, with the x402 exact scheme, on Base mainnet or XDC mainnet. A service that offers no payment of that kind is marked unsupported on the dashboard and not payable for the agent, and comes last in the results. See What a wallet can and cannot pay.
From the dashboard
Services, in the application menu, lists the x402 services your agents can pay.
- Search by name, description or tag.
- Two views. Authorized keeps the services that pass the destination rules of the organization and of the application. Full catalogue shows every service.
- Source keeps one directory, Coinbase or Orthogonal, or both.
- Each row shows the service, its price, what your agents spent on it this month, and whether it is authorized.
- A click on a service opens its details: the resource's address, its price, whether a Keyban wallet can pay it, the agents that paid it this month and how much, its networks and its tags, and a link to copy.
Authorize a service
An administrator authorizes a service by ticking Authorized. This edits the organization's destination rule so that it lets the service's domain through, and unticking takes the domain out again. If it is the last domain the rule allows, the dashboard warns that every x402 payment of the organization would then be blocked. See Control spending.
The box is disabled, with the reason shown, when:
- you are not an administrator;
- the application's rule blocks the service;
- a broader rule already decides, which you change in the organization rules;
- the organization's rule is an allow-list without domains, which you edit in the organization rules.
Behind a gateway such as Orthogonal, every provider shares the gateway's domain. Authorizing one of them authorizes the whole gateway, and the dashboard asks you to confirm, with the number of providers it covers.
Authorized reflects the rules of the organization and of the application only. A rule set on one wallet can still refuse a payment to an authorized service.
What the agent does
Before it pays, the agent finds a service and checks its price:
discover_x402_servicessearches the directory by free text, by network or by tag, and returns up to 50 results, 10 by default. The network is a CAIP-2 chain id, such aseip155:8453for Base mainnet. Each result carries a call recipe, with the HTTP method the service serves and example parameters, and says whether the wallet can pay it. The agent skips a service marked not payable.x402_infoprobes a URL and returns its price and the parameters it takes, without paying. The agent should call it with the same method, query and body it will pay with: a service that only serves POST answers404or405to a GET and never shows its price, and a variable price depends on the request.x402_paythen pays and fetches the resource. See Pay.
From a script, the same tools are keyban wallet discover-x402-services and keyban wallet x402-info. See CLI, MCP and API.
From your own code
The directory is also in the REST API, with an organization API key:
GET /v1/x402/resourceslists the services, with the same search, network and tag filters;GET /v1/applications/{applicationId}/x402/serviceslists them as one application sees them: authorized or not, and what its wallets spent on each this month.
A person signed in with keyban admin login gets the first one as the admin tool list_x402_services, from the Keyban MCP server or as keyban admin list-x402-services. See Admin tools.
Related
- Pay: paying the service once found.
- Control spending: the destination rules behind Authorized.
- x402 protocol: how an x402 payment works.
- Integration guide: finding x402 services to replace the paid APIs your agents use today.