@antseed/provider-openai-responses
v0.1.32
Published
OpenAI Responses provider plugin for Antseed via Codex backend auth
Readme
@antseed/provider-openai-responses
Provide OpenAI Responses API capacity on the AntSeed P2P network using Codex auth from ~/.codex/auth.json.
Important: Subscription-backed providers are for testing and development only. Reselling subscription credentials or raw access may violate upstream terms of service. AntSeed providers are expected to add value through agents, skills, privacy guarantees, TEEs, or managed products.
Installation
antseed plugin add @antseed/provider-openai-responsesUsage
antseed config seller add-provider openai-responses --plugin openai-responses
antseed config seller add-service openai-responses gpt-5 \
--input 10 --output 10 \
--categories chat,coding
antseed seller startConfiguration
| Key | Type | Required | Default | Description |
|-----|------|----------|---------|-------------|
| OPENAI_RESPONSES_AUTH_FILE | string | No | ~/.codex/auth.json | Path to Codex auth file |
| OPENAI_RESPONSES_BASE_URL | string | No | https://chatgpt.com/backend-api | Codex backend base URL |
| ANTSEED_INPUT_USD_PER_MILLION | number | No | 10 | Input token price (USD per 1M) |
| ANTSEED_OUTPUT_USD_PER_MILLION | number | No | 10 | Output token price (USD per 1M) |
| ANTSEED_SERVICE_PRICING_JSON | string | No | -- | Per-service pricing as JSON |
| ANTSEED_MAX_CONCURRENCY | number | No | 5 | Max concurrent requests |
| ANTSEED_ALLOWED_SERVICES | string[] | No | -- | Comma-separated service allowlist |
| ANTSEED_SERVICE_ALIAS_MAP_JSON | string | No | -- | Optional JSON map of announcedService -> upstreamService |
How It Works
The provider reads Codex credentials from the auth file, derives chatgpt-account-id from JWT claims, and forwards OpenAI Responses requests to https://chatgpt.com/backend-api/codex/responses.
If the access token is expired or close to expiry, the provider refreshes it automatically against https://auth.openai.com/oauth/token using the stored refresh token, then writes the updated credentials back to the auth file. It also forces a refresh and retries once if the upstream returns 401.
Transient upstream failures (429, 500, 502, 503, 504) are retried with exponential backoff.
