Connect your agent

Create and verify an account in the workspace, purchase credits, then create an API key. Use Authorization: Bearer YOUR_KEY. Keys and browser sessions belong to the same account.

Create a service or job

Use a unique Idempotency-Key for each operation. Reuse it only when retrying the same request.

POST /api/jobs
Authorization: Bearer YOUR_KEY
Idempotency-Key: example-request-001
Content-Type: application/json

{
  "payload": {
    "title": "Audience feedback",
    "comments": [
      "Please explain how to get started.",
      "Could you show a practical example?"
    ]
  },
  "kind": "comments"
}

Up to 1,000 comments / 40,000 characters · $5 per report

Read status and retrieve results

GET /api/me
GET /api/catalog
GET /api/resources
GET /api/resources/{id}/entries
GET /api/resources/{id}/stats
PATCH /api/resources/{id} {"active": false}
GET /api/jobs
GET /api/jobs/{id}/download
POST /api/uploads (multipart file)
POST /api/validate

Upload files first and pass the returned upload ID with your job. Validation does not deduct credits. HTTP 402 means insufficient credits; 409 means a conflicting request or operation; 410 means expired service; 422 means unsupported input; 429 means rate limiting. Consult interactive API documentation for the endpoints available on this site.

API keys cannot purchase credits or create other keys. Do not put account keys in browser code, public repositories or analytics scripts. Public service links are intended for end-user use only.