Docs

Updated 2026-10-17.

A pipe is a YAML file with pipes: 0, a name, a semver version, JSON Schema inputs and outputs, and a list of steps. Steps form a DAG. The only template syntax is ${path}.

Blocks you can call today

fetch_http, parse_rss, parse_json, csv, regex_extract, hash, dedupe, sort, filter, limit, map, merge, format, diff_since_last, llm_classify (built-in model fast is a local keyword classifier; other models POST to endpoint), emit_stdout, emit_file, emit_webhook. parse_html_select, join, group, llm_extract, read_file, and now still return a clear not-implemented error.

Receipts

A successful run stores a receipt hash. Replay from the recorded snapshot reproduces the output byte for byte and the same receipt. The hash covers the pipe content id, the input hash, each step output hash, each recording hash, and the final output hash. It does not cover the run id or the wall clock.

Call it on Asipipes

1. Sign in at https://asipipes.com/login with an email and an invite code. 2. Create an API key in the app. 3. Send Authorization: Bearer pk_live_… to https://asipipes.com/mcp.

GET /mcp is a JSON 405. POST /mcp is Streamable HTTP.