Bazhuayu MCP integration for AI agents.
Connect AI agents to Bazhuayu through 18 structured actions, including get task actions, start subtasks, and copy task. Review authentication, inputs, workfl…
- ACTION CONTRACTS
- 18
- AUTHENTICATION
- Custom credentials
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Bazhuayu integration exposes
The Bazhuayu Agent App exposes 18 provider-backed actions for data and developer tools work. Its current contract lets an authorized agent get api-addressable steps from bazhuayu tasks so their action ids can be used in parameter updates. requires a flagship+, enterprise, or team plan, start selected cloud subtasks for a bazhuayu task. requires a flagship+, enterprise, or team plan, and copy a bazhuayu task into a task group and return the new task id. requires a flagship+, enterprise, or team plan. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses Custom credentials. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Bazhuayu account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Bazhuayu capabilities.
Showing 12 of 18 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_task_actionsREADGet API-addressable steps from Bazhuayu tasks so their action IDs can be used in parameter updates. Requires a Flagship+, Enterprise, or Team plan.
INPUTS: taskIds / actionTypes
start_subtasksWRITEStart selected cloud subtasks for a Bazhuayu task. Requires a Flagship+, Enterprise, or Team plan.
INPUTS: taskId / subTaskIds
copy_taskREVIEWCopy a Bazhuayu task into a task group and return the new task ID. Requires a Flagship+, Enterprise, or Team plan.
INPUTS: taskId / taskGroupId
get_task_batch_dataREADGet a page of collected data from one Bazhuayu task execution batch. Requires a Flagship, Flagship+, Enterprise, or Team plan.
INPUTS: taskId / lotNo / offset / size
get_task_dataREADGet a page of collected data from a Bazhuayu task using the offset returned by the previous page. Requires a Flagship, Flagship+, Enterprise, or Team plan.
INPUTS: taskId / offset / size
get_task_statsREADGet account-wide counts for waiting, extracting, and finished Bazhuayu cloud tasks and subtasks. Requires an Enterprise plan.
get_task_statusesREADGet the latest execution status for Bazhuayu tasks. Requires a Flagship+, Enterprise, or Team plan.
INPUTS: taskIds
get_unexported_dataREADGet the next unexported records from a Bazhuayu task. Use this with mark_data_exported through only one sequential consumer per task because Bazhuayu acknowledgements are task-scoped. Requires a Flagship, Flagship+, Enterprise, or Team plan.
INPUTS: taskId / size
list_subtask_statusesREADList the latest batch's Bazhuayu subtask statuses. Requires a Flagship+, Enterprise, or Team plan.
INPUTS: taskId / page / size
list_task_groupsREADList the task groups available to the connected Bazhuayu account. Requires a Flagship, Flagship+, Enterprise, or Team plan.
list_tasksREADList the Bazhuayu tasks in one task group. Requires a Flagship, Flagship+, Enterprise, or Team plan.
INPUTS: taskGroupId
mark_data_exportedREVIEWMark the current unexported data for a Bazhuayu task as exported. Call this only after a single sequential consumer has persisted the preceding get_unexported_data result. Requires a Flagship, Flagship+, Enterprise, or Team plan.
INPUTS: taskId
INPUT CONTRACTS
Know what the action needs before it runs.
get_task_actions
taskIdsOPTIONAL- The Bazhuayu task IDs.
actionTypesOPTIONAL- The task step types to return.
start_subtasks
taskIdOPTIONAL- The Bazhuayu task ID.
subTaskIdsOPTIONAL- The Bazhuayu subtask IDs.
copy_task
taskIdREQUIRED- The Bazhuayu task ID.
taskGroupIdOPTIONAL- The destination Bazhuayu task group ID. Omit it to copy into the source task's current group.
get_task_batch_data
taskIdOPTIONAL- The Bazhuayu task ID.
lotNoOPTIONAL- The Bazhuayu task execution batch number.
offsetOPTIONAL- The data offset. Values less than or equal to 0 read from the beginning.
sizeOPTIONAL- The number of records to return, from 1 to 1000.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Task Actions
Get API-addressable steps from Bazhuayu tasks so their action IDs can be used in parameter updates. Requires a Flagship+, Enterprise, or Team plan. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_task_actionsControl Start Subtasks
Start selected cloud subtasks for a Bazhuayu task. Requires a Flagship+, Enterprise, or Team plan. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
start_subtasksVerify with Get Task Batch Data
Get a page of collected data from one Bazhuayu task execution batch. Requires a Flagship, Flagship+, Enterprise, or Team plan. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_task_batch_dataSAFETY BOUNDARY
Operate Bazhuayu with explicit limits
- Authorize Bazhuayu with Custom credentials and grant only the provider access required by the selected actions.
- 4 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Bazhuayu rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Bazhuayu task completed successfully.
CONNECTION MODEL
Custom credentials
Bazhuayu uses Custom credentials. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 10
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 4
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Bazhuayu.