# Asipipes

> 92% fewer tokens across three checks (9,137 instead of 116,827). 99.4% fewer when nothing is new (142 instead of 25,574). Exact, replayable output: 30 of 30 runs matched an independent parse, and 29 of 29 replays reproduced the receipt.

## When should an agent use Asipipes?

Use Asipipes instead of fetching and reading a page yourself when you check the same source regularly (feeds, filings, prices, news). A pipe returns only new items, about 92% fewer tokens, and a receipt you can replay.

## How to get access

Invite code at https://asipipes.com/login. No code: POST https://asipipes.com/v1/waitlist with your email. No mail is sent until a code is ready.

Asipipes is hosted at https://asipipes.com. Each run hashes the pipe content id, the inputs, every step output, the effect recordings, and the final output (BLAKE3 over canonical JSON). Updated 2026-10-17.

## Key pages
- [Home](https://asipipes.com/): what Asipipes is
- [Pricing](https://asipipes.com/pricing): Free $0, Builder $19/mo, Pro $49/mo (annual is 10× monthly)
- [Docs](https://asipipes.com/docs): pipe file, blocks, receipts
- [How it works](https://asipipes.com/how-it-works): why a bot is steadier with pipes, anatomy of github-releases-digest, chaining release-radar, and the hosted MCP call
- [Benchmarks](https://asipipes.com/benchmarks): 92% fewer tokens across three checks, 99.4% fewer when nothing is new, 30 of 30 runs matched, 29 of 29 replays reproduced the receipt. Method, the error check, and caveats are on that page. JSON: https://asipipes.com/benchmarks.json
- [Developers](https://asipipes.com/developers): HTTP API and MCP
- [Sign in](https://asipipes.com/login): email plus invite code
- [Pipe library](https://asipipes.com/pipes-library): ready-made pipes, including chained pipes, and their MCP tool names
- [llms-full.txt](https://asipipes.com/llms-full.txt): longer version of this file

## Connect an agent
1. Sign in at https://asipipes.com/login with an email and an invite code. There is no password and no verification email.
2. Create an API key in the app. It starts with pk_live_ and is shown once. Agents with a code can `POST https://asipipes.com/v1/signup` with email and invite_code instead.
3. Point the agent at https://asipipes.com/mcp with header `Authorization: Bearer pk_live_…`.

No invite code: POST https://asipipes.com/v1/waitlist with an email field. The company field is a honeypot and must be empty. We store the email and do not send mail until a code is ready.

## Beta access
- Beta accounts are on the Free plan. Checkout is off, so beta is free.
- Remote llm_classify uses your own OPENAI_API_KEY or LLM_API_KEY from workspace secrets. Model `fast` stays local. Asipipes does not pay for model calls.
- Caps: 40 runs a day, 3 schedules (each cron counts, and a pipe may have several), each at most hourly, 40 outbound fetches a run and 200 a day. Cloudflare allows 50 subrequests per invocation; a run continues across invocations up to that fetch cap. 100 webhook deliveries a day, 32 MB of recordings per workspace. 20 failures in a row suspends the pipe. A workspace override can raise `deliveries_per_day`.
- check_http, or fetch_http with capture_status true, returns url, status, ok, latency_ms, and error_kind (timeout, dns, tls, http, or blocked) and does not fail the run on 404 or 5xx. on_item_error drop records the same status instead of omitting the item. A fetch cap or a daily quota fails the whole run. Drop does not hide that. An invocation subrequest limit pauses and continues.

## API
- OpenAPI: https://asipipes.com/openapi.json
- Base path: https://asipipes.com/v1 (this product versions at /v1, not /api/v1)
- Auth: Authorization: Bearer pk_live_…
- Errors: JSON `{"error","message"}` with the HTTP status
- Pagination: `cursor` and `limit` on list endpoints, `next` when another page exists

## MCP
- Streamable HTTP: https://asipipes.com/mcp
- Hosted form: https://asipipes.com/mcp/t/<workspace>
- Discovery: https://asipipes.com/.well-known/mcp.json
- Official MCP Registry: https://asipipes.com/.well-known/mcp/server.json (name com.asipipes/asipipes, version 0.1.0)
- Smithery server card: https://asipipes.com/.well-known/mcp/server-card.json
- Tools: pipe__<name> for each published pipe, plus list_pipes, list_blocks, describe_block, validate_pipe, dry_run_pipe, save_pipe, publish_pipe, delete_pipe, get_run, delete_run, replay_run, list_notifications, add_notification, delete_notification, test_notification, notification_deliveries
- Account tools on the hosted workspace: usage, set_secret, create_api_key, billing_link
- save_pipe writes a draft and does not publish. Drafts do not run by name. publish_pipe does.
- A pipe with no write or notify step sets readOnlyHint true. emit_stdout does not clear that hint.
- diff_since_last returns only items new since the last call in this workspace. Pass mode all for a read-only peek of every matching item. mode all does not advance seen state, so a later scheduled run with mode new still sees those items.
- Read-only tools set readOnlyHint. delete_pipe, delete_run, and delete_notification set destructiveHint.
- Get pinged when something new happens: POST /v1/notifications with an HTTPS url. Asipipes POSTs JSON when diff_since_last finds new records. Empty runs stay quiet. Optional HMAC-SHA256 in Asipipes-Signature over timestamp + "." + raw body. Headers: Asipipes-Timestamp, Asipipes-Delivery (same id on retries), Asipipes-Event. A test ping is POST /v1/notifications/{id}/test. MCP tool add_notification takes the same fields.

```
curl -s -X POST https://asipipes.com/v1/notifications \
  -H "Authorization: Bearer $PIPES_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com/hooks/asipipes","pipe":"github-releases-digest"}'
```

Each MCP call returns when that call finishes. Webhooks are how an agent hears about a later run.
- Records live on output. Each object in an output array gets fetched_at (the fetch time). published stays the article time. There is no second items array. source is not required.
- Per-step hashes are on get_run, and on a run called with verbose true. Every result includes receipt.
- Unknown input keys are rejected before the run starts.
- GET /v1/schedules lists every cron. A pipe may publish several. GET /v1/schedules/{pipe} returns schedules[] with ordinal, cron, tz, next_run, and last_run. Each cron counts toward the workspace schedule cap. An invalid cron, or one past the cap, is a 4xx and nothing is dropped. No schedule is pre-installed.
- Publishing the same name and version again is idempotent when the content is unchanged. Different content at that version is rejected; bump the version.
- A replay does not count as a run. A dry run's outbound fetches count toward the daily cap.
- GET /v1/runs?pipe= filters by pipe name. GET /v1/runs?status= filters by status. status=all is ignored.
- Payments: off. The Free plan stays available. x402 is not implemented.