Browser-local contract analysis

Contract Workbench

Paste a contract, review the detected format, then choose a focused analysis. Ambiguous tool wrappers ask for your interpretation.

1. Paste a contract or structured document

JSON or YAML · detection up to 1 MiB · all analysis stays in browser memory.

Primary document editor

Loading editor…

2. Interpretation

Treat as

Start with an example or paste your own content.

One entry point for your contracts

Analyze Draft 2020-12 JSON Schema, individual OpenAI, Anthropic, Gemini or MCP tool definitions, MCP tool collections, and OpenAPI 3.1.x or 3.2.x response contracts. Ordinary structured JSON/YAML can be validated against a schema you provide.

For a focused workflow, open schema validation, provider compatibility, MCP toolset analysis, schema comparison or OpenAPI response validation.

Detection suggests a workflow

Specific OpenAPI and MCP collection markers take precedence over general schema patterns. A detected contract can still be invalid. Overlapping OpenAI and Gemini wrappers stay ambiguous until you select a source interpretation; cross-provider checks retain uncertain outcomes.

Choose the analysis you need

Validate a schema or instance, compare two schemas in both directions, inspect provider compatibility, preview wrapper conversions and deterministic repairs, review MCP protocol and documentation findings, or validate documented and captured OpenAPI response bodies. Additional inputs appear for the selected action.

Your inputs stay local

Processing runs in browser workers. There are no live API calls, MCP connections, provider requests, remote imports, external reference fetching, input history or automatic saving. Pasted content is kept in memory and clears on reload. Specialized links open empty tools.

Scope and limitations

Detection is evidence, not a conformance guarantee. Each engine retains its own supported semantics, input limits, source versions and uncertainty. OpenAPI extraction covers response contracts rather than complete document conformance; response bodies support JSON and ordinary text. MCP overlap findings are internal quality heuristics. Schema comparison does not prove general schema equivalence.

Read the privacy policy · Schema tools · AI tools · API contract tools