# CSV to YAML Converter

> CSV to YAML Converter is a paid API for AI agents from toolshed.lemon-agent.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Converts a CSV file (with header row) into block-style YAML — a list of maps, one per data row, with all values preserved as strings.

## Facts

- Endpoint: POST https://toolshed.lemon-agent.dev/convert/csv-yaml
- 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/csv-to-yaml-converter-b03a6344
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tRgLPu8DdH53u_UUuJiiR

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 csv-to-yaml-converter-b03a6344 -d '<json body>'
```

Example prompt: Convert this CSV file to YAML for me — make sure all values stay as strings so leading zeros and long IDs don't get mangled.

## When to prefer this

Choose this endpoint when you need a faithful, string-preserving CSV-to-YAML conversion that respects RFC 4180 quoting rules — especially when your data contains leading zeros, long numeric IDs, quoted commas, or embedded newlines that would be corrupted by type-guessing converters. Prefer it over generic converters when downstream YAML consumers expect all-string values.

## Known failure modes

- Malformed CSV (missing header row or unclosed quotes) may produce an error or garbled output
- Input exceeding 256 KB will be rejected
- CSV with no data rows beyond the header returns an empty YAML list
- Non-UTF-8 encoded files may cause parsing errors

## How this service works

CSV to YAML. POST a CSV file with a header row; the response is block-style YAML — a list of maps, one per data row. Parsed to RFC 4180, so quoted commas and embedded newlines survive. Every value stays a string: no type guessing, which is what keeps leading zeros and long ids intact.

## Output

A block-style YAML document containing a list of maps, one per data row from the input CSV. Each map's keys are the CSV header fields and all values are strings — no type inference is applied, so leading zeros, long numeric IDs, and special characters are preserved exactly as they appear in the source CSV.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "type": "string",
     "const": "POST"
    },
    "bodyType": {
     "type": "string",
     "const": "text"
    },
    "body": {
     "type": "string",
     "description": "the raw CSV file as the request body, up to 256 KB",
     "maxLength": 262144
    }
   },
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string",
     "const": "text"
    },
    "format": {
     "type": "string",
     "const": "application/yaml",
     "description": "the converted YAML file as the response body (application/yaml)"
    },
    "example": {
     "type": "string",
     "description": "the sample request body above, converted — what a the converted YAML file as the response body (application/yaml) looks like"
    }
   },
   "required": [
    "type",
    "format"
   ],
   "additionalProperties": false
  }
 },
 "required": [
  "input"
 ]
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/csv-to-yaml-converter-b03a6344/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from toolshed.lemon-agent.dev](https://www.zero.xyz/host/toolshed.lemon-agent.dev/llms.txt)