LiveFor production workflows.

Live data your agents run on.
6,045 live data tools behind one URL.
Frontier models: 100% correct with Pipeworx, 63% with web search

1.7M+ requests/month13K+ unique visitors/month

Augment the systems you already have. A retrieval index, an enrichment job, a nightly report — each one was accurate when it was built, and each one drifts. Pipeworx is the live half: 1,571 primary sources behind one URL, including the SEC, the FDA, the Fed, ClinicalTrials, USPTO and EPA. Every answer carries its source and fetch time, so what your system writes down stays checkable — and grounding a question costs about a tenth of searching for it. No API keys, and your agent loads only the ~20 tools a job needs.

Watch EU tenders in the categories you bid on. Flag the drugs clearing Phase 2 in your therapeutic area. Track a competitor’s patent filings.Jobs that run on a schedule, not questions you type once.

Top packs

The 9 most-used, by how many different agents reached for them this week — not by how many calls they took, which would just show you whoever ran the biggest job. The rest of 1,571 sources rotate below ·6,045 tools across the catalog ·browse all →

Browse all 1571 packs →

How it works

A real example: agent connects to Pipeworx, asks for Apple's full profile, gets SEC filings + fundamentals + patents + news + LEI back in one round trip — across five packs, in parallel, with citation URIs.

01

Add Pipeworx to your MCP client

Drop one JSON block into claude_desktop_config.json, Cursor settings, or any MCP-aware client. No API keys, no SDK install.

claude_desktop_config.json
{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}
02

Your agent makes one call instead of fifteen

User asks for a company brief. The agent calls one Pipeworx meta-tool —entity_profile — which fans out across SEC EDGAR, SEC XBRL, USPTO, GDELT, and GLEIF in parallel inside the gateway. No orchestration code, no sequential round-trips burning context.

User → Agent → Pipeworx
User: Give me a brief on Apple.

Agent calls:
  entity_profile({
    type: "company",
    value: "AAPL"
  })
03

Pipeworx returns five sources of structured data with citations

One JSON-RPC call returns SEC filings, fundamentals (Revenue / NetIncome / Cash from XBRL), USPTO patents, recent news, and the LEI — each item carrying apipeworx:// URI for stable citation. Partial failures (e.g., a rate-limited upstream) surface in sources_failed rather than breaking the whole call.

Gateway response (truncated)
{
  "ticker": "AAPL",
  "cik": "0000320193",
  "company_name": "Apple Inc.",
  "lei": "HWUPKR0MPOU8FGXBT394",
  "recent_filings": [
    { "form": "10-Q", "date": "2026-05-01",
      "_pipeworx_uri": "pipeworx://edgar/company/0000320193/filings/..." },
    { "form": "8-K", "date": "2026-04-30", "_pipeworx_uri": "pipeworx://edgar/..." }
  ],
  "fundamentals": {
    "Revenues":      { "value": 416161000000, "unit": "USD", "period": "2025-09-27" },
    "NetIncomeLoss": { "value": 112010000000, "unit": "USD", "period": "2025-09-27" },
    "CashAndCashEquivalentsAtCarryingValue":
                     { "value":  29943000000, "unit": "USD", "period": "2024-09-28" }
  },
  "recent_news": [...],
  "sources_used":   ["edgar", "sec-xbrl", "gleif", "gdelt"],
  "sources_failed": []
}

Common questions

What is Pipeworx?

Pipeworx is an open MCP gateway that connects AI agents to live data from 1571 sources — SEC EDGAR, FDA, FRED, the Census Bureau, USPTO, EPA, UN Comtrade, ClinicalTrials.gov, and many more. One gateway URL exposes 6,045 tools, and your agent loads only the ones it needs for the task at hand.

How do I connect my AI agent to Pipeworx?

Add a single MCP server entry pointing at https://gateway.pipeworx.io/mcp. The gateway speaks the full Model Context Protocol — Tools, Resources, and Prompts — so it works with Claude Desktop, Claude Code, Cursor, VS Code, ChatGPT, Windsurf, and any other MCP-compatible client without an SDK install.

What is MCP (Model Context Protocol)?

MCP is an open protocol for connecting AI agents to external tools and data. It standardizes how an agent discovers, calls, and cites data sources. The spec defines three primitives — Tools (function calls), Resources (citable URIs), and Prompts (workflows). Pipeworx ships all three, plus seven gateway-native meta-tools that collapse multiple round-trips into one.

Do I need to manage API keys for each data source?

No. The Pipeworx gateway handles authentication for public sources (FRED, SEC EDGAR, FDA, Census, BLS, EPA, ClinicalTrials, USPTO, and many more) without any keys at all. For premium sources like ATTOM, Altos, or Alpha Vantage you can bring your own key, or use metered Pipeworx access on a paid plan.

How is Pipeworx different from Composio, Smithery, or Zapier MCP?

Composio, Pipedream, and Zapier MCP target human-triggered workflows and SaaS automations. Smithery, mcp.so, and Glama are directories that index third-party MCP servers. Pipeworx is a single live MCP gateway running 1571 data sources behind one protocol, designed for autonomous-agent traffic and on-demand tool loading rather than human-in-the-loop tasks.

Why does on-demand tool loading matter for AI agents?

Loading every available tool definition into model context burns tokens on definitions the agent never uses — what we call the context tax. Pipeworx returns only the ~20 most relevant tools per task via discover_tools, ?task= scoping on the gateway URL, or vertical bundles. Compound _intel tools further collapse 5–15 round-trips into one. Result: less context burned, faster responses, more stable transcripts.

Is Pipeworx free to use?

Yes for most usage. The free tier allows 50 calls per day anonymously or 200 calls per day with a free GitHub-linked account. Paid plans add unlimited usage with metered billing, budget controls, and access to premium verticals (Housing Intel, FinTech, PharmaPulse, GovCon Radar, AgriPulse, TradeGuard, GreenLens). All public-source data is included on every tier.

Get started

Use the SDK in any TypeScript/Node project, or connect any MCP client — Claude Desktop, Cursor, Windsurf, or your own app.

SDK
import { Pipeworx } from '@pipeworx/sdk';
const px = new Pipeworx();
const result = await px.ask("What is the US trade deficit with China?");
MCP Client Config
{ "mcpServers": { "pipeworx": { "url": "https://gateway.pipeworx.io/mcp" } } }