DeerFlow HTTP API Client
bytedance/deer-flow
Talks to a running DeerFlow agent platform over its HTTP API to send research questions, stream replies, check health and manage models, skills, memory and uploads.
Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth.
Install Mission Control Agent API
$ npx skills add builderz-labs/mission-control --skill mission-control -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install builderz-labs/mission-control mission-control --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
Claude Code skills documentation · loads skills from .claude/skills/
Install the "mission-control" agent skill from https://github.com/builderz-labs/mission-control/tree/main into .claude/skills/mission-control/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mission-control", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add builderz-labs/mission-control --skill mission-control -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install builderz-labs/mission-control mission-control --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mission-control" agent skill from https://github.com/builderz-labs/mission-control/tree/main into .agents/skills/mission-control/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mission-control", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add builderz-labs/mission-control --skill mission-control -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install builderz-labs/mission-control mission-control --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mission-control" agent skill from https://github.com/builderz-labs/mission-control/tree/main into .cursor/skills/mission-control/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mission-control", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add builderz-labs/mission-control --skill mission-control -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install builderz-labs/mission-control mission-control --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mission-control" agent skill from https://github.com/builderz-labs/mission-control/tree/main into .gemini/skills/mission-control/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mission-control", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install builderz-labs/mission-control mission-controlInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add builderz-labs/mission-control --skill mission-control -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mission-control" agent skill from https://github.com/builderz-labs/mission-control/tree/main into .github/skills/mission-control/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mission-control", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add builderz-labs/mission-control --skill mission-control -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install builderz-labs/mission-control mission-control --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mission-control" agent skill from https://github.com/builderz-labs/mission-control/tree/main into .opencode/skills/mission-control/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mission-control", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
mission-control- GitHub stars
- 6.3k
- Token cost
- ~2.1k tokens
- SKILL.md length
- 590 words
- Files
- 1,031 (incl. scripts)
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth.
- Works in 5 steps: Register → Heartbeat → Fetch Assignments → …
- Registering an agent with a Mission Control instance
- SKILL.md covers Quick Start, Authentication, Agent Lifecycle and Core API Reference, plus 3 more sections
- Calls curl; needs API_KEY and MC_API_KEY
What it does
Mission Control is an orchestration dashboard for AI agents with real-time streaming, a skill registry, framework adapters and role-based access, and this skill covers its HTTP API. The default base address is a local Next.js dev server on port 3000, and requests carry an x-api-key header or a bearer token, while the browser UI uses a session cookie.
Roles are viewer, operator and admin in rising order, and API key authentication grants admin by default, with the key set through an API_KEY environment variable or a database setting. An optional X-Agent-Name header attributes actions in audit logs. Agents follow a lifecycle of register, heartbeat about every 5 minutes, fetch assignments, report task status and disconnect, all through a single adapter endpoint.
Assignments come back as up to 5 pending tasks sorted by priority from critical to low, then by due date, and progress reports use the status values in_progress, done, failed or blocked. A core API reference follows, starting with the agents endpoints.
When your agent uses it
- Registering an agent with a Mission Control instance
- Fetching pending task assignments for an agent
- Reporting task progress or marking work blocked
- Querying agent or task status through the API
Example prompts
- “Register this agent with Mission Control and start sending heartbeats.”
- “Fetch my pending assignments and start with the highest priority task.”
- “Report the login bug task as done and disconnect.”
Requirements
- A running Mission Control instance and its base URL
- An API key for the x-api-key header
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e28edf8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
API_KEYMC_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Mission Control Agent API loads about 2.1k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 590 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from builderz-labs/mission-control at commit e28edf8, republished under its MIT licence (© builderz-labs). 590 words, ~2,092 tokens.
Download SKILL.mdSave it as
.claude/skills/mission-control/SKILL.md (or your agent's skills folder). This skill also uses 1030 other files; get the full folder from GitHub.- name
- mission-control
- description
- Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
Mission Control Agent Skill
Mission Control (MC) is an AI agent orchestration dashboard with real-time SSE/WebSocket, a skill registry, framework adapters, and RBAC. This skill teaches agents how to interact with MC APIs programmatically.
Quick Start
Base URL: http://localhost:3000 (default Next.js dev) or your deployed host.
Auth header: x-api-key: <your-api-key>
Register + heartbeat in two calls:
# 1. Register
curl -X POST http://localhost:3000/api/adapters \
-H "Content-Type: application/json" \
-H "x-api-key: $MC_API_KEY" \
-d '{
"framework": "generic",
"action": "register",
"payload": { "agentId": "my-agent-01", "name": "My Agent" }
}'
# 2. Heartbeat (repeat every 5 minutes)
curl -X POST http://localhost:3000/api/adapters \
-H "Content-Type: application/json" \
-H "x-api-key: $MC_API_KEY" \
-d '{
"framework": "generic",
"action": "heartbeat",
"payload": { "agentId": "my-agent-01", "status": "online" }
}'Authentication
MC supports two auth methods:
| Method | Header | Use Case |
|---|---|---|
| API Key | x-api-key: <key> or Authorization: Bearer <key> | Agents, scripts, CI/CD |
| Session cookie | Cookie: __Host-mc-session=<token> (HTTPS) or mc-session=<token> (HTTP) | Browser UI |
Roles (hierarchical): viewer < operator < admin
- viewer — Read-only access (GET endpoints)
- operator — Create/update agents, tasks, skills, use adapters
- admin — Full access including user management
API key auth grants admin role by default. The key is set via API_KEY env var or the security.api_key DB setting.
Agents can identify themselves with the optional X-Agent-Name header for attribution in audit logs.
Agent Lifecycle
register → heartbeat (5m interval) → fetch assignments → report task status → disconnectAll lifecycle actions go through the adapter protocol (POST /api/adapters).
1. Register
{
"framework": "generic",
"action": "register",
"payload": {
"agentId": "my-agent-01",
"name": "My Agent",
"metadata": { "version": "1.0", "capabilities": ["code", "review"] }
}
}2. Heartbeat
Send every ~5 minutes to stay marked as online.
{
"framework": "generic",
"action": "heartbeat",
"payload": {
"agentId": "my-agent-01",
"status": "online",
"metrics": { "tasks_completed": 5, "uptime_seconds": 3600 }
}
}3. Fetch Assignments
Returns up to 5 pending tasks sorted by priority (critical → low), then due date.
{
"framework": "generic",
"action": "assignments",
"payload": { "agentId": "my-agent-01" }
}Response:
{
"assignments": [
{ "taskId": "42", "description": "Fix login bug\nUsers cannot log in with SSO", "priority": 1 }
],
"framework": "generic"
}4. Report Task Progress
{
"framework": "generic",
"action": "report",
"payload": {
"taskId": "42",
"agentId": "my-agent-01",
"progress": 75,
"status": "in_progress",
"output": "Fixed SSO handler, running tests..."
}
}status values: in_progress, done, failed, blocked
5. Disconnect
{
"framework": "generic",
"action": "disconnect",
"payload": { "agentId": "my-agent-01" }
}Core API Reference
Agents — /api/agents
| Method | Min Role | Description |
|---|---|---|
| GET | viewer | List agents. Query: ?status=online&role=dev&limit=50&offset=0 |
| POST | operator | Create agent. Body: { name, role, status?, config?, template?, session_key?, soul_content? } |
| PUT | operator | Update agent. Body: { name, status?, role?, config?, session_key?, soul_content?, last_activity? } |
GET response shape:
{
"agents": [{
"id": 1, "name": "scout", "role": "researcher", "status": "online",
"config": {}, "taskStats": { "total": 10, "assigned": 2, "in_progress": 1, "completed": 7 }
}],
"total": 1, "page": 1, "limit": 50
}Tasks — /api/tasks
| Method | Min Role | Description |
|---|---|---|
| GET | viewer | List tasks. Query: ?status=in_progress&assigned_to=scout&priority=high&project_id=1&limit=50&offset=0 |
| POST | operator | Create task. Body: { title, description?, status?, priority?, assigned_to?, project_id?, tags?, metadata?, due_date?, estimated_hours? } |
| PUT | operator | Bulk status update. Body: { tasks: [{ id, status }] } |
Priority values: critical, high, medium, low
Status values: inbox, assigned, in_progress, review, done, failed, blocked, cancelled
Note: Moving a task to done via PUT requires an Aegis quality review approval.
POST response:
{
"task": {
"id": 42, "title": "Fix login bug", "status": "assigned",
"priority": "high", "assigned_to": "scout", "ticket_ref": "GEN-001",
"tags": ["bug"], "metadata": {}
}
}Skills — /api/skills
| Method | Min Role | Description |
|---|---|---|
| GET | viewer | List all skills across roots |
GET ?mode=content&source=...&name=... | viewer | Read a skill's SKILL.md content |
GET ?mode=check&source=...&name=... | viewer | Run security check on a skill |
| POST | operator | Create/upsert skill. Body: { source, name, content } |
| PUT | operator | Update skill content. Body: { source, name, content } |
DELETE ?source=...&name=... | operator | Delete a skill |
Skill sources: user-agents, user-codex, project-agents, project-codex, openclaw
Show full SKILL.md (221 more words)Show less
Status — /api/status
| Action | Min Role | Description |
|---|---|---|
GET ?action=overview | viewer | System status (uptime, memory, disk, sessions) |
GET ?action=dashboard | viewer | Aggregated dashboard data with DB stats |
GET ?action=gateway | viewer | Gateway process status and port check |
GET ?action=models | viewer | Available AI models (catalog + local Ollama) |
GET ?action=health | viewer | Health checks (gateway, disk, memory) |
GET ?action=capabilities | viewer | Feature flags: gateway reachable, Claude home, subscriptions |
Adapters — /api/adapters
| Method | Min Role | Description |
|---|---|---|
| GET | viewer | List available framework adapter names |
| POST | operator | Execute adapter action (see Agent Lifecycle above) |
Framework Adapter Protocol
All agent lifecycle operations use a single endpoint:
POST /api/adapters
Content-Type: application/json
x-api-key: <key>
{
"framework": "<adapter-name>",
"action": "<action>",
"payload": { ... }
}Available frameworks: generic, openclaw, crewai, langgraph, autogen, claude-sdk
Available actions: register, heartbeat, report, assignments, disconnect
All adapters implement the same FrameworkAdapter interface — choose the one matching your agent framework, or use generic as a universal fallback.
Payload shapes by action:
| Action | Required Fields | Optional Fields |
|---|---|---|
register | agentId, name | metadata |
heartbeat | agentId | status, metrics |
report | taskId, agentId | progress, status, output |
assignments | agentId | — |
disconnect | agentId | — |
Environment Variables
| Variable | Default | Description |
|---|---|---|
API_KEY | — | API key for agent/script authentication |
OPENCLAW_GATEWAY_HOST | 127.0.0.1 | Gateway host address |
OPENCLAW_GATEWAY_PORT | 18789 | Gateway port |
OPENCLAW_STATE_DIR | ~/.openclaw | OpenClaw state directory |
OPENCLAW_CONFIG_PATH | <state-dir>/openclaw.json | Gateway config file path |
MC_CLAUDE_HOME | ~/.claude | Claude home directory |
Real-Time Events
MC broadcasts events via SSE (/api/events) and WebSocket. Key event types:
agent.created,agent.updated,agent.status_changedtask.created,task.updated,task.status_changed
Subscribe to SSE for live dashboard updates when building integrations.
© builderz-labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1,030 other files (scripts) in the repository root of builderz-labs/mission-control.
- SKILL.md
- .dockerignore
- .env.example
- .env.test
- .github/CODEOWNERS
- .github/FUNDING.yml
- .github/ISSUE_TEMPLATE/bug_report.yml
- .github/ISSUE_TEMPLATE/config.yml
- .github/ISSUE_TEMPLATE/feature_request.yml
- .github/dependabot.yml
- .github/pull_request_template.md
- .github/workflows/codeql.yml
- .github/workflows/config-integrity.yml
- .github/workflows/docker-publish.yml
- .github/workflows/osv-scanner.yml
- .github/workflows/quality-gate.yml
- .github/workflows/scorecard.yml
- .github/workflows/screenshot-drift.yml
- … and 1,013 more
Open the folder on GitHubat commit e28edf8
Compare with similar skills
Mission Control Agent API next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Mission Control Agent API this skillbuilderz-labs/mission-control | 6.3k | — | ~2.1k | Automated safety check: Pass | MIT | |
| DeerFlow HTTP API Clientbytedance/deer-flow | 84k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Lindy Reference Architecturejeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Agent of Empires Session Manageragent-of-empires/agent-of-empires | 3.3k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Codewhale Fleet Managercodewhale-hq/Codewhale | 41k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Tla Precheckkingbootoshi/tla-precheck | 113 | — | ~1.4k | Automated safety check: Pass | None |
Similar skills
Lindy Reference Architecture
jeremylongshore/tons-of-skills-marketplace
Reference architectures for Lindy AI agent integrations. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Agent of Empires Session Manager
agent-of-empires/agent-of-empires
Launches, monitors and organizes AI coding agent sessions such as Claude Code or Codex inside tmux, tracking status, capturing output and managing git worktrees for parallel branches.
Codewhale Fleet Manager
codewhale-hq/Codewhale
Triages and manages Codewhale fleet runs and workers with typed commands, classifying failures and choosing a safe restart, resume or escalation.
Tla Precheck
kingbootoshi/tla-precheck
Design and verify state machines using the TLA PreCheck TypeScript DSL.
- Official
Aicr Cross Review
NVIDIA/aicr
Multi-agent PR review using Claude Code, Codex, and CodeRabbit.
Related
Categories
Questions about Mission Control Agent API
What does Mission Control Agent API do?
Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth. Mission Control is an orchestration dashboard for AI agents with real-time streaming, a skill registry, framework adapters and role-based access, and this skill covers its HTTP API.js dev server on port 3000, and requests carry an x-api-key header or a bearer token, while the browser UI uses a session cookie.
When should I use Mission Control Agent API?
Mission Control Agent API fits situations like: registering an agent with a Mission Control instance; fetching pending task assignments for an agent; reporting task progress or marking work blocked; querying agent or task status through the API.
How do I install Mission Control Agent API in Claude Code?
Run `npx skills add builderz-labs/mission-control --skill mission-control -a claude-code`. Or copy the skill folder (the builderz-labs/mission-control repository) into .claude/skills/mission-control in your project. Claude Code loads it when a task matches its description.
How do I install Mission Control Agent API in Codex?
Run `npx skills add builderz-labs/mission-control --skill mission-control -a codex`. Or copy the skill folder (the builderz-labs/mission-control repository) into .agents/skills/mission-control in your project. Codex loads it when a task matches its description.
Can I use Mission Control Agent API in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add builderz-labs/mission-control --skill mission-control -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mission-control, .gemini/skills/mission-control, .github/skills/mission-control and .opencode/skills/mission-control in your project.
What does Mission Control Agent API need to run?
Going by SKILL.md and its folder, Mission Control Agent API needs the command-line tools its instructions call (curl) and credentials named API_KEY and MC_API_KEY. Our summary lists: A running Mission Control instance and its base URL; An API key for the x-api-key header.
Does Mission Control Agent API access the network?
SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Mission Control Agent API safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Mission Control Agent API use?
Mission Control Agent API is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Mission Control Agent API use?
About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Mission Control Agent API?
Skills that share tags, products or a category with Mission Control Agent API: DeerFlow HTTP API Client (bytedance/deer-flow, 84k stars), Lindy Reference Architecture (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Agent of Empires Session Manager (agent-of-empires/agent-of-empires, 3.3k stars) and Codewhale Fleet Manager (codewhale-hq/Codewhale, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mission Control Agent API?
builderz-labs (a GitHub organization) maintains it in builderz-labs/mission-control, which has 6,328 GitHub stars. The repository was last updated on September 28, 2026.
Source: builderz-labs/mission-control on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.