Skip to main content

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.

Emma’s REST endpoints live at: 
https://api.agentweb.pro/api/emma/*
All endpoints require an Authorization: Bearer aw_... header. See Authentication to generate a key. The MCP server at https://api.agentweb.pro/mcp exposes the same toolkit. If you’re building an AI agent integration, prefer MCP — the tool list and schemas are advertised automatically on connect. See Connect Emma.

​
Tool categories

Tools are grouped below by what they do.
EndpointPurpose
POST /api/emma/search-webWeb search with structured results.
POST /api/emma/deep-researchMulti-step research with citations.
POST /api/emma/search-knowledge-baseSearch your uploaded Knowledge Base files.
POST /api/emma/search-ads-knowledge-baseSearch saved ad creative references.
POST /api/emma/search-foreplay-discoverySearch the connected Foreplay swipe file.
POST /api/emma/read-knowledge-base-filesRead the full content of specific Knowledge Base files.
GET /api/emma/knowledge-basesList your Knowledge Base instances.

​
Knowledge management

EndpointPurpose
POST /api/emma/create-knowledge-baseCreate a new Knowledge Base.
POST /api/emma/update-knowledge-base-fileUpdate an existing file.
POST /api/emma/attach-knowledge-base-filesAttach files to a Knowledge Base.

​
Media generation

EndpointPurpose
POST /api/emma/generate-imageGenerate images from a text prompt.
POST /api/emma/generate-videoGenerate short-form video from a prompt.
POST /api/emma/describe-mediaDescribe an image or video.
POST /api/emma/remove-c2paStrip C2PA provenance metadata from generated media.

​
Communication

EndpointPurpose
POST /api/emma/emailSend email through a connected Gmail account.
POST /api/emma/social-postsCreate or schedule social posts across connected platforms.
POST /api/emma/linkedin-outreachSend LinkedIn connection requests or DMs at scale.
POST /api/emma/post-on-accountPost organically to a specific connected account.
POST /api/emma/linkedin-commentComment on a LinkedIn post.
POST /api/emma/linkedin-reactReact (like, celebrate, etc.) on a LinkedIn post.

​
Account analytics

EndpointPurpose
GET /api/emma/connected-account-postsList posts from a connected social account.
GET /api/emma/connected-account-metricsAggregate engagement metrics across posts.
POST /api/emma/post-analyticsPer-post analytics with breakdowns.
POST /api/emma/data-analysisRun analysis on a structured dataset (CSV, JSON).

​
Meta ads

EndpointPurpose
GET /api/emma/meta-ads/campaignsList Meta ad campaigns.
POST /api/emma/meta-ads/insightsPull campaign insights for a date range.
POST /api/emma/meta-ads/metricsPull granular ad-level metrics.
POST /api/emma/meta-ads/marketing-apiDirect passthrough to the Meta Marketing API (advanced).

​
Files & HTML

EndpointPurpose
POST /api/emma/read-fileRead a file from your workspace.
POST /api/emma/read-pageFetch and render a web page as text.
POST /api/emma/save-fileSave a file to your workspace.
POST /api/emma/create-htmlGenerate an HTML page from a prompt.
GET /api/emma/html-templatesList your HTML templates.
POST /api/emma/create-html-from-templateGenerate an HTML page from a template.
POST /api/emma/create-html-templateSave a reusable HTML template.
POST /api/emma/update-html-fileEdit an existing HTML file.

​
Books

EndpointPurpose
GET /api/emma/booksList Books projects.
GET /api/emma/books/:bookIdGet a book’s metadata.
GET /api/emma/books/:bookId/contentFetch a book’s full content.
POST /api/emma/booksCreate a new Books project.

​
Request and response format

All endpoints accept and return JSON. Request bodies are application/json. Successful responses use standard HTTP status codes (200, 201, 204). Errors return: 
{
  "error": "Human-readable description of what went wrong"
}
with the appropriate HTTP status (400, 401, 403, 404, 429, 500).

​
Discovering schemas

The full request and response schema for each endpoint is best discovered through the MCP server, which advertises tool definitions on connect. 
curl https://api.agentweb.pro/mcp \
  -H "Authorization: Bearer aw_YOUR_API_KEY_HERE" \
  -H "Accept: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
The response includes each tool’s name, description, and JSON Schema for inputs.

​
Rate limits

Per-key rate limits are configured when you generate the key. The default is your plan’s standard limit. Set a custom limit on key generation if you need to throttle a specific use case. When you hit the limit, the API returns 429 Too Many Requests with a Retry-After header indicating how long to wait.

​
Next steps