# x402-tools Data Format Converter

> x402-tools Data Format Converter is a paid API for AI agents from x402.nichospt.net, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-10).

Converts structured data documents between JSON, YAML, TOML, and CSV formats, billed at $0.01 USDC per call via x402.

## Facts

- Endpoint: POST https://x402.nichospt.net/convert-data?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-tools-data-format-converter-8e22e897
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oXZ5qKafsZJXKpykEjG8N

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 x402-tools-data-format-converter-8e22e897 -d '<json body>'
```

Example prompt: Convert this JSON string to YAML for me: '{"name":"Ada","langs":["ALGOL","Ada"]}'

## When to prefer this

Choose this endpoint when an AI agent needs to programmatically reformat structured data between JSON, YAML, TOML, and CSV as part of a workflow — especially when a pay-per-call micropayment model (x402/USDC) is acceptable and no local conversion library is available or desired.

## Known failure modes

- Invalid or malformed source document returns a parse error
- Unsupported format enum value returns a validation error
- Document exceeds 2,000,000 character limit returns a size error
- Payment failure (insufficient USDC balance) returns HTTP 402
- Conversion semantics mismatch (e.g. CSV to TOML with nested structures) may return an error or lossy result

## How this service works

Pay-per-call utility APIs for AI agents, settled in USDC via the x402 protocol.

## Output

A JSON object containing the converted document as a string in the target format, plus the source and target format labels (e.g. {"from":"json","to":"yaml","result":"name: Ada\nlangs:\n  - ALGOL\n  - Ada\n"}).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "to": {
   "enum": [
    "json",
    "yaml",
    "toml",
    "csv"
   ],
   "type": "string"
  },
  "data": {
   "type": "string",
   "maxLength": 2000000,
   "description": "Source document as a string"
  },
  "from": {
   "enum": [
    "json",
    "yaml",
    "toml",
    "csv"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "to": "yaml",
  "from": "json",
  "result": "name: Ada\nlangs:\n  - ALGOL\n  - Ada\n"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-tools-data-format-converter-8e22e897/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.nichospt.net](https://www.zero.xyz/host/x402.nichospt.net/llms.txt)