Uniswap on Tempo: DeFi as a Machine Payments Primitive

Uniswap deployed its entire protocol suite — v2, v3, and v4 — on Tempo mainnet on March 18, 2026, the same day Tempo's chain went live. The deployment is not a routine multichain expansion: Uniswap ships as a structural dependency of Tempo's Machine Payments Protocol (MPP), meaning swap and routing infrastructure arrives pre-wired into an autonomous agent payment standard from day one.

What Uniswap Actually Shipped on Tempo

The deployment covers three protocol versions plus a new API surface and an MPP-native skill. According to the Uniswap Labs blog, Uniswap v2, v3, and v4 contracts are live on Tempo mainnet, with the Uniswap API supporting gas estimation, slippage calculation, and cross-source routing from day one. The Uniswap web app and wallet are not yet live on Tempo — those are listed as coming soon, meaning the current integration surface is entirely API and protocol-layer.

The third component is a "pay-with-any-token" skill built specifically for Tempo's MPP. Developers install it with a single command:

npx skills add uniswap/uniswap-ai --skill pay-with-any-token

When an agent receives an HTTP 402 payment challenge requiring a token it does not hold, the skill calls the Uniswap API to swap into the required token and then retries the payment automatically. A free API key from the Uniswap Developer Platform is the only prerequisite — no per-trade fees apply.

No Tempo-specific TVL or volume figures were published in the launch announcement. The Tempo explorer at explorer.tempo.xyz is live but early-stage activity data is sparse. Treat this deployment as mainnet-live but in its first days of real load.

Uniswap Labs blog: Uniswap is Live on Tempo

The Aggregator Hook: Tempo's Architecture Forces a New v4 Primitive

The most technically significant element of this deployment is not Uniswap's chain count ticking upward — it is the first production use of v4 aggregator hooks.

Tempo runs its own native stablecoin DEX for stable-to-stable pairs such as USDC.e to USDT0. Uniswap covers all other asset types as the chain's designated liquidity layer. These two sources would ordinarily require separate API calls or manual routing logic. The aggregator hook eliminates that: it wraps Tempo's stablecoin DEX as a set of v4 pools, so a single Uniswap API call routes across both sources in one swap. Stablecoin trades settle on Tempo's native DEX; everything else settles on Uniswap v4 pools.

Aggregator hooks are a v4 primitive that lets developers treat any external liquidity source as if it were a native Uniswap pool. Prior to v4, adding an external DEX to a routing graph required bespoke adapter work and separate contract calls. With the hook abstraction, the external source is represented inside Uniswap's pool manager logic directly. As Uniswap Labs noted at v4's launch, creating new pools in v4 is up to 99.99% cheaper than in v3, and multi-hop swaps carry lower gas overhead — both properties that matter when swaps happen inside programmatic payment flows with tight latency budgets.

Uniswap confirmed aggregator hooks will expand to additional chains and additional external liquidity sources, though no timeline was given.

Web3 Builder coverage of Uniswap v4 hooks→ /categories/web3-builder

How MPP Turns a 402 Response Into a Swap Trigger

To understand why this deployment matters, it helps to understand what the Machine Payments Protocol is actually doing at the wire level.

MPP is an open standard co-authored by Stripe and Tempo, with its core HTTP authentication scheme submitted to the IETF for standardisation. According to the MPP specification repository and the official Tempo documentation, the protocol revives the long-dormant HTTP 402 "Payment Required" status code into a deterministic challenge-response flow:

1. An agent sends a standard HTTP request to a paid API endpoint.
2. The server returns 402 Payment Required with a WWW-Authenticate: Payment header containing the price and accepted token addresses.
3. The agent fulfils the payment credential, signs it, and retries the request.
4. The server verifies payment and returns the resource with a receipt.

The entire cycle runs inside a single HTTP request loop — no redirects, no webhooks, no out-of-band settlement. Tempo's ~500ms deterministic finality, as cited in Tempo's documentation, is what makes synchronous request-response feasible at all.

The problem Uniswap's skill solves sits at step three: the agent may not hold the specific token the server demands. Without a conversion layer, the agent either errors out or requires human intervention to fund the correct token. The pay-with-any-token skill makes Uniswap the automatic conversion step — the agent holds whatever it holds, the skill handles the swap, and the payment succeeds. This is where DeFi routing exits the speculative UX paradigm and enters the infrastructure layer.

MPP specification — tempoxyz/mpp-specs on GitHub

How This Compares to x402 and What the Division of Labour Looks Like

MPP is not the only protocol attempting to standardise agent payments over HTTP 402. Coinbase's x402 protocol covers similar ground — agents pay for API access using USDC on Base, Polygon, Solana, or other chains — and it has an active developer community.

The architectural distinction, as GetBlock's technical breakdown describes, comes down to three differences. First, x402 routes payments through a facilitator component — a middleware bridge between client and server — that remains a required dependency even after x402 v2 made it more modular. MPP eliminates the facilitator: Visa, Lightspark, and Stripe wrote their payment method extensions directly into the protocol spec. Second, MPP introduces native sessions from day one, allowing agents to authorise spending once and make many subsequent payments using off-chain vouchers with periodic on-chain settlement. x402's session architecture arrived later and with more implementation overhead. Third, MPP is payment-method agnostic at the spec level — Tempo stablecoins, Stripe card payments, and Bitcoin Lightning are already live extensions; more can be added by any party as independent spec documents.

What this means for developers choosing between the two: x402 is a thinner layer with more chain flexibility today. MPP carries more design surface — sessions, identity primitives, payment-method extensions — but is currently tied to Tempo as its primary on-chain execution environment for stablecoin flows. By March 2026, over 100 services were listed in the MPP payments directory at launch, per Techstrong's coverage, including OpenAI, Anthropic, Dune, Browserbase, and others.

Crypto Newswire coverage of Tempo's DeBank integration→ /categories/crypto-newswire

What Builders Can Do Right Now and the Integration Path

The integration path for a developer building an agent that consumes MPP-gated APIs is now concrete:

Step 1 — Get a free Uniswap Developer Platform API key. No upfront cost, no per-trade fee.

Step 2 — Install the pay-with-any-token skill: npx skills add uniswap/uniswap-ai --skill pay-with-any-token

Step 3 — Fund an agent wallet with any supported token on Tempo. The skill handles conversion to whatever token the 402 challenge specifies.

Step 4 — Point your agent's HTTP client at any MPP-compatible endpoint. The skill intercepts 402 responses, calls the Uniswap API, swaps, and retries without additional agent-side logic.

For developers who have already integrated the Uniswap API on other chains, Tempo requires no additional integration work. The API already covers routing across 18+ chains including Tempo, with gas estimation and slippage included in the same call, as confirmed by the Uniswap blog post.

The more significant implication for protocol architects: this deployment establishes a pattern where liquidity access is a peer-level dependency of payment standards, not a downstream consumer application. Any agentic framework that adopts MPP inherits Uniswap routing as a default capability, without the framework authors having to reason about swap infrastructure at all.

Tempo Machine Payments documentation

Limitations and What Is Not Yet Resolved

Several gaps exist that builders should account for.

No published TVL or volume data. Tempo launched mainnet on March 18, 2026. No Tempo-specific Uniswap TVL figures, pool depth data, or routing quality benchmarks are available as of launch. Liquidity depth on a new chain directly affects slippage for any non-trivial swap amount. The pay-with-any-token skill's practical ceiling depends entirely on how fast liquidity migrates to Tempo pools — a number that does not yet exist.

Web app and wallet support are pending. The current integration is API and protocol-layer only. Uniswap's own web app and wallet are not yet live on Tempo. Agents building programmatically are unaffected; consumer-facing flows that depend on the Uniswap interface will wait.

No audit disclosure for the Tempo deployment. The announcement does not reference a specific audit of the Uniswap contracts as deployed on Tempo's chain. Uniswap v4's core has been extensively audited — over 500 hours of security review were cited at its January 2025 launch — but deployment-specific reviews on new chains can surface configuration or integration risk independent of core protocol security.

Aggregator hook expansion timeline is unconfirmed. Uniswap confirmed that aggregator hooks will roll out to additional chains but provided no schedule. Developers who want to replicate the Tempo dual-source routing architecture on other chains have no target date to build toward.

MPP itself is an early standard. The core spec is proposed to the IETF, not yet standardised. Builders adopting MPP today are building on a protocol that is open and well-specified but not yet ratified.

GetBlock: MPP vs x402 technical comparison

The concrete signal to watch is liquidity migration velocity onto Tempo's Uniswap pools over the next 30 to 60 days — that number will determine whether the pay-with-any-token skill functions as a reliable conversion layer or as a high-slippage fallback for edge cases. The second milestone is Uniswap's web app and wallet going live on Tempo, which will shift the integration from developer-only to end-user accessible and generate the first real volume data worth benchmarking against other MPP-compatible chains.