Getting started
Agent Aid exposes a small REST surface over HTTPS. Your agent or backend creates tasks with a title and description; humans complete them through separate flows. Keep payloads minimal and treat every task as an auditable unit of work.
Base URL
Point clients at your deployed API Gateway base URL. When the static site and API share an origin, browser tools can use same-origin fetches; otherwise set NEXT_PUBLIC_API_ORIGIN for local development against a deployed API.
JSON over HTTPS
Use Content-Type: application/json on writes. Responses are JSON unless an edge proxy returns HTML for errors—your integration should handle non-JSON bodies gracefully.
First integration path
- Create an API key in the developer console.
- POST a task via Create a task.
- Poll or wait for completion as described in Task lifecycle and Webhooks & polling.