API reference
The reviewed Gnaww developer contract contains 13 operations.
| Method | Path | Operation ID | Authentication |
|---|---|---|---|
GET | /health/live | getApiLiveness | Public |
GET | /health/ready | getApiReadiness | Public |
POST | /v1/interpret | interpretPrintRequirement | transform:write |
POST | /v1/interpret/continue | continuePrintRequirementInterpretation | transform:write |
POST | /v1/transform | transformPrintRequirement | transform:write |
POST | /v1/matches | matchPrintDemand | match:write |
POST | /v1/matches/universe | matchPrintDemandUniverse | match:write |
POST | /v1/recipes | resolveRecipe | recipes:write |
GET | /v1/recipes/{recipe_id} | getRecipe | recipes:read |
POST | /v1/recipes/{recipe_id}/matches | matchRecipe | recipes:read + match:write |
POST | /v1/specifications | createSpecification | specifications:write |
GET | /v1/specifications/{specification_id} | getSpecification | specifications:read |
GET | /v1/producer-capabilities/{profile_id} | getProducerCapabilityProfile | producer-capabilities:read |
This list is generated and governed from the reviewed gnaww-developer-v0.1 contract, not from the complete implementation OpenAPI document.
POST /v1/interpret returns gnaww.interpretation_result v0.2. The result is job-centric: top-level intent and shared context sit alongside jobs[] and scoped questions[]; canonical GJS, Recipe and SpecMatch readiness sit on the relevant Job. /v1/interpret/continue uses the corresponding v0.2 public continuation contract with answers keyed by question_id.
The base interpretation operation continues to require transform:write. When functional or unfamiliar intent reaches controlled Production Solution Candidate evaluation, the caller must also hold match:write and pass the active matching plan gate before Gnaww can run candidate-level SpecMatch against authorised controlled capability. A transform-only or non-entitled caller keeps the functional requirement in review rather than receiving a fabricated capability answer. When candidate SpecMatch actually runs, result-level truth.specmatch_performed is true; the Job-level specmatch field still describes readiness of canonical Job demand and may remain basis: none. Candidate capability fit is not price, current availability, current capacity or producer acceptance, and a viable candidate still requires explicit production-solution acceptance before canonical completion.
This reference is governed by the reviewed gnaww-developer-v0.1 contract. Only operations included in that contract form part of the Gnaww Developer API. Request and response schemas are generated from the same canonical OpenAPI definition.