Authentication
Use DAXI customer keys for downstream access. Keys carry model scope, scenario permission, quota, and rate limit.
API DOCS & ACCESS GUIDE
Start with familiar API patterns and scenario-aware usage control.
This first-phase documentation page gives customers a clear route to API keys, token packages, model calls, video workflows, and operational support.
Quick request
curl https://api.daxicloud.com/v1/chat/completions \
-H "Authorization: Bearer DAXI_CUSTOMER_KEY" \
-H "X-DAXI-Scenario: ecommerce-video" \
-d '{ "model": "daxi-smart-router", "messages": [...] }'REFERENCE STRUCTURE
Keep the first docs practical and implementation-facing.
Model API
OpenAI-compatible chat, completion, embedding, and routing endpoints for common SDK compatibility.
Video Tasks
Short drama and e-commerce video tasks can start as form and workflow submissions, then evolve into task APIs.
Token Billing
Prepaid token packages, customer balance, usage by key, model, scenario, and monthly export records.
Scenario Headers
Use scenario tags such as model-api, short-drama, ecommerce-video, agent, or compute-inquiry for analytics.
Support Path
Trial customers use Get Started; business customers can request PoC, quote, or custom deployment support.
FIRST-PHASE ACCESS FLOW
Docs should route customers into action, not just explain APIs.
1. Submit requirementCustomer selects API, video, Agent, or compute scenario.
2. Assign token packageDAXI creates downstream customer access and quota.
3. Test endpointCustomer uses DAXI-compatible API endpoint and scenario headers.
4. Review usageAdmin console tracks customer usage and upstream settlement state.