# StationFX JSON-to-TOON Converter

> StationFX JSON-to-TOON Converter is a paid API for AI agents from stationfx.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-01).

Converts a JSON payload into TOON (Tokenized Object Notation), a compact pipe-delimited format that reduces token count by ~60-70% versus equivalent JSON for time-series data.

## Facts

- Endpoint: POST https://stationfx.com/util/convert/json-to-toon?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/stationfx-json-to-toon-converter-eaa83cf2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_x-Z-HWDYbsumgpK2gMSZV

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 stationfx-json-to-toon-converter-eaa83cf2 -d '<json body>'
```

Example prompt: Take this JSON array of time-series economic data and convert it to TOON format so I can fit more of it into my LLM context window — it's about 200 KB of raw JSON.

## When to prefer this

Choose this endpoint when you need to pass large JSON time-series datasets to an LLM and context window or token cost is a concern. It is specifically optimized for array-shaped time-series data (e.g. financial, economic, or sensor readings) and achieves 60-70% token reduction. Prefer it over generic compression if your goal is LLM-token efficiency rather than byte-level compression. Not ideal for deeply nested or non-tabular JSON structures where the gains may be smaller.

## Known failure modes

- HTTP 413 if the request body exceeds 512 KB — checked before payment is processed
- Invalid or malformed JSON body returns an error without consuming a payment
- Missing required 'input' field in the request body results in a validation error
- Unsupported HTTP method (anything other than POST/PUT/PATCH) returns a 405
- Authentication failure if bearer token is invalid or expired; payment via x402 USDC on Base required if no token is present

## How this service works

Convert a JSON payload to TOON (Tokenized Object Notation), a compact pipe-delimited format that achieves ~60-70% token reduction versus equivalent JSON on time-series payloads. Accepts a raw array or an envelope {meta, data, result_type}. Max body: 512 KB (HTTP 413 if exceeded; checked before payment). Pay $0.005 per call via x402 USDC on Base, or use a bearer token from /token/purchase.

## Output

A plain-text TOON-formatted string (text/plain; charset=utf-8) consisting of pipe-delimited rows with a header block, representing the original JSON data in a compact form that typically uses 60-70% fewer tokens than the equivalent JSON for time-series payloads.

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "properties": {}
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "schema": {
  "type": "object",
  "required": [
   "result"
  ],
  "properties": {
   "result": {
    "type": "string",
    "description": "TOON-formatted text (text/plain; charset=utf-8). Pipe-delimited rows: result_type header, field names, separator, then one row per observation. ~60-70% fewer tokens than equivalent JSON for time-series data."
   },
   "content_type": {
    "type": "string",
    "description": "Always text/plain; charset=utf-8"
   }
  }
 },
 "example": {
  "result": "result_type=series\nfields=date|value\n---\n2024-01-01|27360.99\n2024-04-01|27490.12",
  "content_type": "text/plain; charset=utf-8"
 }
}
```

## More

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