Copy an OpenAI-compatible key, paste it into your app, and start testing GPT, Claude, Gemini, DeepSeek, Kimi, embeddings, image and audio models.
No credit card. No registration. Star the GitHub repo for the public key table and follow @getkeyway on X for fresh key drops, model alerts and uptime notes.
OpenAI-compatible project · 3 highlighted model families · 90+ catalog routes · public GitHub updates
Model Coverage
Use this catalog as a developer map for model families, providers and route coverage. The public project stays focused on access, examples and update signals.
Live model catalog is loaded from the production routing inventory.
| Model | Provider | Cloud | Status |
|---|
No models match this filter.
Loading live model catalog...
Coverage only. For keys and examples, open the GitHub repo or follow @getkeyway for drops.
Why follow
The landing page should send builders to GitHub and X because that is where the useful updates happen.
The repo is the visible demand signal. Stars help decide which model families, examples and public key batches get published next.
@getkeyway is the fastest channel for new key batches, model alerts, uptime notes and short build updates.
Use the same OpenAI SDK pattern in Python, Node, cURL and common tools. Copy a key, swap the base URL and test.
Follow changes for GPT, Claude, Gemini, DeepSeek, Kimi, embeddings, image and audio routes without reading a storefront.
Verify whether a key still works before wiring it into your app, then jump into the docs when you need integration details.
The GitHub repo keeps the README, examples, roadmap and issues in the same place so developers can inspect direction quickly.
Quick Start
Replace base_url. Keep the rest of your code identical.
from openai import OpenAI
client = OpenAI(
base_url="https://aiapiv2.pekpik.com/v1",
api_key="sk-...",
)
resp = client.chat.completions.create(
model="claude-opus-4-7", # or gpt-5.4, deepseek-chat, gemini-2.5-pro
messages=[{"role": "user", "content": "Hello"}],
)
print(resp.choices[0].message.content)Explore the build
These pages help developers understand model coverage, OpenAI-compatible migration and routing behaviour before jumping into the GitHub repo.
Developer pages for understanding which model families the project can target.
Provider-level notes for developers mapping OpenAI-compatible requests to model families.
Integration, routing and reliability topics for builders using OpenAI-compatible clients.
Comparison pages for developers evaluating model access patterns and routing tradeoffs.
FAQ
Open the GitHub repo and copy a key from the public table. Follow @getkeyway on X for fresh key drops and availability notes.
No. Requests pass through without content logging. We retain only aggregate routing metrics such as model, latency and health signals.
Stars are the public signal that more shared capacity, examples, model shelves and key batches are worth publishing.
Public keys are shared and temporary, so limits vary by batch and usage. If one key is exhausted, check the repo or X for a fresh drop.
Treat public keys as a testing and learning resource. For production workloads, use your own account controls and stable operational limits.
The primary interface is OpenAI-compatible /v1/chat/completions. Provider-native endpoints can be evaluated when a workflow needs them.
Each model can be backed by a pool of upstream keys with continuous health checks. Bad keys are quarantined and traffic shifts to healthy ones automatically.
Follow the build
GitHub is where the public key table, examples and roadmap live. X is where @getkeyway posts fresh key drops, new model alerts and uptime notes first.