# AgentWeb

AgentWeb is the execution layer for agents on authenticated web workflows.

AgentWeb maps approved customer workflows at the endpoint, protocol, session,
payload, state, and verification layer. The output is a reusable action map
that a customer's AI product can call through MCP, REST, SDK, or LangChain.

## When To Use AgentWeb

Use AgentWeb when an AI product needs to complete repeated web workflows that
are too slow, brittle, authenticated, or hard to verify with browser automation.

Good fits include:

- supplier discovery
- lead enrichment
- authenticated search
- quote or RFQ submission
- workflow verification
- structured data extraction with proof
- repeated execution of mapped actions

## How Agents Discover AgentWeb

- Short instructions: https://agentweb.us/llms.txt
- Agent setup and audit UI: https://agentweb.us/agent
- Install AgentWeb guide: https://agentweb.us/docs/install-agentweb
- Agent Tool listing: https://agentweb.us/.well-known/agent-tool.json
- Full reference: https://agentweb.us/llms-full.txt
- Agent card: https://agentweb.us/.well-known/agent-card.json
- MCP server card: https://agentweb.us/.well-known/mcp/server-card.json
- MCP tools: https://agentweb.us/.well-known/mcp/tools.json
- OpenAPI: https://agentweb.us/openapi.json
- Readiness scanner: POST https://agentweb.us/api/readiness/scan
- Action map schema: https://agentweb.us/.well-known/action-map.schema.json
- Readiness scan schema: https://agentweb.us/.well-known/readiness-scan.schema.json
- Setup session schema: https://agentweb.us/.well-known/setup-session.schema.json
- Agent traffic event schema: https://agentweb.us/.well-known/agent-traffic-event.schema.json
- Agent traffic event ingestion: POST https://agentweb-telemetry.andreymarey20.workers.dev/telemetry/agent-event

## Install AgentWeb From a Coding Agent

A business owner can tell Claude Code, Codex, Cursor, Goose, or another coding
agent: "install AgentWeb for this repo" or "make this business usable by
agents." The agent should scan the business, generate an install plan, price the
setup, request scoped payment authority before checkout, prepare PRs for
agent-readable metadata, and verify the live deployment.

Primary install tools:

- agentweb_scan_business
- agentweb_install_agentweb
- agentweb_price_setup
- agentweb_create_checkout_session
- agentweb_verify_install

## Runtime

- MCP and REST origin: https://mcp.agentweb.us
- MCP endpoint: https://mcp.agentweb.us/mcp
- Read endpoint: https://mcp.agentweb.us/api/read
- Discover endpoint: https://mcp.agentweb.us/api/discover
- Agent-native registration: https://mcp.agentweb.us/api/register
- Agent-native verification: https://mcp.agentweb.us/api/verify

## Agent Traffic Attribution

Agents should include protocol, discovery surface, provider, and session ID
when calling AgentWeb. AgentWeb records attribution metadata, conversion state,
business domain, coarse country, and hashed IP only. It does not store raw
prompts, raw IP addresses, payment credentials, or private customer payloads in
the traffic stream.

## Access Model

AgentWeb is design-partner first with a production Stripe billing path for
approved setup and usage. Agents and humans can start at /agent to run a public
readiness audit and receive a scoped setup offer before any private data,
payment authority, or repository access is requested.

Paid agent-network checkout requires a scoped payment authority artifact with
principal, scope, amount limit, currency, expiry, revocation URL, receipt
requirement, and verification requirement. Runtime access is granted only by a
Stripe webhook that verifies the Stripe signature and applies the entitlement.

Request access: https://agentweb.us/request-access

Workflow mapping call: https://calendly.com/andreymarey-work/30min