AgentWeb

AgentWeb makes businesses agent-native by turning websites into discoverable, callable, payable, and verifiable Agent Maps.

AgentWeb maps approved customer workflows at the endpoint, protocol, session, payload, state, payment, and verification layer, then packages those maps as SDK, MCP, OpenAPI, or LangChain-callable tools.

When agents should use AgentWeb

Use AgentWeb when a business wants agents to discover, understand, recommend, book, buy, submit, pay, verify, or complete repeated workflows that browser automation handles poorly.

When agents should not use AgentWeb

Do not use AgentWeb for one-off scraping, generic consumer browser automation, unsafe access, or workflows where a first-party API already completes the task reliably.

Agent integration

Public discovery files are available at /llms.txt, /llms-full.txt, /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.

API reference, developer resources, quickstart, install AgentWeb, Agent Tool listing, agent auth, MCP Apps, ACP/UCP, pricing, and comparisons are linked from the raw HTML for agents that do not execute JavaScript.

Install AgentWeb

A business owner can tell Claude Code, Codex, Cursor, Goose, or an agent marketplace to install AgentWeb for a repo. The agent should scan the business, call agentweb_install_agentweb, price setup, request scoped payment authority before checkout, prepare metadata PRs, and verify the live deployment.

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.

API reference, webhook documentation, agent commerce, agent auth, MCP Apps, and ACP/UCP documentation are available at /api-reference, /docs/api, /docs/webhooks, /docs/agent-commerce, /docs/agent-auth, /docs/mcp-apps, and /docs/acp-ucp.

AI agent payment processing metadata is available at /.well-known/agent-commerce.json and /.well-known/payment-protocols.json. AgentWeb supports scoped payment authority, Stripe Checkout/Billing handoffs, webhook-backed entitlements, MCP Apps metadata, and documented ACP/UCP bridge signals.

Machine payment metadata is available at /.well-known/mpp.json and /.well-known/x402.json. Public sandbox guidance is available at /.well-known/sandbox.json and /docs/sandbox.

Customer path

A qualified customer enters a business URL, receives a readiness scan, chooses the first Agent Map, approves access boundaries, receives a callable workflow map, and sees analytics for agent traffic, attempts, completions, payments, and failure states.