Create sandboxed code-execution environments via Modal, paid per call over MPP/Tempo.
What it does
This MPP endpoint is intended to create on-demand sandboxes for code execution, powered by Modal's serverless GPU compute infrastructure. It is listed on the Tempo MPP marketplace and would settle payments in pathUSD on the Tempo L2 network.
However, during probing the endpoint returned HTTP 404 on both HEAD and GET requests rather than the expected 402 Payment Required challenge. The provider's root domain (modal.mpp.tempo.xyz) also returns 404 across all tested paths including /docs, /api, /pricing, and /README. No OpenAPI schema, MPP challenge details, or documentation were recoverable from the crawl.
Because no 402 challenge was captured and every probed path returns 404, the endpoint appears to be either not yet deployed, temporarily offline, or decommissioned. There is insufficient information to determine pricing, request/response schemas, or supported parameters. Users should verify availability before attempting integration.
Capabilities
Use cases
- —Running untrusted code in an isolated sandbox
- —Executing AI/ML workloads on demand
- —Providing ephemeral compute environments for agent tool use
Fit
Best for
- —AI agents needing on-demand code execution
- —Sandboxed evaluation of user-submitted code
- —Serverless GPU workloads paid per invocation
Not for
- —Long-running persistent compute jobs
- —Users needing a currently live and documented endpoint
- —Workloads requiring guaranteed uptime SLAs
Quick start
# Endpoint is currently returning 404; verify availability before use.
curl -X POST https://modal.mpp.tempo.xyz/sandbox/create \
-H "Content-Type: application/json" \
-d '{"code": "print(hello world)"}'Endpoint
Quality
The endpoint returns 404 on all probed methods and paths. No MPP 402 challenge, schema, documentation, or pricing information was recoverable. The listing is effectively a stub based solely on the existing title and description.
Warnings
- —Endpoint returned 404 on HEAD and GET — no MPP 402 challenge captured; endpoint may be offline or decommissioned.
- —Root domain and all documentation paths return 404.
- —No pricing, schema, or usage documentation available.
- —Request and response formats are entirely unknown.