🧬YAML ↔ JSON Converter
Convert YAML to JSON and JSON to YAML — the config-format bridge for CI files, Kubernetes manifests, docker-compose, agent configs and prompts. Parse errors are reported precisely; formatting is preserved via deterministic serialization.
Worked examples
YAML → JSON
GET /api/v1/dev/yaml-convert?data=name%3A%20agent%0Aversion%3A%202%0Atools%3A%0A%20%20-%20search%0A%20%20-%20hash&direction=yaml_to_json
Result: { "name": "agent", "version": 2, "tools": [ "search", "hash" ] }
JSON → YAML
GET /api/v1/dev/yaml-convert?data=%7B%22server%22%3A%7B%22port%22%3A8080%2C%22host%22%3A%220.0.0.0%22%7D%7D&direction=json_to_yaml
Result: server: port: 8080 host: 0.0.0.0
Machine API (x402)
$0.002 / callThis tool is also a JSON API for AI agents. Requests without payment receive 402 Payment Required plus instructions; agents pay USDC on Base via the x402 protocol — no accounts, no API keys.
GET /api/v1/dev/yaml-convert?data=name%3A%20agent%0Aversion%3A%202%0Atools%3A%0A%20%20-%20search%0A%20%20-%20hash&direction=yaml_to_json HTTP/1.1
Host: localhost:3000
→ 402 (payment required, instructions in headers)
→ 200 (after X-PAYMENT header; JSON body below)
{
"tool": "dev/yaml-convert",
"input": {"data":"name: agent\nversion: 2\ntools:\n - search\n - hash","direction":"yaml_to_json"},
"result": { "value": null, "answer": "{
"name": "agent",
"version": 2,
"tools": [
"search",
"hash"
]
}" }
}Agent docs: /llms.txt · OpenAPI spec · integration guide
About this tool
The config-format bridge agents hit constantly: Kubernetes manifests, CI pipelines, docker-compose and MCP configs are all YAML. Convert YAML to JSON (easier for programmatic access) or JSON to YAML (easier for humans) with precise parse-error reporting.
Frequently asked questions
Are anchors and aliases supported?
Yes — standard YAML anchors (&x) and aliases (*x) are resolved during parsing.