Skip to main content

What Is Mercator? Tempo's Agent Tool Router

Mercator gives AI agents one interface to find paid tools, get a quote, and pay for and run a multi-step job. Here is how it works and how it connects to the Machine Payments Protocol.

Written by Eco
What Is Mercator? Tempo's Agent Tool Router

Mercator is a discovery layer and tool router for AI agents, listed by Tempo alongside the Machine Payments Protocol (MPP) on its agentic payments page (Tempo agentic payments). It connects an agent to paid tools and services through one interface, so the agent can search the web, research companies, enrich records, or call a model without the developer integrating each provider separately (Tempo Docs, Mercator).
​

The practical change is that an agent with a task and a budget can find the right services, see a price, and pay for the whole workflow as one job. This article covers what Mercator does, how a job moves from search to result, how it relates to MPP and x402, what it costs, and how to connect it to an agent. For background on the chain itself, see What is Tempo blockchain.
​

What is Mercator on Tempo?

Mercator is a single interface that lets an agent find tools, quote a plan, and pay for and run that plan. Tempo's documentation describes it as coordinating discovery, payment, and execution across independently operated services (Tempo Docs, Mercator). The downstream services keep running on their own; Mercator sits between the agent and those providers.
​

Mercator's own documentation breaks the job into three steps: find tools for an open-ended workflow, quote an immutable plan of one or more tool calls, and pay for and run the plan as one durable job (Mercator documentation). The same page shows example downstream providers including Exa for web search, Parallel for web research, and OpenAI for model inference (Mercator documentation).
​

Developers can connect Mercator to an agent through the Model Context Protocol (MCP) or build an integration against its REST API (Tempo Docs, Mercator). Support requests go to a tempo.xyz address listed in the Mercator docs (Mercator documentation).
​

How does a Mercator job work?

An agent receives a task and a budget, uses Mercator to find services, gets a price for the selected tool calls, then pays for and runs them as one job. Tempo's example is asking an agent to research three competitors and turn the findings into a sourced brief (Tempo Docs, Mercator).
​

The flow has four stages:

  1. Discover. The agent searches Mercator's catalog for services that fit the task. Search and service inspection are free (Mercator documentation).

  2. Quote. Mercator returns a quote for a fixed plan of tool calls. The agent passes the quote token and exact total into submission, and Mercator charges that quote until its expiry; expired quotes must be requoted (Mercator documentation).

  3. Pay and run. Payment happens before execution, and paid work stays within the wallet limits approved during authorization plus any extra budget given to the agent (Tempo Docs, Mercator).

  4. Retrieve. Results can be retrieved later, even if the agent disconnects. If a job is still running, the agent keeps its job ID and resumes checking it (Tempo Docs, Mercator).

Because the quote describes an immutable plan, the agent knows the price of the whole workflow before money moves. A pending job does not need a second purchase (Mercator documentation).
​

How is Mercator connected to MPP?

Mercator uses the Machine Payments Protocol for payments on Tempo and also supports providers that use x402 (Tempo Docs, Mercator). MPP is the payment layer; Mercator is the routing and discovery layer built on top of it.
​

Tempo describes MPP as an open protocol co-authored by Tempo and Stripe for machine-to-machine payments. It uses HTTP 402 responses so an API can request payment, and the service verifies payment before returning the requested resource (Tempo agentic payments FAQ).
​

In Tempo's MPP guide, a server sends a challenge in a WWW-Authenticate: Payment header, the client retries with proof in Authorization: Payment, and the server confirms with a Payment-Receipt header (Tempo Docs, How MPP works). On Tempo, the credential can carry a signed transaction, a transaction reference, or a payment-channel voucher, depending on the intent. The guide covers two patterns: a one-time charge for a fixed price, and a session for metered usage with a funded channel and signed vouchers (Tempo Docs, How MPP works).
​

Mercator handles that handshake on the agent's behalf for each provider in a plan. According to its docs, Mercator pays providers through MPP on Tempo or through x402 on Base, and Base is not a customer payment rail (Mercator documentation). Tempo clients use mercator.sh for MPP attribution in transfer memos (Mercator documentation).
​

What does Mercator cost?

Discovery, inspection, quotes, result reads, and product feedback are free. A paid job costs the quoted provider costs plus Mercator's cost multiplier, paid before execution (Mercator documentation).
​

Activity

Cost or rule

Discovery, inspection, quotes, result reads, feedback

Free

Paid job

Quoted provider costs plus Mercator's cost multiplier, paid before execution

Job review

Free; original-payer proof required

Tempo payment

Prices shown in USDC.e; payable in MACH credits or through a supported pathUSD auto-swap

Stripe payment

USD with a shared payment token; whole-cent totals of at least $0.01 (Mercator docs)

MACH purchase rate

1 USD buys 1 MACH, minted to the authenticated wallet

Gas sponsorship

Mercator sponsors up to 8,000,000 declared gas per Tempo charge

Source for every row: Mercator documentation. MACH is a credit that can be used on Tempo to pay approved merchants, including Mercator. pathUSD is Tempo's root quote token and fallback fee token; see What is pathUSD for how it works.
​

Refunds depend on the payment rail. For Tempo payments, unused capacity on failed or succeeded jobs returns to the wallet as MACH credits at a 1:1 value; Stripe payments have no automatic refunds (Mercator documentation). Purchases wasted by Mercator, such as output limits or completion timeouts, are refunded. When a provider refuses Mercator's payment with a fresh challenge, Mercator confirms onchain within about 30 seconds that nothing was paid, then retries or refunds that share (Mercator documentation).
​

How do spending limits work for Mercator agents?

Spending is capped by the wallet limits chosen during authorization, and any budget written into the prompt is an additional limit (Mercator documentation). Native MPP clients and local wallets need quote approval or a sufficient explicit budget, plus a new quote after a price change.
​

On the Tempo side, access keys let an account set a spending limit and expiry for each agent, and Tempo enforces those limits when the key makes a payment (Tempo agentic payments FAQ). Mercator's docs note that the Tempo access key stays valid until revoked by default. To disconnect, revoke the connection in Mercator Account to disable OAuth, then ask Tempo Wallet to revoke the onchain key (Mercator documentation).
​

Network fees are separate from the service charge. On Tempo, the agent's account can pay network fees or a platform can cover them through fee sponsorship (Tempo agentic payments FAQ). For more on how Tempo charges fees, see Does Tempo have a token.
​

How do you connect an agent to Mercator?

For an installed coding agent, run Mercator's installer, authorize the agent with chosen wallet access and spending limits, then verify the connection with free calls. Web apps and managed environments use Mercator's agent setup guide instead (Tempo Docs, Mercator).

  1. Install. Run curl -fsSL https://mercator.sh/install.sh | sh on the computer where the agent runs and select the clients to connect. Users of the Tempo plugin marketplace can install mercator@tempo directly (Tempo Docs, Mercator).

  2. Authorize. Load the installed configuration, complete authorization in the agent, and choose wallet access and spending limits for that connection.

  3. Verify. Ask the agent to search Mercator for services and check connection status without running a paid job. It calls search_services and get_connection_status, which are free (Tempo Docs, Mercator).

Mercator's docs list plugin commands for Claude Code, Codex, and Grok CLI through the public tempoxyz/plugins marketplace, and setup paths for Claude Desktop, Claude web, and ChatGPT (Mercator documentation). Access and funding are managed in Mercator Account.
​

Can API providers list a service on Mercator?

Yes. Operators of a paid API can follow Mercator's service-owner guide to make it discoverable, and Tempo points services that do not yet accept MPP to its guide for accepting payments for an API (Tempo Docs, Mercator).
​

Mercator ingests reviewed catalogs and endpoint metadata, and requests discovery for services using open payment protocols such as MPP and x402 (Mercator documentation). For reviewed endpoints, the live 402 response supplies the realm and recipient, so catalog pins are not required. A service that accepts MPP can charge per request, and Tempo supports sub-cent payments, with pay-as-you-go sessions combining small charges into periodic settlement (Tempo agentic payments FAQ).
​

What should you know before using Mercator?

Mercator is a router, not a provider. The services it calls are independently operated, so output quality and availability depend on each provider (Tempo Docs, Mercator). Agents should show a quote before running a paid job, and keep job IDs for long tasks.
​

Payments settle on Tempo Mainnet. For chain ID, RPC endpoints, and upgrade history, see Tempo mainnet launch date, chain ID, RPC and upgrades.
​

Did this answer your question?