FAQ & when not to use
Answers about where DragonLair fits, how access works, and what to expect from the control plane.
When not to use DragonLair
Choose something else — or wait — when you need:
- A fixed public price sheet without account-specific offers
- A turnkey analytics warehouse supplied as part of the gateway
- A guaranteed savings percentage independent of your workload
- A minimal single-provider proxy with no governance surface
- A general-purpose workflow runtime that replaces your agent framework
Full category framing: /compare.
When DragonLair fits
- Drop-in
POST /v1/chat/completions,GET /v1/models, embeddings (Partial OpenAI-compatible subset), plus documented native protocol PREVIEW surfaces — not full provider parity - Cost- and capability-aware routing with explainability headers (
X-Darouter-*) - Tenant-scoped BYOK and a prepaid wallet / usage-export path — not a black-box reseller
- Deterministic guardrails (PII / secrets / injection) on the chat path (first slices)
- Documented capabilities and explainable routing decisions
Common questions
Do you publish a vanity model count?
No. Catalog size is whatever the signed marketplace returns for your tenant after auth. We refuse absolute catalog-coverage marketing.
Is HTTP 200 quality or savings?
No. HTTP 200 means the gateway accepted and ran the request. Task success, quality floors, and dollar savings require evidence APIs (outcomes, proofs) — empty evidence stays empty.
Where is public pricing?
Current access terms are on the pricing page. Account-specific marketplace rates may appear after sign-in.
Is the portal the operator console?
No. The portal is the customer workspace for projects, keys, usage, policy, and account controls.
What about the optimizer?
Observe → Experiment → Evaluate → Promote/rollback among reviewed choices. No GA savings brochure claims. Details: /docs/optimizer.
Next steps
Where is the API contract?
OpenAPI is authoritative. Public docs show OpenAI Python / TypeScript / curl only — no first-party DragonLair SDK and no cookbook / recipe farm. Deeper behavior is guides + OpenAPI operations, not framework recipes.