Verticals

A vertical is a curated bundle of packs for a domain. They exist for two reasons: discoverability (one URL = “everything an agent doing housing research needs”) and packaging (some verticals include paid data sources you can subscribe to as a unit).

You don’t have to use verticals — the default gateway.pipeworx.io/mcp exposes everything. But scoping by vertical keeps context low and the agent focused.

Active verticals

Vertical	Slug	What’s inside	URL
Housing Intel	`housing`	FRED, BLS, Census, HUD, ATTOM, Altos, FEMA, housing-intel compound	/verticals/housing
FinTech	`fintech`	SEC EDGAR, CFPB, FDIC, AlphaVantage, CoinGecko, fintech-intel compound	/verticals/fintech
PharmaPulse	`pharma`	ClinicalTrials.gov, OpenFDA, RxNorm, WHO, CDC, pharma-intel compound	/verticals/pharma
GovCon Radar	`govcon`	SAM.gov, USAspending, SBIR, Federal Register, govcon-intel compound	/verticals/govcon
AgriPulse	`agri`	USDA NASS, BLS, FRED, Comtrade, weather	/verticals/agri
TradeGuard	`trade`	UN Comtrade, Census Trade, Treasury, IMF, trade-intel compound	/verticals/trade
GreenLens	`green`	EPA ECHO, EPA Emissions, TRI, AirNow, climate disclosures	/verticals/green

How to use one

Append ?vertical=<slug> to the gateway URL:

{
  "mcpServers": {
    "pipeworx-housing": {
      "url": "https://gateway.pipeworx.io/mcp?vertical=housing"
    }
  }
}

Or scope by task instead, which uses semantic search instead of a curated list:

https://gateway.pipeworx.io/mcp?task=mortgage+rates

?vertical= is hand-curated; ?task= is on-the-fly semantic. Use the vertical when you know the domain; use ?task= when you don’t.

Pack vs. vertical vs. compound tool

These three layers compose:

Pack = one data source’s tools (fred pack = FRED-specific tools)
Compound tool = one tool that calls 3–5 upstream APIs (housing_market_snapshot = FRED + BLS + Census in one call)
Vertical = a bundle of packs + compound tools for a domain (housing vertical = fred + bls + census + hud + attom + altos + housing-intel)

A typical agent flow at the housing vertical:

Connect: ?vertical=housing → ~30 tools loaded
For a snapshot: call housing_market_snapshot (1 compound call)
For drilldowns: call individual tools as needed (fred_get_series, attom_avm, etc.)

Multiple verticals

You can mount multiple in the same client:

{
  "mcpServers": {
    "pipeworx-housing":  { "url": "https://gateway.pipeworx.io/mcp?vertical=housing" },
    "pipeworx-fintech":  { "url": "https://gateway.pipeworx.io/mcp?vertical=fintech" }
  }
}

Each connection is independent — separate tool list, separate session memory.

Custom vertical

If your use case spans multiple verticals or has non-standard packs, build a custom one at pipeworx.io/account. You pick which packs to include and get a signed URL.