Submit a data source

Pipeworx is a router, not a directory.

We don't list MCP servers. We route each AI request to whichever of roughly 1,500 data sources can answer it, so there's no catalog placement to apply for.

Building an MCP server? You don't need this form. We sync with the official MCP Registry every day, so if you're registered there you're already included. If you think we've missed something, say hello anyway — we'd rather hear from you than not.

Hosting data you want AI agents to reach? You're in the right place. Send us a link to your API documentation and a key with enough capacity to handle real queries, so we can measure what people actually ask for. We'll integrate the source and see what the demand looks like. If there's enough of it, we're open to paying for access.

One thing worth knowing up front: paid data is served to our paid tiers only. If you want reach as well as revenue, consider offering a useful free slice alongside it — the free tier is where most of the volume, and the clearest demand signal, comes from.

Don't put a key in this form. Describe the source here and email the key to hello@pipeworx.io. We read what comes in, though we can't promise a reply to every submission.

How current the data is, and what it costs you to serve, are both useful here.

Only if you already run one. If you provide it we'll send an MCP initialize and record whether it answered.

Where we can read how the API works. A GitHub repo works too — if you give us one, we'll fetch its stars, description and topics automatically.

Worth giving us if you want to hear back — it's the only way we can reach you.

Submit via API

Submit a data source programmatically. Requires authentication — sign up at /signup to get an API key.

POST https://registry.pipeworx.io/api/submit 
curl -X POST https://registry.pipeworx.io/api/submit \
  -H "Content-Type: application/json" \
  -H "X-API-Key: pwx_your_api_key" \
  -d '{
    "title": "Acme Weather API",
    "description": "Hourly forecasts and observations for 40,000 stations. Docs: https://acme.example/docs",
    "category": "weather",
    "github_url": "https://github.com/user/repo",
    "tags": ["api", "weather"]
  }'

Authentication

Pass your API key via X-API-Key header. Get one at /account after signing up.

Rate limits

5 submissions per day, 20 per week per account.

Required fields

  • title — Name of the source
  • description — What data it covers, and a link to the API docs
  • category — One of: weather, social, geography, science, finance, reference, health, food, culture, education, environment, developer, data, productivity, communication, media, security, ai, ecommerce, blockchain, database, analytics, automation, other
  • endpoint_url or github_url — At least one required. Put your API docs URL in github_url; it accepts any URL and only looks for repository metadata if the link happens to be a GitHub one.

These field names date from when this endpoint took MCP servers, which is why github_url is doing duty as the documentation link and there is no field for licensing or terms. Never send a credential to this endpoint — email it to hello@pipeworx.io instead.

Endpoint check

If you provide an endpoint_url, we'll send an MCP initialize request and record whether it answers with a valid protocol version. That check runs automatically. Anything it does not cover waits to be read by a person, and we can't promise how long that takes.