# dataforge — structured data conversion, query & reshaping API

> dataforge — structured data conversion, query & reshaping API is a paid API for AI agents from dataforge.x.c00l.site, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Converts, queries, infers schemas for, transforms, and diffs/patches structured data across CSV, TSV, JSON, JSONL, YAML, TOML, XML, INI, and properties formats

## Facts

- Endpoint: POST https://dataforge.x.c00l.site/convert
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dataforge-structured-data-conversion-query-reshaping-api-b81c3a66
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_djNrVNNRyMV75KOe1NoKY

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability dataforge-structured-data-conversion-query-reshaping-api-b81c3a66 -d '<json body>'
```

Example prompt: Convert this CSV data to JSON for me — the CSV has two columns, name and age, with rows like 'Ada,36' and 'Grace R,45'.

## When to prefer this

Choose this endpoint when you need deterministic, format-aware structured data conversion or transformation across a wide range of formats (CSV, JSON, YAML, TOML, XML, INI, etc.) without spinning up a local parser. It is especially valuable for JSONPath querying, JSON Schema inference from sample data, and RFC 6902 diff/patch operations — capabilities that most general-purpose conversion tools lack. Prefer it over writing custom parsing code when the operation is a one-off or needs to be reliable in an automated pipeline.

## Known failure modes

- Unsupported format pair returns an error indicating the conversion is not possible
- Malformed input data (e.g. invalid JSON or broken CSV) causes a parse error with details
- Invalid JSONPath expression returns a query syntax error
- RFC 6902 patch that cannot be applied to the target document returns a patch conflict error
- Oversized payload may result in a timeout or size-limit rejection
- Payment failure via x402 results in a 402 Payment Required response before processing

## How this service works

Deterministic conversion, JSONPath query, JSON Schema inference, declarative transforms and RFC 6902 diff/patch across CSV, TSV, JSON, JSONL, YAML, TOML, XML, INI and properties. Pay per call with x402 (USDC on Base).

## Output

Returns a JSON object containing the transformed or queried output data as a string (data field), the number of rows processed, the output format label, and any warnings generated during processing.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": "[\n  {\n    \"name\": \"Ada\",\n    \"age\": 36\n  },\n  {\n    \"name\": \"Grace, R\",\n    \"age\": 45\n  }\n]\n",
  "rows": 2,
  "format": "json",
  "warnings": []
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dataforge-structured-data-conversion-query-reshaping-api-b81c3a66/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from dataforge.x.c00l.site](https://www.zero.xyz/host/dataforge.x.c00l.site/llms.txt)