Skip to content

Start building

Developers

Build on MyDeepAgents

Everything you build in the console you can also build in code. Call the API from your own servers, give your agents the tools of any MCP server, and let any system start a workflow with a webhook.

REST API

Create agents and workflows, start runs, stream answers as they are written, and run your whole organization from code with one key.

281 endpoints in 31 groups

Read the guideBrowse the reference

MCP servers

Connect any remote MCP server and hand its tools to agents and workflows, or serve your own agents, workflows and actions to Claude, Cursor and other AI apps. Every tool is approved or switched on one by one.

Both ways · Streamable HTTP · OAuth, keys or open

Read the MCP guide

Webhooks

Start workflows from any system with a signed request, and get signed events back when runs finish, approvals wait or anything else changes.

Both ways · HMAC-SHA256 signatures · retried for 24 hours

Read the webhooks guide

Your connection details

The same for every call, from any language.

Base URL
https://api.mydeepagents.com
Every path in these docs starts here.
OpenAPI document
api.mydeepagents.com/v1/openapi.json
OpenAPI 3.1, always matching the API that is running. Feed it to a client generator.
Authentication
Authorization: Bearer key
A key belongs to a service account, not a person.
Manage API keys
Version
v1
Changes inside v1 only ever add things.

Your first call in three steps

  1. Create a service account and a key

    In Settings → API keys, add a service account with the role it needs, then create a key for it and choose its scopes. Copy the key straight away: it is shown once.

  2. Keep the key out of your code

    Put it in an environment variable. Every sample in these docs reads it from MDA_API_KEY.

    Shell
    export MDA_API_KEY="mda_live_…"
  3. List your agents

    Every call works the same way: the key in the Authorization header, JSON in and JSON out.

    GET /v1/agents
    curl "https://api.mydeepagents.com/v1/agents?limit=20" \
      -H "Authorization: Bearer $MDA_API_KEY"

    A 200 with a list means you are in. A 401 means the key is wrong, revoked or expired; a 403 means its scopes don't include agent.view.

Not available yet

Designed and on its way. Until it arrives, do what the line suggests.

  • Rate-limit headers. Build retries for 429 and 503 anyway; budgets and model providers can answer with them.

Build with us

Ready for your first call?

Early access is open. Tell us what you want your agents to do, and we will help you get your first key.