Tools
Start withlist_businesses. Every tool that acts on one business takes a
required business argument: the business’s handle or id.
These tools are specific to connected clients:
The rest of the catalog is the tool set your businesses’ agents use (email,
products and payments, documents, tasks, files, site and domain, analytics,
ads, prospects, web research, images, database and repository access), each
with the
business argument added. tools/list is the source of truth: it is
sorted by name and cached for one hour (ttlMs, cacheScope: private), or
five minutes for an account that does not see every tool yet.
These tools only return a link and change nothing: cancel_platform_subscription,
change_auto_topup, request_withdrawal, archive_business, delete_account,
rotate_api_key, rotate_app_signin_secret, rotate_user_auth_secret and
connections_request (the link opens the business’s Connections tab).
Their result is:
cancel_subscription is a different tool: it cancels a subscription that one
of the business’s customers bought.
Founding a business
create_business returns at once with business, welcome_credits_granted
and first_pass. first_pass.status is one of:
started: poll itsturn_idwithget_turn.provisioning: the business is still being set up (about a minute). Pollget_businessuntilreadyistrue, then callstart_first_pass.skipped: the business already has its founding plan; there is nothing to start.not_started: the business exists but its first turn could not start.detailsays why, anderrornames the refusal when there is one. Withconflict, a turn is already running: poll theturn_idit carries. Otherwise fix the cause (for exampleinsufficient_credits), then callstart_first_pass.
create_business again for the same idea: a retry of the same idea
by the same client within ten minutes returns the business already created
instead of a second one.
Turns
send_message returns turn_id, session_id and business_id at once. Poll
get_turn every few seconds. Its status is one of queued, running,
waiting, completed, failed or interrupted. A waiting turn carries
the agent’s question: relay it to the user and answer with send_message on
the same business. A business runs one turn at a time; a message sent while
one runs is refused with conflict.
Clients on revision 2026-07-28 that declare the
io.modelcontextprotocol/tasks extension get a task from send_message
instead: the task id is the turn id, and pollIntervalMs
is 5 seconds. tasks/get reports it as working, completed or
cancelled: a failed turn is completed with an error result, and an
interrupted one is cancelled. tasks/cancel stops the turn. tasks/update
is not supported: send a new message instead.