Skip to main content
A starting block for an Anthropic agent — the Claude API’s tool runner, the Agent SDK, or any framework that takes a system prompt — whose tools are web-router’s MCP server. Every tool name in it is an MCP tool name. Paste it, then cut what your agent does not need: an agent without the browser_* tools should not carry their rules. Claude Code users can install the same guidance as a skill: see skills/web-router/SKILL.md. The prompt encodes the package’s own contract — cheapest method first, billed runs are deliberate, results are checked, sessions are closed, refusals are information — so the model’s behavior matches what the library already enforces instead of fighting it. Binding the Python library directly instead? Its tool names differ, and routing_guide() in web_router.integrations.anthropic (or WebRouterTools.guide()) writes the guide for the tools you expose. The methods map like this:

Tuning it

Budget caps belong in code, not the prompt. The prompt asks the model to be deliberate; the enforcement is research(timeout=...), browse(timeout=...), the MCP server’s ceiling (WEB_ROUTER_MCP_MAX_COST_USD, WEB_ROUTER_MCP_TIME_LIMIT_S), its session lifetime and idle timeout, and the keys you do or do not configure. An agent that should never spend money simply gets an install with no research or browse keys — the tools then say so themselves. Tell the model what this install holds. The tool enums already list only configured backends; if your framework lets you, put the web-router://capabilities resource in context at startup so the model plans with what it has rather than discovering it by refusal. Latency expectations prevent duplicate runs. The single most expensive failure mode is a model impatient with a job-shaped call. Keep the “poll, never resubmit” line even in a heavily trimmed prompt.

As an agent skill

The same contract ships as an agent skill, skills/web-router/SKILL.md, for a client that loads skills instead of a pasted prompt. Copy the skills/web-router folder into your client’s skills directory (for Claude Code, ~/.claude/skills/ or a project’s .claude/skills/).