9. 402 - addon required

The endpoint is gated by an addon the tenant has not enabled yet. Unlike most error bodies, a 402 carries extra typed fields: the addon's short code, its human name, the monthly_usd price, and a purchase_url the dashboard surfaces as a one-click enable.

Calling a paid endpoint (here, natural-language SQL via /ask) before the ask addon is enabled.

curl -X POST "https://$OC_HOST/v1/tenants/$OC_TENANT/ask" \
  -H "Authorization: Bearer $OC_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"question": "how many customers do I have?"}'

{
  "error": "addon_required",
  "message": "natural-language SQL requires the 'ask' addon",
  "retry": false,
  "addon": "ask",
  "name": "Natural language SQL",
  "monthly_usd": 99,
  "purchase_url": "https://originchain.ai/app/addons?enable=ask"
}

• Open the purchase_url from the response body - the dashboard turns it into a one-click enable, no support ticket required.
• Or enable programmatically: POST /v1/tenants/:t/addons with {"addon": "ask"}.
• If you're building a UI on top of OriginChain, surface the name and monthly_usd fields so the user sees what they're enabling.
• retry: false - the call needs the addon, not a retry. Once enabled, the same request will succeed.