Invoket

For agents

Invoket is designed to be consumed with no human in the loop. An agent discovers the endpoints, reads their price and settles the call programmatically. It can find Invoket two ways: through the CDP x402 Bazaar (the registry agents already query) or directly via Invoket’s own machine-readable surfaces.

Discoverable via the CDP x402 Bazaar (MCP)

Invoket settles through the Coinbase CDP facilitator, so every paid resource is indexed in the CDP x402 Bazaar — the registry that agent runtimes (Claude, Cursor and others) actually search. An agent does not need to know about Invoket in advance: it finds us by intent.

  • Via MCP — the official x402 MCP server exposes a search_resources tool. Queries like verify payee, IBAN, sanctions screening or phone fraud surface Invoket’s matching endpoints.
  • Via HTTP — the same index is reachable at …/discovery/search.

This channel sits alongside the home surfaces below: the Bazaar tells an agent that Invoket has a relevant endpoint; /catalog remains the source of truth for its exact path, price and rails. Either way the loop is the same: discover → 402 → pay → replay (see Quickstart).

Note this is the discovery MCP surface (finding endpoints by intent). To also pay for calls through MCP without touching the x402 protocol yourself, use Invoket’s own MCP server (@invoket/mcp) — one line of host config turns every paid endpoint into a typed, spend-capped tool.

/catalog — the living catalog

api.invoket.com/catalog returns every paid endpoint in Bazaar x402 format: for each resource, its method, its price, and the list of rails (accepts). It is the source of truth: an agent queries it to know what to call and how to pay.

llms.txt — site map for LLMs

invoket.com/llms.txt is a concise map of the site, meant to be read by an LLM: it points to the key pages and the machine surfaces. (Published with the agentic surface.)

/.well-known/x402.json — machine manifest

invoket.com/.well-known/x402.json is the domain’s x402 manifest: it indicates where the gateway lives and where to find the catalog. An agent can start from there to bootstrap discovery. (Published with the agentic surface.)

The same document is also served, byte for byte, at invoket.com/.well-known/x402 (the extensionless spelling used by the x402 discovery draft) and at invoket.com/x402.json. All three answer 200 — no redirect — so a probe never has to guess the spelling. /.well-known/x402.json stays the canonical one.

/blog — use-case context (not a payment surface)

The blog (feed: invoket.com/blog/rss.xml) carries use-case articles and x402 ecosystem notes. It is background reading on why and when to call an endpoint — not a payment channel. The price, path and rails always come from /catalog; an article never settles a call.

Free trial

Some endpoints offer one free call per day, identified by payer address — not by IP, not by an API key. There is no new primitive: when an endpoint offers a trial, its 402 challenge includes one extra rail at a symbolic dust amount, far below the published price, alongside the paid ones. Sign it with the same x402 SDK you already use to pay and replay the call: the trial is never settled, so nothing moves on chain and the signed authorization expires unused — once per day, per endpoint, per address. Check /catalog (metadata.trial) to see which endpoints currently offer one.

Send feedback

Hit an unsupported case, a missing data point or a bug? Send feedback via the free POST /review channel — no payment, no account. It is the place to tell us what you need us to build next.

Typical agent loop

  1. Discover the endpoint — by intent through the CDP Bazaar / MCP (search_resources), or by reading the manifest or /catalog directly.
  2. Pick the useful endpoint and read its price (priceUsd) and its rails.
  3. Call, receive the 402, sign the chosen rail and replay — see Quickstart. If the endpoint offers a free trial, one of the rails simply carries a dust amount.