FrostSkyNetDATA TOOLS

SMALL TOOLS. CLEAR INPUTS. PER-CALL PRICING.

Messy text in.
Usable data out.

Clean text, check JSONL rows, and turn examples into useful formats. Three focused APIs for developers building data workflows and AI agents.

See the examples Read the guide

0.005–0.01 USDC per request · Base · x402

A SMALL DATA WORKFLOWSynthetic example
01

Clean

Three rows. One duplicate.

3 → 2
02

Judge

Flag a pattern. Redact an email.

[EMAIL]
03

Format

Question + answer → chat examples.

JSONL
One response’s output becomes the next request’s input.

THREE TOOLS, ONE SIMPLE CONTRACT

Choose the step you need.

Send an input string and options. Receive an output string and stats.

POST /clean0.005 USDC

Clear the clutter.

Turn text, JSON, or JSONL into cleaned JSONL. Remove empty, short, and duplicate rows using fixed rules.

51,200-byte request limit Options ↗
POST /judge0.01 USDC

Check each row.

Add rule-based quality scores. Flag selected PII and language patterns, with optional redaction and filtering.

10,240-byte request limit Options ↗
POST /format0.005 USDC

Make it fit.

Convert JSONL to JSONL, chat training examples, or Markdown. Keep your integration focused on the result.

51,200-byte request limit Options ↗

Limits cover the complete UTF-8 JSON body, including options and escaping. Judge uses fixed rules, not an AI model; pattern detection can miss information or flag false positives.

SHOW, THEN BUILD

Follow a real example.

These recorded outputs were generated locally from synthetic data. Selecting a step makes no API payment.

Clean: remove the repeated row

Loading the recorded example…

REQUEST JSON
OUTPUT STRINGDownload sample
The service returns the output string inside a JSON object with stats. Download complete request/response examples ↗

    
FOR DEVELOPERS & PAYMENT-CAPABLE AGENTS
A request.
A price.
A result.
  1. Ask for the tool.
    An unsigned POST returns HTTP 402 with payment terms. GET / provides the API description for free.
  2. Review and authorize.
    An x402-compatible client reviews the network, token, receiver, and amount, then signs the payment authorization.
  3. Get the output.
    The client retries with the authorization. Check both the returned result and settlement evidence.

    
Ready to explore the interface?
Start with schemas and an unpaid request. No wallet is needed to read the docs.
Developer guide ↗OpenAPI schema