Description
Your OpenAI Dot only talks inside its own interface, so scripts, automation tools and SDKs have no way in. Dot2API is a self-hosted gateway that wraps your Dot in OpenAI and Anthropic compatible endpoints, so an existing client connects by changing nothing but the base URL.
It also skips what most 2API projects do: no reverse-engineered web interface and no OpenAI credentials involved. A request is queued, your Dot is woken through MCP Events, claims the task and returns the answer over MCP, and the gateway turns it back into an ordinary completion. The gateway never calls a model itself.
Two API dialects: OpenAI Chat Completions and Anthropic Messages, plus a model list and an asynchronous task API.
Streaming: SSE in both formats, with keep-alives while the Dot works so the connection does not drop mid-task.
Tasks that survive: durable storage, atomic claims, leases, bounded retries and deadlines, with automatic cancellation when the caller disconnects.
Wide client support: works with OpenAI and Anthropic compatible SDKs, automation tools and plain HTTP.
Security note: anyone holding an API key can prompt your Dot, which may reach your connected apps, so issue keys only to callers you trust.
It also skips what most 2API projects do: no reverse-engineered web interface and no OpenAI credentials involved. A request is queued, your Dot is woken through MCP Events, claims the task and returns the answer over MCP, and the gateway turns it back into an ordinary completion. The gateway never calls a model itself.
Features
Two API dialects: OpenAI Chat Completions and Anthropic Messages, plus a model list and an asynchronous task API.
Streaming: SSE in both formats, with keep-alives while the Dot works so the connection does not drop mid-task.
Tasks that survive: durable storage, atomic claims, leases, bounded retries and deadlines, with automatic cancellation when the caller disconnects.
Wide client support: works with OpenAI and Anthropic compatible SDKs, automation tools and plain HTTP.
Security note: anyone holding an API key can prompt your Dot, which may reach your connected apps, so issue keys only to callers you trust.
