AgentWeb Developers

AgentWeb exposes mapped workflow execution through MCP, REST, SDK, and LangChain-compatible tools.

For crawler-friendly developer resource discovery, start at /developers/agent-resources.

Runtime

• MCP endpoint: https://mcp.agentweb.us/mcp
• OpenAPI: /openapi.json
• MCP tool manifest: /.well-known/mcp/tools.json
• MCP Apps manifest: /.well-known/mcp/apps.json
• Agent payment processing resources: /developers/agent-payment-processing
• Agent auth examples: /docs/agent-auth
• ACP/UCP support: /docs/acp-ucp
• Auth and limits: /docs/auth-and-limits.html
• Agent platform configs: /agent-platforms/

Auth

Use Authorization: Bearer aw_<key> for production keys. OAuth metadata and PKCE bootstrap are available on the MCP origin for compatible clients.

Agent-Native Registration

1. In MCP, call agentweb_start_api_key_signup with the user's email address.
2. Ask the human for the emailed code, then call agentweb_complete_api_key_signup with email, code, and device ID.
3. Raw HTTP clients can use POST https://mcp.agentweb.us/api/register and POST https://mcp.agentweb.us/api/verify for the same flow.
4. Use the returned MCP URL and API key in the customer's agent runtime.

Provider Connections

1. Call agentweb_auth_status or agentweb_connection_status before executing partner actions.
2. If Hermes or another cookie-backed provider is not connected, call agentweb_start_connection.
3. Send the human to the returned live_view_url, then call agentweb_poll_connection until it returns done.