post_data_convert
Deterministic data-format conversion — the shape work an LLM cannot do reliably token-by-token. POST {data, from, to}: JSON, NDJSON, CSV, TSV, or a SQL INSERT dump in; any of the same out. Handles RFC 4180 quoting (commas, quotes, newlines in values), flattens nested objects to dot-notation columns, unions ragged records into a stable column set, and parses SQL string literals with '' and ' escapes. No AI, no network — same input, same bytes, every time. ($0.005 per call, paid via x402)
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | csv (default), tsv, json, ndjson, or sql | |
| data | Yes | The dataset as a string (up to ~4MB) | |
| from | No | json (default), ndjson, csv, tsv, or sql | |
| table | No | Table name when to=sql (default 'data') | |
| header | No | CSV/TSV input has a header row (default true) | |
| flatten | No | Flatten nested objects to dot-notation columns (default true) | |
| delimiter | No | Override the delimiter for csv/tsv | |
| infer_types | No | Convert numeric/boolean/null strings on input (default true); leading zeros stay strings |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | ||
| from | No | ||
| rows | No | ||
| bytes | No | ||
| output | No | ||
| columns | No |