Skip to main content
AgentWeb exposes its capabilities three ways: All three use the same underlying capabilities — content generation, lead management, ad operations, performance data, and integrations.

Base URL

The MCP server speaks Model Context Protocol over Streamable HTTP. Connect it once and any MCP-compatible client (Claude.ai, Claude Code, OpenClaw, Cursor, custom MCP clients) gets the full Emma toolkit. See Connect Emma for client-specific setup.

REST API

REST endpoints mirror the MCP toolkit. Use these when you’re building against AgentWeb from a language or environment that doesn’t have an MCP client, or when you want fine-grained HTTP-level control. See Emma tools for the endpoint reference.

Authentication

All endpoints require authentication. Three paths: API keys start with 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