---
title: "Create an authenticated feasibility interpretation"
method: POST
path: "/api/v1/feasibility/analyses/{analysisId}/interpretations"
tags: ["feasibility"]
---

# Create an authenticated feasibility interpretation

`POST /api/v1/feasibility/analyses/{analysisId}/interpretations`

## Request

- Base URL: `https://buckybuild.com`
- URL: `https://buckybuild.com/api/v1/feasibility/analyses/{analysisId}/interpretations`
- Auth: HTTP bearer

Creates an AI-backed interpretation for a completed deterministic feasibility analysis, grounded in the frozen analysis facts and persisted for the authenticated user. A Supabase bearer JWT is required for every request; missing or invalid auth returns `AUTH_REQUIRED`. The route accepts an `Idempotency-Key` header for safe retries, uses the authenticated-user `AI_GENERATE` route bucket behind the `PUBLIC_API` middleware backstop, and returns registered v1 error codes including `INVALID_REQUEST`, `AUTH_REQUIRED`, `RATE_LIMITED`, and `ANALYSIS_FAILED`.

## Response `200`

Successful response.

## Other responses

- `400`: Validation or client error.
- `401`: Authentication required.
- `403`: Insufficient permissions.
- `404`: No such resource, or no such route under this version prefix.
- `429`: Rate limit exceeded (`code: RATE_LIMIT_EXCEEDED`, `retryable: true`). Honour `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/buckybuild/apis/bucky-public-api.md) · [All operations](https://skmtc.dev/buckybuild/apis/bucky-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/buckybuild/apis/bucky-public-api/revisions/30e442927a24?raw)