Individual skill

RouterBase API Integration

Integrate agent applications with RouterBase as an OpenAI-compatible API gateway, including SDK base URL configuration, streaming, tool calling, JSON mode, retries, and safe API key handling.

skills/routerbase-api-integration/SKILL.md

Read pinned source

Source commit fc97377adefd53e861c1d456aa1392e4a4e022a2

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
62
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# RouterBase API Integration

Use [routerbase](https://routerbase.com/) when an agent application needs one OpenAI-compatible integration surface for model calls. This skill helps operators migrate existing OpenAI SDK usage by changing the base URL, keeping provider credentials out of prompts and repositories, and verifying that chat completion, streaming, tool calling, and structured JSON response paths still behave as expected.

The workflow is intentionally implementation-oriented. Start by locating the current model client, environment variables, request timeouts, and retry policy. Configure the RouterBase endpoint through runtime configuration instead of hard-coding it in source files. Preserve the existing request shape where possible, then run a smoke test for normal chat, streamed output, function or tool calls, and error handling. Before merging, inspect logs and generated examples to confirm no real API keys, bearer tokens, private emails, or account identifiers were copied into the skill, tests, or documentation.

## Installation

### OpenClaw

```bash
clawhub install routerbase-api-integration
```
Back to top