Developers

Build on Manifest from your own code.

Call any agent over a REST API with streaming and structured replies, manage your agents from Claude Code or any MCP client, and give each of your customers their own agent workspace.

agents.manifestautomation.com
# Run an agent and stream its reply POST /a/your-team/agents/api/post/?stream=true # Read one turn: status, reply, token usage GET /a/your-team/agents/api/turns/<agent_event_id>/ # MCP connector for Claude Code and other clients https://agents.manifestautomation.com/mcp # Give a customer their own workspace POST /api/products/your-saas/teams/provision/
● stream data: {"event": "progress", ...} data: {"event": "response", ...}

REST API

Call any agent over HTTP.

Every agent and workflow on your team has the same endpoint. Send a message or any JSON, describe the answer you want as a JSON Schema, and get structured data back.

Terminal
# Run the support-triage workflow and stream the reply curl -N \ "https://agents.manifestautomation.com/a/your-team/agents/api/post/?stream=true" \ -H "Authorization: Api-Key $MANIFEST_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "task_slug": "support-triage", "client_run_key": "ticket-4182", "request_data": {"message": "Summarize this ticket and draft a reply"}, "response_schema": { "type": "object", "properties": { "summary": {"type": "string"}, "reply": {"type": "string"} }, "required": ["summary", "reply"] } }'
# Server-Sent Events, abridged data: {"event": "connected", "message": "Stream connected"} data: {"event": "progress", "data": {"event_description": "..."}} data: {"event": "response", "conversation_id": "...", "data": {"response_data": {"summary": "...", "reply": "..."}}}
AuthorizationApi-Key and your key. Create keys in the console under API Keys. Each key is shown once and acts with its owner's role.
task_slugRuns one workflow. Leave it out and the team agent answers.
request_dataThe input: a chat message, or any JSON your workflow expects.
response_schemaA JSON Schema. The answer comes back as response_data in that shape.
client_run_keyYour own ID for the conversation, such as a ticket number. Send it again to continue the same conversation.
?stream=trueServer-Sent Events: progress while the agent works, then the response. Without it, the post returns a conversation ID at once and you read the turn when it is done.
stream_text_fieldStreams one text field of the answer as it is written, with execution=worker. Available on OpenAI models.

MCP connector

One URL for Claude Code and any MCP client.

Manifest runs its own MCP server over streamable HTTP. Add it with one command, then sign in through your browser with Google or email and approve access. There is no key to copy.

Other clients that support remote MCP servers use the same URL. They find our OAuth server through standard discovery and register themselves. On a machine without a browser, send an API key in the Authorization header instead.

# Add the connector to Claude Code claude mcp add --transport http manifest-agents \ https://agents.manifestautomation.com/mcp # Then sign in, inside Claude Code /mcp # No browser? Use an API key instead claude mcp add --transport http manifest-agents \ https://agents.manifestautomation.com/mcp \ --header "Authorization: Bearer $MANIFEST_API_KEY"

What the connector can do

list_teamsThe teams you belong to. Everything else is scoped to a team.
list_tasks · get_task · update_taskRead and edit workflows: instructions, model and tools. Editing needs an admin.
list_task_runs · get_task_run_eventsRuns and their full event timelines.
list_mcp_servers · list_knowledge_sourcesYour team's integrations and knowledge sources.
run_agent · get_agent_responseSend a message to an agent and read its reply.
manifest_api_request · list_api_endpointsFind and call any platform REST endpoint as yourself.

The connector acts as you. It sees only your teams and can do only what your role allows in the console.

Claude Code plugin

Run your agents from Claude Code.

The manifest-agents plugin packages the MCP connector for Claude Code: the same server, the same sign-in and the same tools. Ask us for plugin access, or add the connector directly in three steps.

01Add the connector
Run this once in your terminal. It works from any directory.
claude mcp add --transport http manifest-agents \ https://agents.manifestautomation.com/mcp
02Sign inRun /mcp in Claude Code. Your browser opens the Manifest sign-in, then a consent screen. Approve it, and Claude Code refreshes its session by itself from then on.
03Ask in plain words
Claude Code picks the right tools. For example:Show me today's failed runs of support-triage and what went wrong.Tighten the instructions of the weekly-report workflow so it always lists open risks first.

Agents for Products API

Give every customer their own agent workspace.

For SaaS teams. Define your agents once as versioned templates. One call provisions a customer: an isolated workspace with its own copy of every agent, its own knowledge and its own conversations, mapped to your customer ID.

✓Publish a template version, then roll it out to every customer in one call, or hold one customer on an earlier version ✓Run a customer's agent from your backend, streamed or not ✓Name your own end user on a post and the turn runs as that person, with their permissions ✓Agents call your MCP server with a signed token that names the customer and the user ✓Erase an end user's conversations and data by your own ID
How Agents for Products works →
Terminal
API=https://agents.manifestautomation.com/api/products/your-saas AUTH="Authorization: Api-Key $MANIFEST_API_KEY" # Give a new customer their own workspace curl -X POST "$API/teams/provision/" -H "$AUTH" \ -H "Content-Type: application/json" \ -d '{"name": "Acme Corp", "external_id": "cust_123"}' # 201 Created {"team_slug": "acme-corp", "external_id": "cust_123", "shell_tasks": [{"task_slug": "customer-support", ...}]} # Roll the published version out to every customer curl -X POST "$API/templates/customer-support/push-upgrade/" \ -H "$AUTH"

Documentation

Full developer docs are coming.

A documentation site with guides for the API, streaming, the MCP connector and the Agents for Products API is on its way. Until then, we help each team with its first integration.

Tell us what you are building.

We onboard every team directly. Tell us what you want to connect, and we will help you ship the first integration.

Talk to us