Format Toolkit
activeConvert, validate, detect, infer-schema and canonicalize structured data — JSON, YAML, XML, CSV, TSV, TOML, NDJSON, INI, .env, .properties, plist, querystring.
- Transactions · 30d
- 0
- Volume · 30d
- $0.00
- Unique buyers · 30d
- 0
- Uptime · 30d
- 100.0%
- Latency p50
- 190ms
- Reported calls · 30d
- 7
Endpoints (5 live)
POST/v1/infer-schema— Infer a JSON Schema (draft-07) from a sample document in any supported format. Types are inferred, present keys are marked required, and heterogeneous array item schemas are merged. The result validates out of the box with /v1/validate. (0.004 USDC on Base)POST/v1/canonicalize— Parse a document (in any format) and re-emit it in the RFC 8785 JSON Canonicalization Scheme form — sorted keys, canonical number/string formatting — plus the SHA-256 of the canonical bytes for stable hashing, signing and dedup. (0.004 USDC on Base)POST/v1/validate— Parse a document (json, json5, jsonc, yaml, xml, csv, tsv, toml, ndjson, ini, env, properties, plist or querystring) and validate it against a JSON Schema. Returns whether it is valid and a list of precise, path-tagged errors. Malformed input or an invalid schema is rejected before payment. (0.004 USDC on Base)POST/v1/detect— Sniff which structured format an unknown document is. Because formats overlap, returns every plausible format with a 0–1 score plus the best guess — honest about ambiguity rather than pretending certainty. (0.004 USDC on Base)POST/v1/convert— Transcode a document between json, json5, jsonc, yaml, xml, csv, tsv, toml, ndjson, ini, env, properties, plist and querystring. Any source converts to any target through a JSON hub. Malformed input or a target that cannot represent the structure is rejected before payment. (0.004 USDC on Base)
First seen · last seen