AgentWeb exposes its capabilities three ways:Documentation Index
Fetch the complete documentation index at: https://docs.agentweb.pro/llms.txt
Use this file to discover all available pages before exploring further.
| Surface | Best for |
|---|---|
| MCP server | AI agents (Claude, Cursor, custom clients). The recommended path for most use cases. |
| REST API | Direct programmatic access from your own code. Same toolkit, no MCP client needed. |
| Webhooks | Receive callbacks from AgentWeb when events happen (lead replies, meeting summaries, etc.). |
Base URL
MCP server (recommended)
REST API
Authentication
All endpoints require authentication. Three paths:| Path | When to use |
|---|---|
| Bearer token (API key) | Server-to-server REST calls, MCP from Claude Code / OpenClaw |
| OAuth 2.0 | MCP from Claude.ai (the connector handles the flow) |
| Session cookie | The portal frontend (not for external use) |
aw_. Generate them in the portal under Settings → API Keys.
See Authentication for the full flow.
What’s not documented
Internal endpoints used by the portal frontend (auth, user management, scheduling internals) and admin-only endpoints are intentionally not exposed in this reference. They aren’t part of AgentWeb’s public contract and can change without notice. If you need a capability that isn’t here, email support@agentweb.pro.Next steps
- Authentication — generate an API key.
- Emma tools — the REST endpoint reference.
- Webhooks — incoming callbacks.
- Connect Emma — use Emma in Claude.ai, Claude Code, or OpenClaw.