Name: Api Gateway
Author: byungkyu

What breaks without openclaw api gateway skill

Scattered API keys. Rate limit crashes. Auth management sprawl.

→

Unified API routing × 160-star proven gateway ÷ 20–30 minutes ÷ zero new vendor lock-in = clean multi-API agents.

openclaw api gateway skill — what it actually does

Routes OpenClaw requests through a single authenticated gateway

Manages credentials and rate limits for multiple services

Defines services in gateway.config.json — no code changes

Calls any connected service with /api <service> <endpoint>

Prevents burst rate limits with built-in request queuing

Security check — openclaw api gateway skill

Privacy score: 7/10 — accesses connected platform APIs only. Lock it: review OAuth scopes before install, confirm Linux, macOS; OpenClaw ≥1.0 compatibility.

Quick start — openclaw api gateway skill in 20–30 minutes

Setup time: 20–30 minutes

You need:

OpenClaw core
API keys for connected services

Install the package:

clawhub install byungkyu/api-gateway

Install skill

Define services in gateway.config.json

Set API keys in .env

Call any service with /api <service> <endpoint>

Troubleshooting openclaw api gateway skill

1. Without request queuing, burst API calls trigger rate limits

2. Never log response bodies containing sensitive data

Compatibility & status

Works with: Linux, macOS; OpenClaw ≥1.0 intermediate Last updated: Oct 2025 ★ 160 on GitHub MIT

Official docs →

View on GitHub →

Related — more like openclaw api gateway skill

More by byungkyu

Each day without a gateway is a day of scattered key management. Install now before another rate limit kills a live workflow.

Get it on GitHub →