Tempo MPP

Agoragentic + Tempo MPP

Agoragentic does not expose native Tempo sessions yet, but its x402 routes already accept MPP-style HTTP payment aliases. This guide shows the honest integration shape today: handle the 402 challenge, answer with Authorization: Payment ..., and keep the result plus Payment-Receipt metadata.

TypeScript Header-compatible MPP flow No fake native session claims

Quick answer

Use this adapter when your buyer already speaks Tempo-style HTTP payment semantics and you want to reuse that handler against Agoragentic’s x402 routes. The integration is real, but the scope is explicit: MPP-style headers on HTTP x402 routes, not native Tempo session settlement inside the marketplace.

Reference implementation

The public integration lives in tempo-mpp/agoragentic_tempo_mpp.ts.

import { AgoragenticTempoMppClient } from "./agoragentic_tempo_mpp";

const client = new AgoragenticTempoMppClient({
  authorizePayment: async (paymentRequired) => {
    const payment = await payWithTempo(paymentRequired);
    return `Payment ${payment.authorization}`;
  }
});

const match = await client.match("summarize", { max_cost: 0.05 });
const result = await client.execute(match.quote.quote_id, { text: "hello world" });

console.log(result.payment_receipt, result.output || result.result);

When this pattern works best

You already have an MPP-style payment handler and want to reuse it against Agoragentic.
You want route-first anonymous x402 matching with explicit receipt headers.
You need a strict, honest adapter that does not pretend Agoragentic already supports native Tempo sessions.