Daya API Overview
Daya provides a unified API layer for teams that need to call multiple model families without rebuilding their integration stack for every provider. You can authenticate with one Daya API key, choose the protocol that matches your SDK, and centralize metering, billing, and observability in one place.
Protocols
OpenAI-compatible
- Base path:
https://api.dayaai.com/v1 - Best for: OpenAI SDKs, Responses API, Chat Completions, tools, structured output
- Core docs:
Anthropic-compatible
- Base path:
https://api.dayaai.com/v1 - Best for: Claude SDKs and Anthropic-native request shapes
- Core docs:
Google-compatible
- SDK base URL:
https://api.dayaai.com - REST path prefix:
/v1beta - Best for: Gemini-native client flows
- Core docs:
Platform APIs
- Base path:
https://api.dayaai.com/api/v1 - Best for: Daya-specific account balance, subscription, flow rate, and generation lookup APIs
- Core docs:
Authentication
Use your Daya API key in the Authorization header unless the target SDK requires a different header shape:
http
Authorization: Bearer <DAYA_API_KEY>You can create or manage keys from:
Base URLs At A Glance
| Protocol | Base URL |
|---|---|
| OpenAI-compatible | https://api.dayaai.com/v1 |
| Anthropic-compatible | https://api.dayaai.com/v1 |
| Google-compatible | https://api.dayaai.com (/v1beta REST path prefix) |
| Platform API | https://api.dayaai.com/api/v1 |
Recommended Starting Points
- Start with the Quickstart if you need your first successful request fast.
- Use the OpenAI-compatible endpoints if you want the broadest SDK support.
- Use the protocol-specific docs when you need SDK-native behaviors such as Anthropic Messages or Gemini-native calls.
- Use Get Generation for post-request auditing and billing lookups.