Mission Control · API bay · §4.6

Output Schema Designer

Describe the output you want and Haiku will return a tight JSON Schema (draft 2020-12) with short field names, enums, and additionalProperties: false — ready to paste into your Anthropic SDK call.

Commander tier required

Locked on the recon tier.

Output Schema Designer is part of the API bay. Commander unlocks all 6 API-bay tiles + all 8 Code-bay tiles, $25 AI budget, public REST API, and CLI plugin for $24/mo.

See tiers

Why a tight schema matters

Short field names save output tokens. "id" vs "identifier" is 1 vs 4 tokens per field per call. At 100k calls/mo with 8 fields, that's ~2.4M tokens of pure waste.

Enums force compliance. "sentiment" as a free string can be "very positive", "mostly positive", "kinda happy" — all variations of the same idea. Enum forces one of {positive|neutral|negative} — cheaper, parseable, no fuzzy matching needed downstream.

additionalProperties: false prevents bloat. Without it the model can invent extra fields that nobody asked for. With it, you get exactly the shape you defined — no surprises in production.

Descriptions are free hints. JSON Schema description fields are sent as inline guidance to the model. Doesn't cost extra output tokens — improves compliance.