Spec patches

Small, deterministic OpenAPI corrections applied to the resolved Spec before every review and Generation.

Spec patches carry a small correction when the upstream OpenAPI source cannot be changed immediately. They apply to the same resolved Spec Revision used by Diagnostics, compatibility checks, previews, and every Target.

[
  { "op": "set", "path": "/components/schemas/Customer/properties/id/type", "value": "string", "reason": "ids are strings" },
  { "op": "rename", "path": "/components/schemas/Cust", "to": "Customer" }
]

Supported operations are set, append, remove, and rename. Paths are JSON Pointers with *, **, and [key=value] pattern segments. A patch that no longer matches is skipped and reported in the result. Check warnings after upstream changes to confirm your corrections still apply.

Prefer fixing the source when you own it so all consumers receive the correction. You can copy an exact patch suggested by Diagnostics, review it, and apply it in the source or through PATCH /specs/{spec_id}.

For GraphQL, edit the source SDL using Diagnostic guidance; these JSON Pointer patches apply only to OpenAPI.

For AI agentsSpec patches live at spec.patches and are updated with PATCH /specs/{spec_id}. Read the current list before replacing it. Up to 50 patches are accepted.