Conduit Rpc Gateway

Conduit RPC Proxy

Paid JSON-RPC access to Conduit chains using the Machine Payments Protocol.

All networks on the Conduit Hub or configured as discoverable are supported. Each network is a paid route at /:network-id. Cost is $0.00005 per JSON-RPC call.

Gateway URL

https://mpp.conduit.xyz

Setup (Required)

BEFORE making any requests, you MUST determine which client to use. Follow this flow:

1. Ask the user which client they prefer. Present this prompt exactly:

Which client would you like to use for Conduit RPC calls?

1. Tempo Wallet (Recommended) — Managed MPP client with built-in spend controls. No manual key management.
2. mppx — Lightweight MPP client via npx. Manages keys internally.

Do NOT skip this prompt. Do NOT pick a client on behalf of the user. Wait for their explicit choice before proceeding.

2. Based on the user's choice, follow the setup instructions in wallet-bootstrap.

Use when

• The user asks to query a Conduit chain (Tempo, Plume, Polygon Katana, etc.)
• An agent needs to make EVM JSON-RPC calls to a Conduit chain
• Fetching chain data: block numbers, balances, transaction receipts, contract reads
• The user mentions Conduit, Conduit chains, or any Conduit-hosted chain
• The user needs RPC access to a chain without running a node

Rules

Discovery

The gateway serves built-in discovery endpoints so agents can find available networks and pricing without prior knowledge:

curl https://mpp.conduit.xyz/openapi.json  # OpenAPI discovery document (machine-readable)
curl https://mpp.conduit.xyz/llms.txt      # LLM-friendly overview

API Reference

Troubleshooting

402 Payment Required

A 402 Payment Required response means a payment must be authorized or a channel opened for this network. You must follow these steps exactly:

1. First-Time Authorization (MANDATORY): You MUST STOP and ask the user for explicit permission to initiate the payment. Prompt the user: "Connecting to this network requires a small payment/deposit. Do you authorize this transaction?"
2. Wait for Input: Do NOT pass auto-confirm flags (such as -y or --yes) to any CLI commands. Wait for the user to explicitly approve the transaction.
3. Execute Protocol Flow: Once the user approves, proceed based on the response headers:
   • MPP: Extract the WWW-Authenticate header, create a credential with mppx, and retry the request with the Payment credential in the Authorization header.
   • (See the payment rule for your chosen protocol for additional details).
4. Autonomous Execution & Settlement: After the initial authorization, you may send subsequent off-chain signatures or vouchers automatically until the task is complete. When finished, you MUST settle the session to refund any unused deposits:
   • SDK users: Call session.close().
   • Tempo Wallet users: Run tempo wallet sessions close --all.

Session Management (Tempo Wallet)

When the user chose Tempo Wallet and you have completed a batch of RPC queries, you MUST follow this flow:

1. Ask the user before closing the session. Prompt exactly:

   "I've completed the queries. Would you like to make more RPC calls, or should I close the payment session?"

2. If the user wants more queries, continue making tempo request calls. The existing session stays open.
3. If the user is done, close the session:

   tempo wallet sessions close --all
   

4. You can also inspect active sessions at any time:

   tempo wallet sessions list
   

Do NOT close the session without asking the user first. Open sessions lock deposited funds in escrow; closing releases the unused balance back to the wallet.

404 Not Found

The path didn't match any network ID. Browse available networks on the Conduit Hub.

Resources

• Conduit
• Conduit Docs
• Conduit Hub
• MPP overview
• MPP pay-as-you-go guide