Automate governed builds with JWTs and API keys

The current API version is v1. The base URL for all API requests is:

When a new API version is released, the previous version remains available for a deprecation period. Version sunset notices are published in the changelog and communicated via email.

{  "error": {    "code": "VALIDATION_ERROR",    "message": "The prompt_text field is required.",    "details": [      {        "field": "prompt_text",        "constraint": "required"      }    ]  }}

The code field contains a stable error identifier suitable for programmatic handling. The message field provides a human-readable explanation. The optional details array contains field-level validation errors when applicable.

Common error codes include:

• VALIDATION_ERROR — request body failed validation
• UNAUTHORIZED — missing or invalid authentication
• FORBIDDEN — authenticated but insufficient permissions
• NOT_FOUND — requested resource does not exist
• RATE_LIMITED — request rate exceeded the limit
• BUDGET_EXCEEDED — organization or project budget exhausted

Rate limit headers included on every response:

• X-RateLimit-Limit — maximum requests per window
• X-RateLimit-Remaining — requests remaining in the current window
• X-RateLimit-Reset — UTC epoch timestamp when the window resets

When the rate limit is exceeded, the API returns HTTP 429 with a Retry-After header indicating how many seconds to wait before retrying.