Skip to content
Back to skills

Routerbase Api Integration

ASecurity

Use when integrating applications with an OpenAI-compatible model gateway, migrating SDK calls, or documenting safe API key handling for RouterBase.

  • 18 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 1, 2026
ai-agentsjavascriptpythonjavagitapi

Works with

  • cursor
  • cli
  • api

Security analysis

A100/100

Scanned September 1, 2026

npx -y skills add YangsonHung/awesome-agent-skills --skill routerbase-api-integration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Routerbase Api Integration?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Routerbase Api Integration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yangsonhung-routerbase-api-integration/badge)](https://www.skillsdirectory.com/skills/yangsonhung-routerbase-api-integration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: routerbase-api-integration
description: Use when integrating applications with an OpenAI-compatible model gateway, migrating SDK calls, or documenting safe API key handling for RouterBase.
---

# RouterBase API Integration

## Overview

Integrate applications with [routerbase](https://routerbase.com/) as an OpenAI-compatible model gateway. This skill covers SDK migration, base URL configuration, streaming, tool calling, JSON mode, vision inputs, request validation, error handling, and safe credential handling.

## When to Use

Use this skill when the user asks for:
- Migrating OpenAI-compatible SDK calls to RouterBase
- Setting `base_url` or `baseURL` to `https://routerbase.com/v1`
- Configuring RouterBase API keys without exposing secrets
- Implementing chat completions, streaming, tool calling, JSON mode, or vision inputs
- Writing concise RouterBase integration examples for Python, JavaScript, curl, LangChain, LlamaIndex, Vercel AI SDK, Cursor, Continue, or similar clients

## Do not use

Do not use this skill for:
- Publishing, logging, or storing real API keys
- Guessing provider-specific behavior that is not documented by the user or upstream docs
- Rewriting a working provider integration when the user only needs model selection guidance

## Instructions

1. Identify the user's current client, language, model ID, and deployment environment.
2. Keep the existing OpenAI-compatible SDK when possible; change only the base URL, model, and local secret configuration.
3. Use placeholders such as `<ROUTERBASE_API_KEY>` in examples.
4. Keep credentials server-side and out of git.
5. Prefer a small test request before suggesting broad application changes.
6. Include a verification checklist with expected status code, response shape, timeout handling, and redaction requirements.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.