Zyla API Hub is answering right now. Last checked 12 min ago. It exposes 8 tools.
Discover and call 10,000+ production APIs from one MCP server. Pay-per-call billing for AI agents.
Uptime history
47 days of history
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
8
Tools
read from the server
71 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 4
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 September 2026. No other catalogue keeps this.
8 Sep
4 tool descriptions were rewritten
account_status, call_api, get_payment_url and 1 more
Nothing serious here today
Today is the operative word: we check Zyla API Hub every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.
run in your terminal
claude mcp add api-hub --transport http https://mcp.zylalabs.com/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"api-hub": {
"url": "https://mcp.zylalabs.com/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.api-hub]
url = "https://mcp.zylalabs.com/mcp".cursor/mcp.json
{
"mcpServers": {
"api-hub": {
"url": "https://mcp.zylalabs.com/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"api-hub": {
"url": "https://mcp.zylalabs.com/mcp"
}
}
}Available tools 8
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
account
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.
api
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.
browse
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.
call
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.
catalog
search_catalog
Semantic search across ALL 10,000+ public APIs on Zyla API Hub. Natural-language queries work best (e.g. "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.
categories
list_categories
List all available API categories on Zyla API Hub with the real count of public APIs in each. Use the category names returned here as the "category" parameter in browse_catalog to filter APIs by category. Example categories: Sports, Finance, Data, Science, etc.
payment
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.
register
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.zylalabs.com/mcp | streamable-http | answering | 77 ms | 12 min ago |
Alternatives to Zyla API Hub
same job, measured the same wayMinia2a MCP
by minia2a
MCP server for minia2a.uk — discover and call 1,600+ x402 pay-per-call APIs with USDC payments.
I
Decixa MCP
by koki-socialgist
Decixa MCP Server — intent-driven API discovery and selection for AI agents.
Agentictrade
by miranttie
AI service marketplace — agents discover, call, and pay for API services automatically.
MCP Package
by ordersofmagnitudellc
MCP server for OOM x402 search 1,000+ pay-per-call API endpoints
PayGate MCP — Monetization Gateway for AI Agents
by geoacpfilho
Monetize any MCP server: x402 paywall, pay-per-call billing in USDC on Base, agent marketplace.
run.pay
by palabrex
Stripe-native marketplace where AI agents discover and pay per call for API services.
Publicdata Kr
by fieldcure
Korean public data API gateway for discovering and calling data.go.kr APIs from MCP clients.
A
Salt
by saltapp
Chat, pay and hire on Salt, with humans and AI agents. Discover agents and products.
Zyla API Hub — questions
Answers built from our own checks of this server.
What can Zyla API Hub do?
It exposes 8 tools, read directly from the server on our last check. Among them: account_status, browse_catalog, call_api, get_api_info, get_payment_url, list_categories and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Zyla API Hub working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 71 ms. The bar chart above shows every period we have measured.
How do I connect Zyla API Hub?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Zyla API Hub need an API key?
No. Zyla API Hub completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Zyla API Hub?
It answers our handshake in 71 ms on average, which is faster than 86% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.