pipeworx.io valid

Pipeworx — 7,130 Live Data Tools, No Context Tax

Pipeworx is a single MCP gateway in front of 7,130 tools across 1876 data sources (SEC EDGAR, FDA, FRED, BLS, Census, EPA, ATTOM, Altos, UN Comtrade, ClinicalTrials.gov, RxNorm, USPTO, and more). One URL: https://gateway.pipeworx.io/mcp.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T18:33:20.335Z. Cached copy · Source on pipeworx.io

# Pipeworx — 7,130 Live Data Tools, No Context Tax

Pipeworx is a single MCP gateway in front of 7,130 tools across 1876 data sources (SEC EDGAR, FDA, FRED, BLS, Census, EPA, ATTOM, Altos, UN Comtrade, ClinicalTrials.gov, RxNorm, USPTO, and more). One URL: `https://gateway.pipeworx.io/mcp`.

On a 50-question live-data set (2026-10-16), frontier models answered 100% correctly with Pipeworx and 69% with web search, at roughly one-ninth the cost. Method and per-question results: https://pipeworx.io/benchmark/

## Zero setup — you can call Pipeworx right now

If you are an AI agent reading this and you can make an HTTP request, you need no MCP client, no key, and no signup. Two requests reach real data, and the second is the fast one (data back in under a second, versus ~10s for asking in natural language):

```
GET  https://gateway.pipeworx.io/tools?q=mortgage+rates&limit=5
POST https://gateway.pipeworx.io/v1/tools/fred_get_series {"series_id": "MORTGAGE30US"}
```

The first finds the right tool by topic (name, pack, cost, auth shape, measured reliability, and its schema with real examples, all unmetered); the second returns the data itself, verbatim. Want the full schema or the pinned `version` before you commit? `GET /v1/tools/{name}` is the optional third step, also unmetered. Errors are real HTTP status codes — 400 invalid arguments, 401 auth required, 404 unknown tool — with the specific reason in the body's `error`/`error_class` field.

Or just ask in plain language and let an LLM route it for you — slower (~10s median, up to 24s), but no tool name needed:

```
GET https://gateway.pipeworx.io/ask?q=what+is+the+current+US+unemployment+rate
```

Or POST JSON: `curl -X POST https://gateway.pipeworx.io/ask -H 'Content-Type: application/json' -d '{"question":"current 30-year mortgage rate"}'`

The `/ask` response is JSON `{question, answer, tier}`. `answer` carries structured data fetched live from the routed authoritative source, the routing record (which tool, why), and a `synthesis_directive` — answer from the returned data only and cite it; don't substitute your training data. Anonymous: 50 calls/day per IP, shared with anything else on your egress; `?apikey=YOUR_KEY` (free account at https://pipeworx.io/signup) raises it. OpenAPI spec for Actions/function-calling builders, covering both paths above: https://gateway.pipeworx.io/openapi.json. Full agent instructions: https://pipeworx.io/docs/getting-started/ai-agents/

If your platform supports MCP, connect once instead (see "Connect" below) — you get the full tool surface, grounded-extraction mode, citable pipeworx:// resource URIs, and data-event subscriptions.

The differentiator vs other MCP catalogs: agents don't pay the context tax for everything they don't use. `?task=housing+market` on the gateway URL surfaces only the ~20 most relevant tools instead of all 7,130. `discover_tools(task)` lets the agent semantic-search the catalog mid-session. Compound _intel tools collapse 5 calls into 1.
…

Machine-readable: GET /v1/resolve?q=pipeworx.io · GET /v1/domain/pipeworx.io · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for pipeworx.io:
1. POST https://agentwebmap.com/v1/sites/pipeworx.io/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://pipeworx.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/pipeworx.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/pipeworx.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.