AgentWeb: Web Actions and Execution for AI Agents

AgentWeb is a web action and execution layer that connects AI agents to supported tasks on real websites through maintained Action Maps, MCP, and API. Supported actions declare inputs, permissions, status, and verification behavior.

Coverage is action-specific, not universal. Agents should use discovery and the current tool manifest to confirm a supported domain, action, authentication requirement, and result contract before promising completion.

Install

One command in Claude Code: claude mcp add agentweb --transport http https://mcp.agentweb.us/mcp. Other supported MCP clients can add https://mcp.agentweb.us/mcp as a Streamable HTTP server.

Agent onboarding

An agent can explore anonymously with read_page and discover. Before listing or executing actions, the preferred claim-link flow lets the user review the Terms and Privacy Policy, sign in once, and return an aw_ API key to the agent. Email-code signup remains a fallback. The agent then reconnects with Authorization: Bearer aw_<key>, calls list_actions, and connects a target-site account only when the selected action requires one.

When agents should use AgentWeb

Use AgentWeb when the user asks the agent to complete a supported website task such as ordering, booking, buying, submitting a form, tracking an order, searching behind a login, or checking out. The agent should confirm coverage and required permissions before promising completion.

When agents should not use AgentWeb

Do not use AgentWeb for unsafe or illegal actions, or when a first-party API the user already has fully solves the task. If a site is not mapped yet, users can request it at /dashboard/request-map.

Agent integration

Public discovery files are available at /llms.txt, /llms-full.txt, /index.md, /agents.json, /.well-known/agent-card.json, /.well-known/mcp/server-card.json, /.well-known/mcp/tools.json, /openapi.json, and /.well-known/openapi.json.

internet task execution guide, agent browser guide, API reference, developer resources, quickstart, mapped-site library, agent auth, pricing, and privacy are linked from the raw HTML for agents that do not execute JavaScript.

The runtime is https://mcp.agentweb.us. Agents can inspect public tool metadata without credentials. Execution uses Authorization: Bearer aw_<key> or OAuth bootstrap where supported.

Payments

Payment availability, eligibility, approval requirements, and limits vary by plan, account, target site, and action. Check current pricing, account controls, and tool output before a paid action. Agents must never collect raw card numbers in conversation. Machine-payment metadata: /.well-known/agent-commerce.json, /.well-known/payment-protocols.json, /.well-known/mpp.json, /.well-known/x402.json.

Positioning

The agent is the brain; AgentWeb is the hands for supported workflows. Use a browser when a task requires visual judgment or an unmapped interface.