What you can do with the API
Manage agents programmatically
Create, update, delete agents and run executions, pause or resume them, complete runs, and trigger evaluations.
Power conversational assistants
Send messages to assistants, retrieve chat histories and integrate them directly inside your product.
Configure tool servers
Create and manage tool servers with their tools, authentication, and test tool calls programmatically.
Monitor quality with evaluations
Score outputs, audit behaviour and receive structured feedback using Devic’s evaluation engine.
FinOps and cost visibility
Retrieve daily, monthly and aggregated cost data for each agent.
Health checks
Verify API availability using a dedicated health endpoint.
API surface at a glance
The Devic API is divided into the following groups:Agents
- Create, list, update and delete agents
- Create and list agent threads
- Pause, resume or complete executions
- Trigger evaluations
- Retrieve evaluation results
- Retrieve daily, monthly and summary costs
Assistants
- List available assistants
- Send messages
- Retrieve chat histories
- Filter conversations across assistants
Tool Servers
- Create, list, update and delete tool servers
- Manage tool definitions within servers
- Configure authentication (JWT, OAuth2, Basic, Custom Headers)
- Test tool calls programmatically
- Clone tool servers
Documentation
- List available docs
- Retrieve rendered HTML or markdown
Health
- Basic availability checks
View OpenAPI specification
Download the OpenAPI specification used to generate this API reference.
Environments and base URLs
Devic offers separate environments for development and production.Production
https://api.devic.aiStaging
https://staging-api.devic.ai Example full endpoint: GET https://api.devic.ai/v1/agents/{agentId}/threadsAuthentication
All Devic API requests require a Bearer token. Include your token in every request using theAuthorization header:
Header format:
Authorization: Bearer YOUR_API_TOKEN
Example request:
GET https://api.devic.ai/v1/agents/{agentId}/threads
Authorization: Bearer YOUR_API_TOKEN
Content-Type: application/json
Invalid or missing tokens return 401 Unauthorized.
Typical workflows
1. Managing agents
- Create an agent POST /v1/agents
- List all agents GET /v1/agents
- Update or delete an agent PATCH /v1/agents/ DELETE /v1/agents/
Start with agents
Create your first agent programmatically.
2. Running an agent
- Create a thread POST /v1/agents//threads
- Monitor or control the execution GET /v1/agents/threads/ POST /v1/agents/threads//pause POST /v1/agents/threads//resume POST /v1/agents/threads//complete
- Trigger or fetch evaluations POST /v1/agents/threads//evaluate GET /v1/agents/threads//evaluations
- Inspect costs GET /v1/agents/agents//costs/daily GET /v1/agents/agents//costs/monthly GET /v1/agents/agents//costs/summary
Run agent threads
Create execution threads for your agents.
3. Conversational assistants
- List assistants GET /v1/assistants
- Send messages POST /v1/assistants//messages
- Retrieve chat history GET /v1/assistants//chats/ GET /v1/assistants//chats POST /v1/assistants/chats
Start with assistants
Learn how to send your first message to an assistant.
4. Managing tool servers
- Create a tool server with tools POST /v1/tool-servers
- List and get tool servers GET /v1/tool-servers GET /v1/tool-servers/
- Manage tools in a server GET /v1/tool-servers//tools POST /v1/tool-servers//tools PATCH /v1/tool-servers//tools/ DELETE /v1/tool-servers//tools/
- Test tool calls POST /v1/tool-servers//tools//test
- Clone a tool server POST /v1/tool-servers//clone
Start with tool servers
Create and configure tool servers programmatically.
Error handling
Most endpoints return structured error objects. Common status codes:- 400 — Invalid input
- 401 — Missing or invalid token
- 404 — Resource not found
- 429 — Rate limit exceeded
- 500 — Internal server error