Manus

Read one agent by id: its nickname, its description and its configuration via GET /v2/agent.detail

List the Manus agents on this account, with the ids agent.detail takes and the task listing's `agent_subtask` scope filters on via GET /v2/agent.list

List the user's own browser clients that are online right now and therefore available to a task. On an OAuth connection this is what the `use_my_browsers` scope covers via GET /v2/browser.onlineList

List the connectors -- Manus's own third-party integrations -- this credential may name in a task message. On an OAuth connection this needs the `use_connectors` scope AND the specific connector UIDs selected on the Open App, and a connector the user revoked simply disappears from here via GET /v2/connector.list

Read one uploaded file's metadata by id via GET /v2/file.detail

List the projects this credential can see, with the ids that task.create and skill.list take via GET /v2/project.list

List the user's global skills, plus a project's own skills when `project_id` is given via GET /v2/skill.list

Read one task by id: its status and stop reason, title, the credits it consumed, its task and share URLs, and the structured output when a schema was armed via GET /v2/task.detail

List the tasks this credential can see, newest first by default, filtered by scope (all, standard, project or agent_subtask), by agent, by project, or by the Open App or API key that created them. AN OAUTH TOKEN HOLDING ONLY `create_task` SEES ONLY THE TASKS THAT APP CREATED; reaching the user's other tasks needs `manage_all_tasks`, which Manus labels broad access. An API key sees everything on the account via GET /v2/task.list

Page through a task's event stream: user and assistant messages, errors and status updates, plus tool_used, plan_update, new_plan_step and explanation events when `verbose=true`. `start_event_id` resumes from one event and cannot be combined with a cursor; `slides_format=pptx` converts HTML slide attachments to PowerPoint via GET /v2/task.listMessages

Read the credits still available to this account. Manus meters agent work in credits, so this is the call that says whether task.create and task.sendMessage can succeed via GET /v2/usage.availableCredits

Page through this user's own credit-usage records via GET /v2/usage.list

Page through the team's per-member usage log over a date window given as Unix timestamps in seconds, sorted by task count or by credits via GET /v2/usage.teamLog

Read the team's aggregate task count and credit spend over a date window given as Unix timestamps in seconds via GET /v2/usage.teamStatistic

Resolve the Manus user this connection acts as -- the user_id behind the API key or the OAuth access token. Read-only, takes no arguments, and Manus states it needs no additional OAuth scope, which is why it is also the credential check on the paste form via GET /v2/user.me

List the webhook endpoints registered on this account, with the ids webhook.delete takes via GET /v2/webhook.list

Read the public key Manus signs webhook deliveries with, so a receiver can verify that a notification really came from Manus via GET /v2/webhook.publicKey

List a website's checkpoints -- the deployable snapshots a task produced -- addressed by `task_id` OR `website_id`, exactly one via GET /v2/website.listCheckpoints

Read the deployment status of the website a task publishes, addressed by `task_id` OR `website_id` -- exactly one, never both via GET /v2/website.status

Change an agent's display name or the description shown with it. Neither field is reverted by omitting it -- send only what should change via POST /v2/agent.update

DESTRUCTIVE AND PERMANENT. Delete an uploaded file. Manus publishes no trash and no restore endpoint for files, so there is no undo and no safer alternative to prefer -- a task that already read the file keeps its own conversation, but the file is gone via POST /v2/file.delete

Register a filename and receive the upload target plus the `file_id` a task message attaches. AGENTIC FABRIQ DOES NOT SEND THE BYTES FOR YOU: a task can instead take a file by public `file_url` or as base64 `file_data` in the message itself via POST /v2/file.upload

Create a project and optionally its default instruction, which Manus prepends to every task created inside it -- the way to enforce one behaviour across related tasks via POST /v2/project.create

Answer a task that paused for confirmation, naming the `waiting_for_event_id` from the status_update event that asked and any input its `confirm_input_schema` describes. THIS AUTHORISES THE ACTION THE AGENT WAS WAITING ON and it proceeds immediately, so read the pending event before calling this via POST /v2/task.confirmAction

Start a Manus agent task from a message (text, an uploaded file_id, a public file_url, base64 file_data, or voice), optionally inside a project whose instruction is prepended, with an agent profile (standard, lite or max), a locale, a share visibility and a structured-output JSON Schema. TASKS SPEND CREDITS -- read usage.availableCredits first. `hide_in_task_list` keeps a background task out of the Manus webapp list while leaving it reachable at its task_url via POST /v2/task.create

DESTRUCTIVE AND PERMANENT. Delete a task with its message history and attachments. Manus publishes no trash and no restore endpoint, so there is no undo; stopping the task is the reversible alternative when the intent is only to end its run. Agent-related tasks cannot be deleted at all and answer an error via POST /v2/task.delete

Continue a task with another message (text, file or voice), optionally overriding the agent profile for this and later turns, replacing its connectors with a new list, clearing them entirely, or arming a structured-output schema for the next time it finishes. Omitting both connector fields reuses whatever task.create configured via POST /v2/task.sendMessage

Stop a running task. The task, its messages and its attachments all survive -- only the agent's execution ends -- so this is the reversible alternative to deleting a task that is merely going the wrong way via POST /v2/task.stop

Rename a task, show or hide it in the Manus webapp task list, or change who may view it. `share_visibility: public` MAKES THE SHARE URL READABLE WITHOUT AUTHENTICATION by anyone who holds it; `team` limits it to the team and `private` to the creator via POST /v2/task.update

Register an HTTPS endpoint to receive Manus task notifications by POST. It must be publicly reachable and answer 2xx; verify each delivery against the key from webhook.publicKey before trusting it via POST /v2/webhook.create

DESTRUCTIVE AND PERMANENT. Remove a webhook endpoint, which stops every future delivery to it. There is no undo and no disable: re-registering the same URL creates a NEW webhook with a new id via POST /v2/webhook.delete

Publish a task's website at a visibility: `public` (anyone), `team` (team members only, which requires a Team account) or `private`. OMITTING `visibility` RESETS THE SITE TO PUBLIC rather than leaving it unchanged, and a site may cap the visibility it allows and answer 403 above that cap. Addressed by `task_id` OR `website_id`, exactly one via POST /v2/website.publish

Change a website's title, its visibility or whether new checkpoints auto-publish. Omitted fields are left unchanged and an empty string is invalid, which is the difference from website.publish. Changing `auto_publish` neither publishes existing checkpoints nor cancels a deployment already in flight via POST /v2/website.update