Zyla API Hub

com.zylalabsPublished by zylalabs.comOfficial publisherv1.0.0Updated Oct 24, 2026

Discover and call 10,000+ production APIs from one MCP server. Pay-per-call billing for AI agents.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping Developer Tools Business & Commerce

Server details

Identifier: com.zylalabs/api-hub
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to zylalabs.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.zylalabs%2Fapi-hub.svg)](https://sourceweft.com/mcp/com.zylalabs%2Fapi-hub?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Lets an assistant search a catalog of 10,000+ public APIs and call them, with pay-per-successful-request billing through a Zyla API Hub account.

What you can do: Provides semantic search and paginated browsing over the Zyla API Hub catalog, plus category listing and detailed API info including endpoints, parameters, JSON schemas and per-call prices. The call_api tool invokes a chosen endpoint and returns the response with the exact billed cost. Account tools register a new account, check usage and billing status, and fetch a Stripe Checkout link to add or update a card.
When to use it: Useful when an assistant needs live external data it does not have, such as weather, prices, stocks, currency rates, transport status or lookups, and you are willing to pay per successful call rather than integrate each API yourself.
Requirements: A remote streamable HTTP endpoint at mcp.zylalabs.com; no local runtime. An Authorization bearer token holding a Zyla API key is optional for discovery tools and required for call_api and account tools. A Zyla account with a credit card on file is needed for paid calls.

Before you install

Calls spend real money: billing is per successful request at each API's listed price, and a card must be on file. The register tool creates an account and returns a payment link, and get_payment_url opens Stripe Checkout. The Authorization header carries a secret API key. Requests send your parameters to third-party APIs outside Zyla.

Installation

In SourceWeft

Open Zyla API Hub in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.zylalabs%2Fapi-hub/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "zyla-api-hub": {
      "type": "http",
      "url": "https://mcp.zylalabs.com/mcp"
    }
  }
}

Tools

search_catalog

Use this FIRST whenever the user needs live, real-world or external data you do not have: train or flight status, weather, prices, stocks, currency rates, company or person lookups, social media data, validation, scraping and more. Semantic search across ALL 10,000+ public APIs on Zyla API Hub. Natural-language queries work best (e.g. "trains departing from a station now", "validate an email address", "get stock prices"). Returns matching APIs ranked by relevance with their ID, name, description, category, price per successful call (USD), average latency (ms), and endpoints summary.

Parameterslimitqueryrequired

get_api_info

Get full details of a specific Zyla API by its numeric ID. Returns the API name, description, category, price per successful call (USD), average latency (ms), and all endpoints with their parameters, example values, and a formal JSON Schema (input_schema) for argument validation.

Parametersapi_idrequired

call_api

Call an API endpoint on Zyla API Hub. Requires the user's API key and a credit card on file. Billing is pay-per-successful-request: you only pay for 2xx responses. Each API has its own price per call (shown in get_api_info), and every successful response includes cost_usd — the exact amount billed for that call. There is no monthly fee and no minimums. Usage is charged to the credit card automatically; call account_status for the billing mode in effect and the amount accrued this cycle. If a 402 error is returned with a payment_url, the user MUST open that URL in their browser to add a credit card before retrying. Pass the api_id, endpoint_id, HTTP method, and parameters.

Parametersapi_idrequiredmethodparamsendpoint_idrequired

browse_catalog

Browse the full Zyla API Hub catalog with pagination. Use this to explore ALL public APIs beyond the top 500. Supports filtering by category and search keyword. Returns paginated results with total count and page info. Results come already ranked: the default "featured" sort is the marketplace order (relevance_score, refreshed daily), so take the list as-is to pick the top APIs.

Parameterspagesortsearchcategoryper_pageinclude_params

register

Register a new Zyla API Hub account directly from the AI agent. Returns an API key AND a payment_url. The user MUST open the payment_url in their browser to add a credit card before making any API calls. Billing model: pay-per-successful-request with no monthly fee and no minimums. Each API has its own per-call price. The card is only ever charged for actual usage; call account_status to see the billing mode in effect and the amount accrued this cycle. No authentication required to call this tool.

Parametersnamerequiredemailrequiredpasswordrequired

account_status

Check the current user's account status, billing, and usage. Returns plan info, API call count, the amount consumed this billing cycle in USD (amount_consumed_this_cycle_usd), the billing mode in effect (billing_mode), whether a credit card is on file, and any failed/pending payments. Use this to diagnose why API calls are blocked (missing card or failed payment). Requires the user's API key in the Authorization header.

Takes no parameters.

get_payment_url

Get a Stripe Checkout URL so the user can add or update their credit card. REQUIRED after registration and whenever a 402 error occurs. The user must open the returned URL in their browser to add/update their card. Billing is pay-per-successful-request: no monthly fee, no minimums. You are only charged for successful API responses (2xx). Prices vary per API (see get_api_info). API calls are blocked until a valid credit card is on file.