the provider catalog
OpenAI
The most widely known API. Structured outputs make schema: a real contract. The answer arrives as data the next task can trust. One provider/model line moves a workflow here or away again: the same file runs on every provider the catalog names, and swapping is a one-word diff. Machines read the catalog; the binary answers nika catalog.
- 2pinned modelsaliases pin exact upstream ids
- cloudfamilybring your own key; it rides an env var and stays yours
- OPENAI_API_KEYthe key rides herean env var, never a config file
- openai-chatwire dialectthe adapter speaks it
the wire
cloud · bring your own key; it rides an env var and stays yoursA workflow names this provider in the model line (model: openai/gpt-5.2), and the engine speaks openai-chat on the wire. The key rides OPENAI_API_KEY in the environment, never a config file, never the workflow. The provider id also answers to gpt.
- default
gpt-5.2- cheap
gpt-5-mini- dialect
openai-chat- tags
- code-execution · frontier · function-calling · image-gen · prompt-caching · realtime · streaming · vision
the models
2 pinsAliases are what the file may write; the engine pins each one to an exact upstream id, so a run stays reproducible after a vendor rotates names.
gpt-5.2gpt-5.2ctx 272k · reasoning · vision · json:schemagpt-5-minigpt-5-minictx 272k · reasoning · vision · json:schema$0.25/M in · $2/M out
prices are the ENGINE's, not ours: the audit's pricing snapshot (models.dev · pinned 2026-07-07): the same table nika check prices your ceiling with.
in the released catalog
2 roomsThe wire models this provider serves in the released binary's catalog · each one is a room with its seats, exact prices and measured energy.
- gpt-5-minias gpt-5-mini
- gpt-5.2as gpt-5.2
the whole register: /catalog/models · what the released binary knows, vendored at the engine pin.
in a real file
a complete workflow · shown wholenika: v1workflow: id: typed-extraction description: "the answer arrives as data, not prose — schema makes the shape a contract"tasks: extract: infer: model: openai/gpt-5-mini max_tokens: 200 schema: type: object required: [severity, component] properties: severity: { type: string, enum: [low, medium, high] } component: { type: string } prompt: | "Login fails with a 500 after the session-store deploy." Extract severity and component.outputs: ticket: ${{ tasks.extract.output }}check-green against the released engine · 1 task · 1 wave · worst-case ceiling $0.0004 · the drift gate re-proves this copy on every test run · open it in the playground →
get set up
keys at platform.openai.com- 1Create a key in the platform console.
- 2The key rides the environment, never the file
export OPENAI_API_KEY=…
Pick it for when downstream tasks consume the answer as data, not prose. Then prove the seat: nika doctor names every provider this binary can reach.
swap it
10 more cloud seatsMoving off OpenAI is editing one line. The rest of the file (tasks, permits, outputs, the trace) does not change. The register orders the catalog local first; beyond it the engine embeds 21 more OpenAI-compatible endpoints.
cross-references
the words that meet it
Try it in the playground, or install and go local first. Read the spec →