Data Conversion API
Convert structured data between JSON, CSV, TSV, YAML, and XML from your code. One endpoint, five formats, clean string output.
Try it
Free endpoint (live during beta)
POST { from, to, data }. from and to are one of json, csv, tsv, yaml, xml. data is your source document as a string.
POST https://data.wrapper-agency.com/api/v1/convert
Content-Type: application/json
{
"from": "json",
"to": "csv",
"data": "[{\"id\":1,\"name\":\"Ada\"}]"
}
→ 200 OK
{
"from": "json",
"to": "csv",
"output": "id,name\n1,Ada"
}GET (for small payloads)
Pass the data inline for quick tests and links:
curl "https://data.wrapper-agency.com/api/v1/convert?from=csv&to=json&data=id,name%0A1,Ada"Bulk / large payloads (paid, x402)
For high-volume or large documents, the per-call endpoint accepts the same body and is priced per request in USDC on Base (x402). Built for AI agents and automated pipelines.
POST https://data.wrapper-agency.com/api/v1/pro/convert
Content-Type: application/json
X-PAYMENT: <x402 payment header>
{ "from": "xml", "to": "json", "data": "<root>…</root>" }Calling without payment returns HTTP 402 with the payment requirements, per the x402 spec. See the OpenAPI spec.
Why FormatForge
- One API, every common format
- JSON ⇄ CSV ⇄ TSV ⇄ YAML ⇄ XML, in any direction.
- Predictable output
- RFC 4180 CSV quoting, indentation-stable YAML, well-formed XML with a root element, and pretty-printed JSON.
- Stateless & private
- Nothing is stored. Each call is independent.
New to this? Read the developer guide.