REST API

Standard conventions

• Requests and responses use JSON unless uploading files.
• Errors return a JSON object with an error field.
• Mutations require authentication.
• List endpoints may support pagination or filters.
• Long-running work usually creates an Inngest event and returns a run id or task id.

Example: run an agent

POST /api/agents/seo.content.pipeline/run
Content-Type: application/json

{
  "workspace_id": "workspace_uuid",
  "input": {
    "brief": "Create a content plan for the product launch"
  }
}

Check the agent run or reports endpoints for status and output.