Platform · Developers
Developer APIs: your agents, callable
VegaDūta exposes a REST developer API under /api/dev/v1 for calling your agents and workflows from your own code. Access is governed by scoped API keys — a key carries only the permissions you grant it — with rate limits applied per key. The same key system powers the platform's MCP server, so one credential model covers both plain HTTP integrations and MCP-native tools.
REST access to agents and workflows
Anything you build in the console becomes callable: invoke an agent, start a workflow, and integrate the results into your own product or back office. The API speaks plain REST under /api/dev/v1, so it works from any language with an HTTP client, without an SDK dependency.
Scoped keys and rate limits
API keys are scoped, not all-powerful: each key carries an explicit set of permissions, so a key that only needs to run one workflow cannot read your knowledge base. Rate limits are enforced per key, keeping a misbehaving integration from starving the rest of your tenant.
One key system, two surfaces
The same scoped keys authenticate the MCP server surface, which presents a curated set of five tools to clients like Claude and other MCP-capable hosts: list_my_agents, call_agent, list_my_workflows, call_workflow, and search_knowledge. Build against REST, MCP, or both — the credential you manage is the same either way.
Where to start
Create a key, scope it to what your integration actually needs, and make your first call against /api/dev/v1. The docs at /docs cover authentication and endpoints, and the MCP page explains when the MCP surface is the better fit than raw REST — typically when the caller is itself an AI tool.
Frequently asked questions
Does VegaDūta have an API for calling agents programmatically?
Yes. The REST developer API under /api/dev/v1 lets your code invoke agents and start workflows, authenticated with scoped API keys and subject to per-key rate limits. It is plain REST, so any HTTP client works.
How are VegaDūta API keys scoped?
Each key carries an explicit set of permissions rather than blanket tenant access, so you can issue a key that only runs a specific surface of your account. Rate limits apply per key, which isolates one integration's traffic from another's.
What is the relationship between the developer API and the MCP server?
They share the same key system. The REST API is for conventional code integrations; the MCP server presents five curated tools — list_my_agents, call_agent, list_my_workflows, call_workflow and search_knowledge — for AI clients. One scoped key can authenticate either surface.
Can I try the API without a paid plan?
You can explore the platform without signing up at /try, and API access follows your plan's limits once you have an account. Plan details are at /billing; the API itself is documented at /docs.
See it working in two minutes
The sandbox provisions a real tenant — describe an agent in one sentence and test it, no account, no card. Or browse ~90 industry workflow recipes to see what teams build.
