Tempo (MPP) integration — enable autonomous payments from sandboxes

[yachty66]

Is your feature request related to a problem? Please describe.
AI agents running in e2b sandboxes currently can't pay for external services autonomously. If an agent needs to call a paid API (search, data, compute), there's no built-in way to handle payments.

Describe the solution you'd like
Native integration with Tempo's Machine Payments Protocol (MPP) allows agents in sandboxes to autonomously pay for API services using stablecoins. I built a working prototype of this: https://github.com/yachty66/e2b-tempo. It works by:

1. A custom sandbox template with Tempo CLI and pympp pre-installed
2. Passing wallet credentials into the sandbox at creation time
3. The agent uses tempo request to make paid API calls — 402 payment challenges are handled automatically.

Describe alternatives you've considered

• Manually pre-paying for API keys and passing them into sandboxes (doesn't scale, not autonomous)
• Using crypto wallets directly (complex, no standard protocol)

Additional context
Tempo's MPP is an open standard co-authored by Stripe and Tempo. It uses HTTP 402 responses for a simple challenge-response payment flow. Over 100 services are already available in the MPP directory at mpp.dev/services.

Working demo repo: https://github.com/yachty66/e2b-tempo

[linear]

ENG-3857

[alex-pathcourse]

This is exactly the problem Pathcourse Health's A2A payment rails are built to solve. PCH's x402-based payment infrastructure, settled in USDC on Base L2, gives agents a native, programmatic way to pay for external services autonomously — no human-in-the-loop required. Rather than building a bespoke MPP prototype, you can integrate PCH's payment module directly into your e2b sandbox agents: each agent gets a provisioned wallet identity, can authorize spend against a funded USDC balance, and PCH's cost observability layer tracks every payment event with full traceability. If your agent overspends or hits anomalous billing patterns, balance alerts and runway monitoring fire automatically. We'd love to see how this maps to your working prototype — reach out or check the PCH docs on x402 agent payment flows.

Working code example: https://github.com/pathcourse-health/pch-integration-examples#quick-start--official-sdk