x402 API Gateway for OpenClaw Bots: One Endpoint Replaces 18 API Keys
An x402 API gateway has been built to simplify OpenClaw bot configuration by replacing multiple API keys with a single endpoint. Instead of managing separate keys for services like Brave Search, Firecrawl, Google Maps, and LLM providers, developers can now use one gateway that handles authentication via USDC wallet credits.
Key Features and Services
The gateway provides access to 18 services without requiring individual API keys:
- Smart LLM Router: Multi-provider access to GPT-5, Claude Opus, Kimi K2.5, and Gemini Flash with auto-routing based on complexity. Simple questions go to fast/cheap models, while hard tasks use more powerful ones. It's OpenAI SDK-compatible—just set your base_url to the gateway.
- Web & Search: Brave Search with snippets and Firecrawl for site scraping.
- Maps & Navigation: Google Maps, Naver Maps, Kakao Maps, and TMap for places, geocoding, directions, and real-time traffic.
- Travel: Flight search with calendar pricing and route discovery, hotel search across 2M+ properties, and worldwide Airbnb listings.
- Food: Michelin Guide (Japan, Korea, USA) and Tabelog for Japanese restaurants.
- AI: ElevenLabs TTS for multilingual text-to-speech and Gemini Image Gen + Video (Veo 3.1 Fast).
- Finance & Data: DART for Korean corporate filings, Financial Modeling Prep for stock quotes, Korea Public Data Portal, and Court Auction for Korean property auctions.
Setup Process
Configuration requires three steps:
- Go to clawy.pro and top up USDC credits (minimum $1)
- Add the clawy-services skill to your bot—it auto-configures the gateway connection
- For LLM routing specifically, point your bot's LLM config base URL at the gateway:
base_url: https://x402.clawy.pro/v1/llm
No API keys are needed in your bot config. The gateway handles authentication via your wallet and deducts credits per token.
Why This Matters
Typical OpenClaw bot setups require 5-10 API keys for basic functionality, each representing a potential point of failure due to expiration, rate-limiting, or billing issues. With the gateway, configuration changes from multiple keys to a single endpoint:
base_url: https://x402.clawy.pro/v1/llm
You manage one balance and use one endpoint. If one provider goes down, the smart router automatically falls back to another.
Pricing
Most API calls cost fractions of a cent. LLM calls are per-token at actual provider cost plus 20% markup. A $1 top-up is sufficient for testing. Specific costs include:
- Brave Search: $0.006 per call
- Google Maps: $0.0036 per call
- Flight Search: $0.005 per call
- Hotel Search: $0.003 per call
- ElevenLabs TTS: $0.015 per call
- LLM (auto-routed): per-token + 30% markup
📖 Read the full source: r/clawdbot
👀 See Also
Custom status line for Claude Code shows context usage, rate limits, and token counts at a glance
A custom script adds a persistent status line to Claude Code, displaying context %, 5-hour rate limit %, KV cache reads, cumulative input/output tokens, model name, and working directory — color-coded for dark terminals.
Omnicoder-9B Performance Review: Speed vs. Tool Calling Issues
Omnicoder-9B, a coding-focused model fine-tuned on Qwen3.5 9B with outputs from Opus 4.6, GPT 5.4, GPT 5.3 Codex and Gemini 3.1 Pro, shows strong performance on mid-tier hardware but has tool calling issues in IDEs.
PromoClock: Timezone Tracker for Claude's 2x Off-Peak Hours Built with Claude 4.6
A developer built PromoClock.co, a free tool that automatically converts Claude's "5-11am PT / 12-6pm GMT" 2x off-peak promo hours to local time, using Claude 4.6 to handle timezone logic, Next.js 15 setup, and UI design.
KV Cache Reuse for Long Conversations on Apple Silicon Delivers 200x Speedup
A developer implemented session-based KV cache reuse for local LLM inference using Apple's MLX framework, achieving a 200x improvement in time-to-first-token at 100K context length. The approach keeps the KV cache in memory across conversation turns, processing only new tokens.