Tools for When "It's Valid" Still Doesn't Work
Inspectly provides simple, browser-based tools that explain silent failures in APIs, configs, and data — no accounts, no uploads, no storage.
100% Client-Side
All analysis runs in your browser. Your specs never leave your machine.
Instant Analysis
No sign-ups, no waiting. Paste your spec and get results immediately.
Actionable Insights
Get clear explanations of why things break and how to fix them.
Available Tools
Each tool focuses on a specific kind of silent failure. Pick the one that best matches the problem you are debugging.
Configuration & Environment Drift
Config Diff Inspector
Compare environment configs the way your app actually reads them, so you can see why staging and production behave differently.
Helps when you ask:
- Why does production behave differently from staging?
- Which config keys are missing between environments?
- How do I safely diff appsettings.json, .env, and Helm values.yaml?
How it helps
- Normalizes JSON, .env and YAML so you diff what the app really sees.
- Flags missing keys, type changes, and suspicious value drift between environments.
- Separates noisy differences from the ones that explain "it only breaks in prod".
OpenAPI & API Specs
OpenAPI Silent Failure Validator
Find the subtle OpenAPI issues that pass schema validation but quietly break Swagger UI, code generators, and strongly-typed clients.
Helps when you wonder:
- Why is my OpenAPI spec valid but not working?
- Why does Swagger UI ignore or hide my examples?
- Why do code generators choke on my nullable/oneOf schemas?
How it helps
- Analyses your OpenAPI like Swagger UI and generators do, not just the schema.
- Highlights unions, nullable fields, and examples that are valid on paper but break tools.
- Ranks issues by risk so you know what silently breaks clients first.
HTTP Contract Drift
HTTP Contract Drift Inspector
Compare expected contracts with real HTTP payloads to spot missing fields, type drift, and structural changes that silently break clients.
Helps when you suspect:
- Why do valid API requests get rejected?
- Why does the response break my client?
- Did the API contract drift without versioning?
How it helps
- Compares expected contract samples with real HTTP payloads field by field.
- Flags missing required fields, extra fields, type mismatches, and structural drift.
- Classifies findings by how likely they are to silently break generated or strongly-typed clients.
Data & Payload Debugging
JSON Runtime Checker
Explain why syntactically valid JSON crashes deserializers, validation rules, or downstream logic.
Helps when you see:
- Why does valid JSON still crash my app?
- Are duplicate keys breaking deserialization?
- Why is a boolean treated like a string?
How it helps
- Scans for parser edge cases like duplicate keys and mixed-type arrays.
- Surfaces type traps (string vs boolean/number) that compile but blow up at runtime.
- Translates "deserialization failed" into specific, fixable causes.
Dependencies & Compliance
Dependency License & Risk Inspector
Inspect dependency lists to detect risky, incompatible, or surprising licenses before they become a legal or delivery problem.
Helps when you worry:
- Why is GPL showing up in my dependency tree?
- Are any dependencies legally risky for my project?
- Can transitive dependencies cause license issues?
- Why did legal flag this package late?
How it helps
- Walks your dependency text for license signals and transitive chains.
- Highlights strong copyleft, unknown, or surprising licenses earlier in the lifecycle.
- Surfaces patterns to discuss with legal/compliance without making legal conclusions.