Catch bad data before your next import.
Audit a JSON batch for missing values, duplicate rows, mixed types and explicit required/unique/type rules. Get field profiles, failing row indices and a sample-inferred schema without echoing source values.
See a real example result
Calculated by the same tool engine on this fixed synthetic example. No account, payment or external provider call. Use the tool page to submit your own input.
Input · JSON
{
"rows": [
{
"id": 1,
"email": "sample@example.test"
},
{
"id": 1,
"email": null
},
{
"id": 2
}
],
"rules": {
"required": [
"email"
],
"unique": [
"id"
],
"types": {
"id": "integer"
}
}
}Output · JSON
Reveal the result to inspect the output format before using the tool.
What you receive
- Field profiles: completeness, types, distinct counts and duplicate counts
- Rule failures with zero-based row indices, not source values
- Sample-inferred schema and reproducible input/report SHA-256 hashes
Scope & limits
- 1–500 rows, 64 top-level fields and 128 KiB total; bounded nesting/node count.
- Required rejects missing/null/blank. Unique ignores missing/null; types check present values. No coercion or automatic repair.
- Profiles describe this sample only, not correctness of facts. Do not submit credentials or unnecessary personal data.
Use it in your workflow
- Supply JSON rows and optional quality rules.
- Review the quote and authorize one audit.
- Use row indices and field profiles to investigate failures.
API schemas and request examples are on the tool reference. Read the authentication and payment guide.
Your data & delivery
Submitted input and result bodies are not stored by InvokePort. Operational metadata and hashes may be recorded. Do not submit credentials or unnecessary personal data.
Keep your exact original JSON. New confirmed purchases support hash-verified result recovery for 30 days through Purchases, without another payment. Recovery remains subject to tool availability and execution controls.
Delivery problem? Contact support with the request ID.