Manus Im Manus Integrations API
56
AI ReadinessFoundational (C)56/100
Agent-ready OpenAPI document · curated by JenticAI/MLLanguage ModelsapiKey13 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Hand off autonomous tasks to the Manus AI agent platform - including file upload, task creation, project grouping, and completion webhooks - through an API-key REST API.
Use for: Upload a PDF and create a Manus task to summarise it, Create a new Manus project for the Q3 research workstream, List all completed Manus tasks from the last 24 hours, Cancel the running Manus task with id task_123
Not supported: Does not handle direct LLM completions, embeddings, or fine-tuning - use for delegating long-running autonomous tasks to the Manus agent only.
Manus is an AI agent platform that runs autonomous tasks on behalf of a user; the Integrations API is the surface external systems use to feed work into Manus and read results back. Manus publishes its own OpenAPI document for this API, and Jentic maintains a curated, agent-optimized specification covering the same operations, kept validated and agent-ready. The endpoints cover files (upload and reference), tasks (create, list, update, delete), projects (group related tasks), and webhooks (receive completion notifications). Authentication uses an API key sent in the API_KEY header.
Install Jentic One Beta
Connect the Manus Integrations API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Manus Integrations API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmanus.im%2Fmanus" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmanus.im%2Fmanus" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Manus Integrations API.
Upload a file to Manus and reference it from a downstream task
Create a Manus task with a prompt, attached files, and target project
List active and completed tasks across the workspace
Group related tasks under a Manus project for organisation and reporting
Register a webhook to receive notification when a task finishes
Update or cancel a task before it completes
Use Cases
Patterns agents use Manus Integrations API for, with concrete tasks.
★ Hand off a long-running research task
Knowledge workers need an autonomous agent to run a multi-hour research job - gathering sources, comparing options, drafting a memo - without blocking the user. POST /v1/files uploads any seed documents, POST /v1/tasks creates the task with the prompt and file references, and the Manus agent executes asynchronously. A registered webhook delivers the result so the calling system can surface it when ready.
Upload a brief PDF, create a Manus task titled 'Compare top 3 vendors mentioned in the brief', and store the returned task_id.
Project-scoped task tracking
Teams running parallel Manus workstreams need each task associated with the right project for reporting and billing. POST /v1/projects creates a project, then POST /v1/tasks references the project_id when creating tasks. GET /v1/tasks filtered by project returns the per-project task list for status reviews.
Create a project named 'Customer Discovery Q3' and submit five Manus tasks under it, one per discovery interview.
Webhook-driven result handling
Apps that integrate Manus need to be told when tasks finish rather than poll. POST /v1/webhooks registers a callback URL; Manus posts the task id and outcome when the task completes, and the calling system can call GET /v1/tasks/{task_id} to retrieve the full result. This avoids long-poll loops on the client side.
Register the webhook https://app.example.com/manus/done and verify it fires by creating a short test task.
Agent-to-agent delegation through Jentic
An orchestrator agent inside Jentic can offload heavyweight, multi-step subtasks to Manus while focusing on user-facing dialogue. The orchestrator searches Jentic for 'create a manus task', loads the schema, and executes with the Manus API key kept in the vault. The orchestrator returns to the user as soon as Manus accepts the task and finalises when the webhook fires.
Given a user request 'do deep research on lithium battery suppliers', delegate to Manus by uploading a brief and creating a task, then return the task_id.
Key Endpoints
13 endpoints — manus is an ai agent platform that runs autonomous tasks on behalf of a user; the integrations api is the surface external systems use to feed work into manus and read results back.
METHOD
PATH
DESCRIPTION
POST
/v1/files
Upload a file
GET
/v1/files/{file_id}
Retrieve file metadata
POST
/v1/tasks
Create a Manus task
GET
/v1/tasks
List Manus tasks
GET
/v1/tasks/{task_id}
Retrieve a task and its result
PUT
/v1/tasks/{task_id}
Update an existing task
POST
/v1/projects
Create a project
POST
/v1/webhooks
Register a webhook
POST
/v1/files
Upload a file
GET
/v1/files/{file_id}
Retrieve file metadata
POST
/v1/tasks
Create a Manus task
GET
/v1/tasks
List Manus tasks
GET
/v1/tasks/{task_id}
Retrieve a task and its result
PUT
/v1/tasks/{task_id}
Update an existing task
POST
/v1/projects
Create a project
POST
/v1/webhooks
Register a webhook
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
M
Manus Integrations API
- Foundational (C)56/100
93
Foundational Compliance58
Developer Experience & Jentic Compatibility31
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
93
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
58
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
4%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
29%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
31
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
61%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
65%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Manus by hand means setting its API_KEY header, learning the /v1 files, tasks, and webhook endpoints, and polling task status yourself. Through Jentic you install once, import the Manus Integrations API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Scoping is by operation: you limit the agent to the operations it needs, such as creating a task, listing tasks, or reading a task's status, and leave out ones like registering webhooks or creating projects. Every operation you allow is one you have chosen, so the agent stays inside that set.
Credential isolation
Your Manus API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a Manus task' or 'check a task's status', and Jentic returns the matching Manus operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Manus Integrations API through Jentic.
Which OpenAPI specification does this Manus Integrations API page describe?
A curated, agent-optimized Jentic specification covering 13 Manus Integrations API operations. Manus also publishes its own OpenAPI 3.1.0 document at https://open.manus.ai/docs/v1/openapi.json, which describes the same 13 operations but is served with a trailing comma that strict JSON parsers reject. The Jentic variant is expressed as OpenAPI 3.0.3, parses cleanly, and is validated so agents and developers can load it through structured tooling. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Manus Integrations API use?
Manus uses an API key sent in the API_KEY header (declared as apiKey in the spec, despite the bearerAuth scheme name). Keys come from the Manus account UI. Through Jentic the API key is stored encrypted in the vault and injected at call time, so the raw key never enters the agent's prompt.
Can I attach files to a Manus task?
Yes. Upload the file with POST /v1/files first, capture the returned file_id, then reference that id in the file array on POST /v1/tasks. The agent can then read the uploaded content as part of executing the task.
What are the rate limits for the Manus Integrations API?
The spec does not publish hard rate limits. Manus is designed for relatively low-frequency, long-running tasks rather than high-QPS workloads, so rate limits are applied at the workspace level for task creation. Honour 429 responses with the Retry-After header rather than retrying immediately.
How do I create a Manus task through Jentic?
Run pip install jentic, then search Jentic for 'create a manus task'. Jentic returns the POST /v1/tasks operation with its input schema, which you execute with the prompt, optional file_ids, and optional project_id to hand the task off to the Manus agent.
How do I find out when a Manus task is done?
Register a webhook with POST /v1/webhooks pointing at your callback URL. Manus posts task lifecycle events to that URL when the task completes; your handler then calls GET /v1/tasks/{task_id} to fetch the full result. Polling is possible but webhooks are the recommended pattern.
Can I limit what my agent is allowed to do with the Manus Integrations API?
Yes. Because Jentic One is self-hosted, you decide which Manus operations the agent may call, and your own rules govern the stored API key. You can allow only the operations a job needs, such as creating a task, listing tasks, or reading a task's status, while leaving out others like registering webhooks or creating projects. Every operation the agent can reach is one you have explicitly granted, so it stays inside that set.
GET STARTED