feature_not_enabled

What it means

The endpoint exists and the key is valid, but the project's plan or settings do not allow the operation — write access to /v1 needs a Pro plan AND the project's “Allow AI write operations” toggle.

Common causes

• A write request (POST/PUT) from a project on the Free plan — Free is read-only.
• The “Allow AI write operations” toggle is off under Settings → API Keys.

How to fix it

Upgrade the project to Pro and/or enable “Allow AI write operations” in Settings → API Keys. Read endpoints keep working either way.

Should you retry?

No — not until the plan or toggle changes.

The response shape

Every /v1 error is an RFC 9457 application/problem+json document: type links to this page, code is the stable value to branch on (never parse title or detail), and request_id identifies the request to support. Validation failures add an errors array of per-field JSON pointers.

API overview · API reference · All error codes:

• missing_credentials — HTTP 401, Missing credentials
• invalid_api_key — HTTP 401, Invalid API key
• invalid_token — HTTP 401, Invalid access token
• unsupported_credential_type — HTTP 403, Credential type not usable on this surface
• insufficient_scope — HTTP 403, Insufficient scope
• validation_failed — HTTP 400, Request validation failed
• resource_not_found — HTTP 404, Resource not found
• rate_limited — HTTP 429, Rate limit exceeded
• quota_exhausted — HTTP 429, Plan quota exhausted
• idempotency_key_reused — HTTP 422, Idempotency-Key reused with a different request
• idempotency_in_progress — HTTP 409, A request with this Idempotency-Key is still in progress
• internal_error — HTTP 500, Internal server error