1. Required fields
Check that every required field exists in successful, error, and partial-response cases. Do not assume a field will always be present just because it appeared in one example.
2. Field types
Test strings versus numbers, booleans versus string values such as "true", arrays versus objects, and integer versus decimal values where the consumer expects a specific type.
3. Null, missing, and empty are different
Decide whether null, a missing key, "", [], and {} are all acceptable. Clients often handle these states differently.
4. Enum and status values
Enumerate allowed states and test unknown or newly added values. A downstream switch statement may fail when an API adds a status the client does not recognize.
5. Extra fields and sensitive data
Decide whether additional properties are permitted. Check that debug traces, internal prompts, access tokens, and personal data do not leak into public responses.
6. Boundary and failure cases
Include empty arrays, long strings, zero values, missing nested objects, malformed JSON, timeouts, rate-limit responses, and errors that use a different schema from success responses.
7. Schema drift over time
Keep representative payloads from real versions and rerun them when the provider, model, prompt, tool definition, or API version changes. A successful HTTP status alone does not prove the response matches your contract.
Try it with redacted sample data
Use the free browser-based tester to compare multiple outputs against a JSON Schema. It runs locally in your browser, but currently supports a subset of JSON Schema rules—not every specification feature—so do not treat a PASS as a full compliance or security guarantee.
Request a free one-payload preflight
Not ready to buy? Describe the mismatch and request a limited free check of one redacted example. Do not paste JSON, credentials, personal data, or confidential details into this form. If useful, we will reply by email with the next step; a free preflight is limited and is not a full review.
Need a second pair of eyes?
The manual API & AI-Agent Contract Review covers one JSON Schema or documented contract and up to 10 representative, redacted payloads. You receive a concise PASS/FAIL table and practical recommendations within 2 business days after payment and materials are confirmed.
Launch price: 4 USDT. Current payment options are USDT on TRC20 or BEP20 only; card checkout is not available. Do not pay if you cannot use one of these networks.
Review scope and payment options Ask a question by email
Never send production secrets, credentials, personal data, or confidential customer payloads. Use redacted examples. This service is not a security audit or a guarantee of production correctness.