The Qoder Cloud Agents API provides full management capabilities for cloud-hosted AI Agents, covering Agent creation, environment configuration, session management, event streaming, and more. All endpoints follow REST conventions and use JSON for requests and responses.Documentation Index
Fetch the complete documentation index at: https://docs.qoder.com/llms.txt
Use this file to discover all available pages before exploring further.
The API is currently in Beta. Some functionality may change in future releases.
Gateway URL
| Environment | URL |
|---|---|
| Production | https://api.qoder.com/api/v1/cloud |
Versioning
The API is currently at versionv1. All endpoints are versioned through the /v1/ URL prefix — no additional version header is required.
Available APIs
| Resource | Description | Base path |
|---|---|---|
| Agents | Agent CRUD and archival | /agents |
| Environments | Runtime environment configuration | /environments |
| Sessions | Agent session creation and lifecycle | /sessions |
| Events | Session event stream reads and pushes | /events |
| Files | File upload and association | /files |
| Vaults | Secure storage for sensitive credentials | /vaults |
| Skills | Agent skill registration and management | /skills |
| Memory Stores | Persistent memory storage | /memory_stores |
Request size limits
- Maximum request body size: 32 MB
- Requests exceeding this limit return
400 invalid_request_error.
Required headers
Every API request must include the authentication header; Content-Type is recommended but not mandatory — the server can auto-detect:Beta status
- The API surface is broadly stable, but signatures may receive minor adjustments in future iterations.
- New functionality ships behind new beta identifiers.
- Lock the API version and add compatibility handling when running in production.
- All current features are available without an additional Beta header.
Quick connectivity check
Rate Limiting
The API application layer currently has no active rate limiting. The gateway layer has global burst traffic suppression and DDoS protection, which may return 429 or 503 when triggered. Clients should implement exponential backoff retry for 5xx/429 (1s → 2s → 4s, max 3 retries).Next steps
- Authentication — obtain and use a PAT
- Errors — error codes and troubleshooting
- Pagination — pagination for list endpoints
- Idempotency — safe retries for write operations