API Overview

Base URL

All API requests are made to:

https://api.gen.pro/v1

All paths in this reference are relative to the base URL. For example, GET /v1/me means GET https://api.gen.pro/v1/me.

Authentication

Every API request requires authentication via one of these headers:

Header	When to use
X-API-Key	Recommended for all integrations. A Personal Access Token (PAT) you create in the GEN dashboard.
Authorization: Bearer <jwt>	Only if your app already uses GEN’s browser login flow.

curl https://api.gen.pro/v1/me \
  -H "X-API-Key: your-api-key"

How to get an API key

1. Log in to gen.pro
2. Select an agent (or create one)
3. Go to the API page in the left sidebar (gen.pro/{agent_id}/api)
4. Click Create API Key, give it a name, and copy the token

That token is your X-API-Key. Store it securely — it won’t be shown again.

You can also create and manage API keys programmatically via the API Keys endpoints.

Tip

API keys are scoped to your user account. Any agent you have access to can be used with the same key by passing the agent_id parameter.

Agent scoping

All /autocontentengine/ endpoints require an agent_id query parameter. This scopes every request to a specific GEN agent. The authenticated user must have access to the agent, and the agent’s workspace must have active GEN credits.

curl "https://api.gen.pro/v1/autocontentengine?agent_id=42" \
  -H "X-API-Key: your-api-key"

Error format

Errors return a JSON object with error (human-readable message) and error_code (machine-readable identifier):

{
  "error": "Agent not found",
  "error_code": "not_found"
}

Common status codes

Code	Meaning
200	Success.
201	Resource created.
204	Success, no content (used for deletes).
401	Unauthorized. Missing or invalid API key / JWT.
404	Resource not found, or you don’t have access.
422	Validation error. Check the error field for details.

Rate limiting

Note

Rate limiting is not currently enforced. We reserve the right to add limits in the future. Build your integrations to handle 429 Too Many Requests responses gracefully.

Pagination

The API currently returns full result sets. There is no cursor or offset-based pagination yet. For large datasets, use filtering parameters where available.

Timestamps

Timestamp fields follow two conventions:

Field pattern	Format
created_at, updated_at	ISO 8601 string ("2026-03-01T12:00:00.000Z")
created_at_ts, updated_at_ts	Unix epoch in milliseconds (1709294400000)

Most resource responses include both forms. Use the _ts variants for numeric comparisons and sorting.

OpenAPI spec

A machine-readable OpenAPI specification is available at:

https://api.gen.pro/openapi.yaml

Use it to generate client libraries, import into Postman, or validate requests.