API

Field contracts and worked examples for the api blocks — converted at build time from the repo's authoring-skill reference. Every example body is YAML; in a real doc the fence language is the block type (for example sequence … ). Schemas are strict — unknown fields are rejected. See the field contract for the at-a-glance shape of all 77 blocks, or the block catalog for live previews.

API reference

endpoint — a Swagger-style API endpoint card

{ "items": [{ "sku": "A1", "qty": 2 }] }

{ "id": "ord_123", "status": "pending" }

Only method and path are required. params[].in is path | query | header | cookie. For a whole spec, generate docs with avo sync openapi.

pullquote — a standout quote

layers — a layered explanation (N numbered layers)

Use layers (not a table) when content reads as ordered tiers each answering one question — e.g. an L1/L2/L3 model. callout also now supports tone: success (green).