Zyla API Hub Skill

Turn your OpenClaw AI agent into a real-world operator.
Power it with 10,000+ production-ready APIs from Zyla API Hub — instant access to weather, finance, translation, email validation, geolocation, and more, all through one unified API key, pay-as-you-go pricing, and zero vendor lock-in.

Setup

If ZYLA_API_KEY is not configured, guide the user:

1. 1. Visit https://zylalabs.com/openclaw/connect to get an API key
2. Or run /zyla connect if the plugin is installed (opens browser automatically)
3. Add the key to ~/.openclaw/openclaw.json under INLINECODE3

Never ask the user to paste their API key in chat. Ask them to set it via the config and confirm when ready.

Quick Start — Popular APIs

Use these directly without searching the catalog. Each includes the API ID, endpoint details, and parameters.

Weather by Zip API (ID: 781)

• - Use when: user asks about weather, temperature, forecast, climate, conditions by zip code
• Category: Weather & Environment
• Call: INLINECODE4

Currency Conversion API (example)

• - Use when: user asks about currency exchange, conversion rates, forex
• Category: Finance
• Call: INLINECODE5

Email Validation API (example)

• - Use when: user asks to validate, verify, or check an email address
• Category: Data Validation
• Call: INLINECODE6

Note: Run npx tsx {baseDir}/scripts/generate-popular.ts to regenerate this section with real API IDs and endpoints from the live catalog.

Discovering APIs

For APIs not listed above, search the catalog:

CODEBLOCK0

Calling APIs

Using the helper script (recommended)

CODEBLOCK1

Using curl (fallback)

CODEBLOCK2

URL pattern: INLINECODE8

• - api_id and endpoint_id are numeric IDs (these do the actual routing)
• INLINECODE11 and endpoint_name_slug are URL-friendly names (for readability)

Error Handling

• - 401 Unauthorized: API key is invalid or expired. Ask the user to run /zyla connect or visit https://zylalabs.com/openclaw/connect to get a new key.
• 403 Forbidden: Subscription issue. The pay-as-you-go plan should handle this automatically. If it persists, ask the user to contact support.
• 429 Too Many Requests: Rate limit exceeded. Check the X-Zyla-RateLimit-Minute-Remaining response header. Wait before retrying.
• 404 Not Found: The API or endpoint does not exist. Verify the IDs using the catalog.
• 5xx Server Error: Upstream API issue. Retry after a short delay (2-5 seconds).

Rate Limit Headers

Every API response includes these headers:

• - X-Zyla-RateLimit-Minute-Limit: Max requests per minute
• INLINECODE16: Remaining requests this minute
• INLINECODE17: Total calls this billing cycle
• INLINECODE18: Remaining calls this cycle

Billing

• - Pay-as-you-go: No monthly fee. Each API call is billed at the API's per-call rate.
• Billing happens at the end of each cycle via Stripe.
• Use the health endpoint to check current usage: INLINECODE19