One room for every SDK release decision.

SDK Parity turns API and SDK changes into stable release artifacts: normalized specs, TypeScript manifests, compatibility reports, overlays, and agent dry-runs.

Spec to SDK evidence

Normalize OpenAPI changes, extract SDK surfaces, and show the exact compatibility impact before release.

Overlay review

Keep naming, pagination, resources, and error decisions explicit instead of burying them in generated code.

Agent-safe execution

Expose dry-run MCP and Code Mode workflows with typed contracts, redaction, and audit output.

Release operations

Give product, SDK, and platform teams one room for runs, reports, billing gates, and reviewer signoff.

Release workflow

A narrow path from API change to SDK release evidence.

01
Connect
Point SDK Parity at an OpenAPI source, repo, or CI artifact.
02
Extract
Build a TypeScript SDK manifest from the generated surface.
03
Compare
Diff previous and candidate manifests against the normalized API graph.
04
Approve
Ship with a review packet that humans, CI, and agents can inspect.

Artifact map

Every layer has a typed output.

Layer	Input	Output
Source	OpenAPI	operation graph
SDK	TypeScript	surface manifest
Review	Compatibility	semver recommendation
Agent	MCP dry-run	typed tool result
Platform	Billing gate	usage and entitlement

Typed output

{
  "sdk": "typescript",
  "semver": "minor",
  "majorBreakages": 0,
  "addedSymbols": 4,
  "removedSymbols": 0,
  "agentWrites": "dry-run",
  "nextAction": "approve"
}

json

Integration layers

Keep your generated SDK, docs snippets, and agent tools attached to the same source of truth.

Start with TypeScript, prove the compatibility loop, then add languages and publishing paths once the evidence model is trusted.