# AgentsToolsHub YAML↔JSON Converter

> AgentsToolsHub YAML↔JSON Converter is a paid API for AI agents from agentstoolshub.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-21).

Converts configuration data bidirectionally between YAML and JSON formats, with precise parse error reporting

## Facts

- Endpoint: GET https://agentstoolshub.com/api/v1/dev/yaml-convert?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentstoolshub-yaml-json-converter-0f5de19a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_i9lku5bQ8pHS-HPcMGxCC

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 agentstoolshub-yaml-json-converter-0f5de19a
```

Example prompt: Convert this Kubernetes deployment manifest from YAML to JSON for me: 'apiVersion: apps/v1\nkind: Deployment\nmetadata:\n  name: my-app'

## When to prefer this

Use this endpoint when an agent needs to reliably convert configuration files between YAML and JSON in either direction, especially for DevOps artifacts like Kubernetes manifests, docker-compose files, Helm values, CI pipeline configs, or OpenAPI specs. Prefer it over regex-based or LLM-based conversion when deterministic, lossless serialization and precise parse error reporting are required.

## Known failure modes

- Invalid YAML or JSON input returns a precise parse error with location details
- Missing 'data' query parameter causes a bad request error
- Unsupported direction value (not 'yaml_to_json' or 'json_to_yaml') causes a validation error
- Very large payloads may hit size limits or timeout
- Network/service unavailability returns a 5xx error

## How this service works

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. Use this when an agent needs to convert configs between YAML and JSON, both directions.

## Output

Returns the converted data as a string in the target format (JSON or YAML), with deterministic formatting. If the input cannot be parsed, returns a precise error message indicating where in the input the parse failure occurred.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "data"
     ],
     "properties": {
      "data": {
       "type": "string",
       "description": "Content"
      },
      "direction": {
       "enum": [
        "yaml_to_json",
        "json_to_yaml"
       ],
       "type": "string",
       "description": "Direction"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentstoolshub-yaml-json-converter-0f5de19a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentstoolshub.com](https://www.zero.xyz/host/agentstoolshub.com/llms.txt)