eroq api · text
Expressive AI,
one API.
The uncensored roleplay engine behind millions of conversations, in an OpenAI-shaped chat API. Persona context, streaming, vision — and scenes that render instead of hitting a refusal wall.
NSFW-friendly by policy · adults only, always
50 free credits on signup · no card required
curl https://eroq.ai/v1/chat/completions \
-H "Authorization: Bearer $EROQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "eroq-rp-plus",
"context": "Mira: sardonic starship mechanic, dry humor, hates small talk. Scene: engine bay, mid-shift.",
"messages": [
{
"role": "user",
"content": "The reactor is making that noise again."
}
]
}'The models
2 models. Flat prices.
RP+
chateroq-rp-plus
Our production roleplay engine: stays in character across long scenes, tuned sampling against repetition and filler, streams over SSE. The model behind millions of conversations on our consumer network.
3 credits / completion
RP mini
chateroq-rp-mini
The economical tier for high-volume products. Same API shape and same persona handling as RP+, sized for latency and cost.
1 credit / completion
What you get
Text, built for products that ship.
Stays in character
RP+ is tuned for persona work: repetition damping, filler suppression, and sampling that survives 200-message scenes. A context field carries the character sheet; a messaging mode answers like texting when your product is DMs, not novels.
Uncensored by design
Fiction goes where your users take it. Adult roleplay between adult characters renders instead of refusing — the wall is a written acceptable-use policy (no minors, no real people, ever), not a filter's mood.
Streaming first
Server-sent events with the standard chunk format. First tokens reach your UI while the model is still writing, and the shape is the one your existing client already parses.
It can see
Send an image alongside the messages and the model reacts to it in character — the missing half of a companion product, where users send pictures and expect to be seen.
Flat per reply
One credit on RP mini, three on RP+, whatever the length of the reply or the size of the context you send. Per-user costs stay predictable as scenes get long, which is exactly when token pricing stops being.
Two tiers, one shape
RP+ for the turns that carry a scene, RP mini for volume. Identical API and persona handling, so routing between them is a model string and nothing else.
In the reference
Keep reading
FAQ
The short version.
Is the chat API OpenAI-compatible? +
The request and response shapes follow the OpenAI convention, so most client code ports by changing the base URL, the key and the model id. We are not affiliated with OpenAI.
What does a reply cost? +
One credit on RP mini and three on RP+, flat. The price does not move with reply length or context size.
Will the model refuse my users mid-scene? +
The engines are chosen so adult scenes render rather than hitting a refusal wall. A request outside the acceptable-use policy returns an explicit content_blocked error instead of a lecture, and is never charged.
Are there embeddings or tool calling? +
No. There is no embeddings endpoint and no tool-calling surface. Keep a mainstream API for retrieval and agents, and route the character work here.
Is there a context window limit? +
Long scenes are what these models are tuned for, but they are not infinite. Summarise older turns into the context field rather than resending an entire history, which also keeps latency flat.
First call in five minutes.
Sign up, create a key, paste the quickstart. 50 free credits are enough to try every model, and plans start at $15.