ToolRouter

List connected accounts and MCP servers (summary) or detail on one connector. Pass slug for detail including every tool the connector exposes. Optional type: "oauth" | "mcp" filter. Pass include_available: true to also see available catalog MCPs you can connect.

View or set permissions for tools on a connected MCP server — which tools are allowed, rate limits, budget caps, argument restrictions. Pass the connector slug (from connector_list) and action: "list" to see current rules, or action: "set" with tool_name + rules to update one. Team scope requires admin role.

Disconnect a connector. Pass slug.

Set the default value for a multi-value credential.

Remove a saved credential. If label is provided, removes only that specific entry. If no label, removes ALL entries for that credential name.

Get setup instructions for a specific credential.

List saved credentials (summary) or detail on one. Pass name for detail view. Pass show_available: true to include the full credential catalog.

Save a credential (BYOK provider API key). Saved keys persist across sessions and are used automatically.

Current balance, plan tier, rate limits, and any negative-balance warnings for the active context.

Usage summary or history. Pass scope: "me" | "team" and detail: "tool" | "skill". Sorted by cost with _others rollup.

Find the right ToolRouter tool for your task. Describe what you need in plain language. Examples: "analyze a website", "research competitors", "find prospect companies", "check DNS records". Exact tool name (e.g. "seo") returns full schemas and examples. Flow: prefer route({ intent }) to pick and run a tool. Use discover when you need schemas or a listing, then call use_tool(tool, skill, input). Every discover response also includes a top-level `connectors` array listing SaaS accounts the user has already connected (LinkedIn, Google, Notion, etc.). Use that to pick the right tool and account w…

Report a ToolRouter platform bug that blocks you from completing the user's task. Use this when you suspect the issue is on our side — a tool crashed, returned malformed data, timed out unexpectedly, or behaved inconsistently. Include the relevant ToolRouter errors, call IDs, non-sensitive input shape, retries, and expected behavior. Do not include chat history, unrelated conversation text, uploaded file contents, personal data, API keys, or secrets. Reports are stored and reviewed within hours. Skip this for expected errors like invalid input, missing credentials, insufficient balance, rate l…

Ask ToolRouter to build a tool that does not exist yet. Use this when discover returned nothing useful for what the user needs. Describe the capability in plain terms — do not include personal data, API keys, or secrets. Requests go straight to the team. Limit: 5 per hour.

Submit a review or star rating.

Delete a file. Cannot be undone. For team files: requires owner/admin role.

List or search files. Optional query triggers semantic search. Supports section, tags, plan_status, limit, cursor filters.

Read a file's full content. Text files return content inline. Binary files (images, video) return a download URL.

Create or update a file. Pass mode: "create" | "update". Binary uploads: call with binary: true to get an upload_url, then PUT bytes, then call with mode: "finalize".

List invoices for the active billing context.

Cancel a running job.

Get job status and result. Returns status: running | completed | failed and result when terminal. Keep polling until you get a terminal status.

List your active and recent jobs. Optional status filter.

Create a new API key. Returns the secret once — save it immediately.

Revoke an API key. Refuses to revoke the currently-authenticating key.

List API keys (summary) or get detail on one key. Pass key_id for detail view.

List your outfits.

List your personas.

List your products.

Send a natural-language intent and optionally any dimensions you already know (tool, skill, model, input fields). Fills only the blanks via Jev, then either executes the call or returns a ready-to-run use_tool payload. Explicit values are never overridden. Returns candidates when confidence is low or no tool fits. Flow: route → if confident and complete, result is returned; otherwise use the pre-filled call with use_tool.

List your scenes.

Get a Stripe management URL (portal, upgrade, or cancel). Also covers billing portal — returns the URL for the user to open.

Add credits to your account. Returns a Stripe checkout URL — share it with the user to complete payment. Minimum $1.

Call a ToolRouter catalogue tool. Prefer `route` with a natural-language intent when you do not already know the tool and skill — it picks them, fills arguments, and runs the call. Use discover when you need schemas or a catalogue listing, then pass the exact tool name and skill here. IMPORTANT: "discover", "route", "credits_balance", and other built-in tools are NOT catalogue tools — call them directly, never through use_tool. Long-running tools return a job_id — poll with job_get. If a skill needs an image_url or file URL and you have a local file or base64 image, use file_write first to get…