MPP-proxied OpenAI Responses API (GPT-4o, Codex, etc.) settled via Tempo L2
What it does
This endpoint proxies the OpenAI Responses API through the Tempo MPP (Micropayment Protocol) gateway at openai.mpp.tempo.xyz. The Responses API is OpenAI's newer unified interface that supports models like GPT-4o, Codex, and others, returning structured responses. Payments are expected to settle on Tempo L2 using pathUSD.
The endpoint is located at /v1/responses, which mirrors the OpenAI Responses API path. Because the OpenAI Responses API uses POST requests, the probe's HEAD/GET attempts returned 404 rather than the expected 402 MPP challenge. This is consistent with a method-restricted endpoint rather than a dead service, though without a successful POST probe the liveness cannot be fully confirmed.
Documentation, pricing details, and schema information are not available from the proxy itself — all crawled paths (root, /docs, /api, /pricing, /README) returned 404. The listing description states "price varies by model," suggesting per-call charges that differ depending on which OpenAI model is invoked. Without a captured 402 challenge or OpenAPI spec, exact pricing and supported parameters remain unknown.
Capabilities
Use cases
- —AI agents that need LLM completions without managing OpenAI API keys or billing accounts
- —Pay-per-call access to OpenAI models settled in pathUSD on Tempo L2
- —Building agentic workflows that chain LLM calls with crypto-native payment rails
Fit
Best for
- —Agents or services that want OpenAI model access via crypto micropayments
- —Developers already integrated with the Tempo/MPP ecosystem
- —Use cases requiring per-request billing without subscription commitments
Not for
- —High-volume production workloads where direct OpenAI billing is cheaper
- —Users who need guaranteed SLA or official OpenAI support channels
- —Applications requiring non-LLM OpenAI endpoints (DALL·E, Whisper) — those may be separate proxies
Quick start
curl -X POST https://openai.mpp.tempo.xyz/v1/responses \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <MPP_TOKEN>" \
-d '{"model":"gpt-4o","input":"Hello, world!"}'Example
Request
{
"input": "Explain micropayment protocols in one paragraph.",
"model": "gpt-4o"
}Endpoint
Quality
No 402 challenge was captured (HEAD/GET returned 404, likely because the endpoint only accepts POST). All crawled documentation paths returned 404. No schema, no pricing details, and no confirmed liveness. The listing is effectively a stub based on the Bazaar description and URL structure alone.
Warnings
- —Endpoint returned 404 on HEAD and GET probes; likely POST-only but liveness is unconfirmed
- —No MPP 402 challenge captured — payment terms (amount, currency, intent) are unknown
- —All documentation and pricing URLs returned 404
- —Exact supported models and per-model pricing are not documented at the proxy
- —Example request/response are inferred from OpenAI's public Responses API format, not from this proxy's actual schema
Citations
- —The endpoint is listed as 'Responses API (Codex, GPT-4o, etc.) - price varies by model' and is part of an OpenAI proxy group on Tempo MPPhttps://openai.mpp.tempo.xyz/v1/responses
- —All crawled paths (root, /docs, /api, /pricing, /README) returned 404 Not Foundhttps://openai.mpp.tempo.xyz