THE DEVELOPER GUIDE

Build a small
data workflow.

API origin: https://route-a-worker.frostskynet-api.workers.dev

Explore three practical workflows, a simple setup guide, and troubleshooting tips ↗

Start without a wallet

GET / returns the current API description. An unsigned POST returns HTTP 402 with x402 payment terms. This request checks the offer; it does not pay or return transformed output.

curl -i https://route-a-worker.frostskynet-api.workers.dev/clean \
  -H 'Content-Type: application/json' \
  --data '{"input":"First example line\nSecond example line","options":{"minChars":3}}'

The example uses Bash quoting. Download the public examples pack for Node.js and Python unpaid checks with no shell quoting required.

Browse the public examples on GitHub ↗ for the README, Node.js and Python offer checks, recorded examples, and example-code license.

Input and output

All tools accept a JSON object with a nonempty input string and optional options object. A successful response is {"output":"…","stats":{…}}. The output is serialized text, even when it contains JSONL. See the OpenAPI schema and recorded examples.

RouteUSDC per requestComplete body limit
POST /clean0.00551,200 UTF-8 bytes
POST /judge0.0110,240 UTF-8 bytes
POST /format0.00551,200 UTF-8 bytes

Clean

Accepts text, JSON, or JSONL; returns cleaned JSONL. Removes empty, short, and duplicate rows. No CSV parsing is provided through this API.

Judge

Accepts JSONL and adds _quality information using fixed rules. There is no AI model call, and llm_score is null. Pattern detection is incomplete and may produce false positives; it does not certify that a dataset is safe, private, or suitable for training.

Format

Accepts JSONL and returns the chosen serialized layout.

Chain tools explicitly

Send the clean response’s output as judge’s input, then judge’s output as format’s input. Each call is separately priced. There is no /pipeline endpoint. The next complete JSON request must fit its own byte limit; judge has a smaller limit than clean.

Pay using an x402 client

  1. Request an unsigned offer.
  2. Review the exact payment terms before signing with your own payment-capable client.
  3. Retry the request with its x402 authorization.
  4. Check the output, settlement result, and public onchain receipt. HTTP 200 alone is not independent settlement proof.

Expected terms: scheme exact, Base mainnet eip155:8453, native USDC token 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, receiver 0x3a1121e787586a504fF74FC53E3AcEE19faDE698. Prices are 5,000 token base units for clean/format and 10,000 for judge. Testnet USDC cannot pay these requests.

An ordinary wallet transfer does not unlock an API request. This website has no wallet connection or checkout. Keep private keys and recovery phrases in your own secure wallet storage; never include them in API inputs or support messages.

For AI clients

Use llms.txt, OpenAPI, and the public service catalog to inspect this interface directly. These files do not automatically configure or fund an agent. Public Bazaar indexing has not been confirmed. Coinbase offers Bazaar discovery and MCP discovery/payment instructions for compatible clients.

Errors and retries

Frequently asked questions

Can I look around without paying?

Yes. The website, documentation, schemas, downloadable examples, and unsigned payment-offer checks are free to use. The website displays recorded synthetic results; it does not process your own input or connect to your wallet.

What does a complete three-step workflow cost?

The advertised prices total 0.02 USDC: 0.005 for clean, 0.01 for judge, and 0.005 for format. These are API prices; review any additional client or network costs separately. Each call is authorized individually, and its complete request must fit that tool’s size limit.

Has real-money payment been tested?

Our controlled mainnet settlement test remains pending. This is a preview release. Recorded examples and HTTP 402 offers demonstrate the interface, not successful real-USDC settlement.

Does “judge” use an AI model?

No. It uses fixed scoring and pattern rules. Redaction can miss personal information or flag false positives. Review outputs before relying on them.

Should I send USDC directly to the receive address?

No. Paid API requests use an x402-compatible client and a signed authorization for the request. An ordinary wallet transfer does not unlock an API call. Never share your private key or recovery phrase.

How do I report a problem?

Use the public examples repository to report documentation or example issues. Include the route, HTTP status, and a small synthetic example that reproduces the problem. Public reports are visible to everyone: omit credentials, payment headers, and personal data. If a signed request times out, investigate settlement before authorizing another payment.

Data handling

This static website uses no analytics, cookies, wallet connection, or input upload. The examples use synthetic data and are served as static files. The API application processes input in memory and logs route, status, and byte count rather than input text. This describes application behavior, not a blanket guarantee about all infrastructure logs. Avoid sending credentials or sensitive records.