Documentation
The eroq API
One base URL, one bearer key, one unit of account. Every model — roleplay chat, image, video, speech, transcription — sits behind the same conventions, and every call has a flat credit price you can read off the pricing table.
The request and response shapes follow the OpenAI convention where one exists (chat/completions, images/generations, audio/speech), so existing client code usually ports by changing three strings: the base URL, the key, and the model id.
Guides
Quickstart
First call in five minutes.
Authentication
API keys and how to keep them safe.
Credits & billing
How metering works, packs, refunds on failure.
Streaming
Server-sent events for chat.
Errors
Error shape, codes, and how to handle 402.
Rate limits
Per-key caps and the Retry-After header.