API Orchestration

API Orchestration is a standalone skill that teaches any OpenClaw agent how to call, chain, and coordinate multiple APIs in production workflows — not just hitting an endpoint, but handling authentication across services, managing rate limits, retrying failures, transforming data between formats, and sequencing multi-step operations that stay reliable even when individual services aren't. Most agents can call one API. This skill teaches them to build pipelines across five.

Drop this skill into any OpenClaw persona's skills folder and your agent immediately knows how to authenticate with any API pattern (keys, OAuth2, token refresh), build retry logic with exponential backoff, respect rate limits without getting blocked, transform data between service formats, and orchestrate multi-step operations with rollback on failure.

🔗 Everything Included This skill covers the full API orchestration lifecycle — no separate purchases needed:

Authentication Patterns — API keys, OAuth2 client credentials, authorization code flow, and automatic token refresh so connections stay alive Error Handling — retry with exponential backoff, circuit breakers, and status code handling that recovers from transient failures automatically Rate Limiting — request throttling, batch processing, and rate-aware scheduling so you stay within limits without manual counting Data Transformation — mapper functions, validation, and format conversion between services so Service A's output feeds cleanly into Service B Orchestration Patterns — sequential pipelines, parallel fan-out, fan-out/fan-in, saga pattern with compensation, and webhook response handling

Proven patterns:

Token management with automatic refresh before expiry Retry logic that distinguishes between retryable and permanent failures Batch processing calibrated to each API's rate limits Saga pattern with compensating transactions for multi-service operations What makes this different from reading API docs: Multi-service coordination — not just calling one API, but chaining many with proper error handling at each step Production failure patterns — what actually goes wrong when you orchestrate 5 APIs and how to handle each failure mode Agent-native — structured for LLM consumption so your agent builds reliable pipelines autonomously Anti-patterns included — the 8 most common API orchestration mistakes that cause silent data loss or cascading failures Reusable code patterns — token managers, rate limiters, circuit breakers, and retry wrappers ready to drop into any project

Includes SKILL.md with complete API orchestration documentation covering authentication, error handling, rate limiting, data transformation, and 5 orchestration patterns. Designed for OpenClaw. Works with any persona that needs to coordinate between services.