API Reference

Authentication

Pass your API key in the Authorization header as a Bearer token. Generate your key in the GWC dashboard under Settings → API Keys.

curl https://api.gwc-corp.com/api/tasks \
  -H "Authorization: Bearer YOUR_API_KEY"

Example: create a task

curl -X POST https://api.gwc-corp.com/api/tasks \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Generate report",
    "agent": "my-agent",
    "input": "Analyze Q2 sales data"
  }'

More Examples

List tasks with filters

Use query parameters to filter and paginate your task list. Pass offset to fetch subsequent pages.

curl "https://api.gwc-corp.com/api/tasks?status=RUNNING&limit=10" \
  -H "Authorization: Bearer YOUR_API_KEY"

Get a single task

Fetch a specific task by its ID to check status or retrieve results.

curl https://api.gwc-corp.com/api/tasks/clx1y2z3a0000qzrm5f8h2j9k \
  -H "Authorization: Bearer YOUR_API_KEY"

Update a task

Patch a task to update its status, output, or other fields.

curl -X PATCH https://api.gwc-corp.com/api/tasks/clx1y2z3a0000qzrm5f8h2j9k \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "status": "COMPLETED",
    "output": "Q2 sales up 12% year-over-year"
  }'

Check credit balance

Query your current credit balance and usage.

curl https://api.gwc-corp.com/api/credits/balance \
  -H "Authorization: Bearer YOUR_API_KEY"

Create a subscription

Subscribe to a paid tier. Add "seats" for corporate (no minimum) or enterprise (min 100 seats). Returns a Stripe Checkout URL — redirect the user to complete payment.

curl -X POST https://api.gwc-corp.com/api/subscriptions/subscribe \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "plan": "standard"
  }'

Tasks

Agents

MCP Servers

Credits & Billing

Auth

Request & Response Schemas

Error Codes

The API uses standard HTTP status codes. Error responses are wrapped in an envelope: { error: { message, code?, details?, timestamp, path } }. The code field is optional — many errors (e.g. most 401s) carry no code, so key off the HTTP status first and treat error.code as a hint.

Example error response:

{
  "error": {
    "message": "Task not found",
    "code": "NOT_FOUND",
    "timestamp": "2026-07-05T12:00:00.000Z",
    "path": "/api/tasks/clx1y2z3a0000qzrm5f8h2j9k"
  }
}

For 429 responses, retry timing comes from the Retry-After and RateLimit-Reset headers, not the response body.

Rate Limiting

Rate limits are applied per user account, not per API key — every key you mint draws on the same bucket, so adding keys does not add headroom. Unauthenticated requests are keyed by client IP instead. Limits vary by subscription tier.

Each tier has a single enforced ceiling: the number of requests allowed in a rolling 60-second window. There is no separate “burst” allowance on top of it — the ceiling below is the tier’s base rate plus its burst, which is what the server enforces and what RateLimit-Limit reports.

Chat, agents, and media-generation endpoints are metered on the separate, lower AI ceiling in the right-hand column — also per user account. A request against one of those endpoints counts toward both ceilings.

Rate limit headers

Every response includes these headers so you can track your usage:

When you hit the limit

The API returns 429 Too Many Requests with a Retry-After header indicating how many seconds to wait. We recommend exponential backoff with jitter.

Pagination

Pagination is per-endpoint — there are no cursors.

GET /api/tasks

GET /api/agents

Example: paginate tasks with offset

# First page
curl "https://api.gwc-corp.com/api/tasks?limit=50" \
  -H "Authorization: Bearer YOUR_API_KEY"

# Response: { "tasks": [ ... ], "total": 142 }

# Next page
curl "https://api.gwc-corp.com/api/tasks?limit=50&offset=50" \
  -H "Authorization: Bearer YOUR_API_KEY"