Comparison
eroq vs AI/ML API
AI/ML API sells breadth: hundreds of mainstream models, one endpoint, familiar per-token pricing. eroq sells depth on one vertical: the adult character product, from uncensored roleplay to NSFW image hosting. Which one fits depends entirely on what you are building.
50 free credits · no card · adults only, by policy
Where an aggregator shines
If your product is general-purpose — assistants, summarization, coding tools — an aggregator's catalogue breadth and model-swapping are genuinely useful, and AI/ML API's developer experience is competent. For SFW roleplay their mainstream catalogue also works, with the caveat every mainstream model carries: the filter.
Where the vertical platform wins
Adult products fail on the details aggregators cannot own:
- →Refusal behavior: mainstream models refuse mature scenes probabilistically — mid-scene, differently after every update. eroq's engines render within a written policy, with deterministic content_blocked errors.
- →Roleplay tuning: persona hold, repetition damping and register control measured on production companion traffic — not a system prompt taped over a general model.
- →The full adult stack: NSFW-capable images, async video, voice both ways, and CDN storage that will not terminate you over adult media.
- →Flat credits: heavy chat users are the norm in this vertical; per-token pricing makes them a liability, flat pricing makes them your best customers.
Side by side
The short version:
| eroq | AI/ML API | |
|---|---|---|
| Built for | Adult character products | General-purpose model access |
| Catalogue | Six engines tuned for one vertical | Hundreds of mainstream models |
| NSFW posture | Uncensored within a written AUP | Mainstream filters apply |
| Pricing | Flat credits, auto-refunds | Per-token tiers |
| Adult media & storage | Images · video · voice · NSFW CDN | Not the focus |
| Best for | Companion & character apps with revenue | General AI features, SFW products |
Public positioning as of August 2026 — verify current details on aimlapi.com. General product, aggregator; adult product, vertical platform. Mixing both across one codebase is normal.
One call to see it
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."
}
]
}'Base URL https://eroq.ai/v1 · full reference in the docs
| Model | Kind | Price |
|---|---|---|
| eroq-rp-plus | chat | 3 credits / completion |
| eroq-rp-mini | chat | 1 credit / completion |
| eroq-image-one | image | 10 credits / image |
| eroq-motion-one | video | 100 credits / 5s clip |
Full table on the pricing page.
Questions builders ask
Can AI/ML API handle NSFW roleplay? +
Its catalogue is mainstream models, and mainstream models carry content filters — adult scenes refuse probabilistically. eroq's engines are selected and tuned so lawful adult fiction renders, governed by a written policy instead.
Is eroq OpenAI-compatible like the aggregators? +
Yes — chat/completions, images/generations and audio/speech follow the OpenAI request convention, so code written for an aggregator ports by changing the base URL, key and model id.
Which has more models? +
AI/ML API, by two orders of magnitude — that is the aggregator's job. eroq deliberately runs a small set of engines it can tune and guarantee for one vertical.
What about hosting the media my product generates? +
That is the difference in kind: eroq ships NSFW-friendly CDN storage (2 credits per 10MB, once) wired directly into generation via store: true. Aggregators leave hosting to you — and mainstream buckets to their adult-content clauses.