Multi-provider routing
- Persona decides which model fits
- Calls this provider when its strengths apply
- Falls back to alternatives on rate-limits
13 tools available
OpenRouter is a platform that provides a unified API for accessing various large language models (LLMs) from different providers, allowing developers to integrate multiple AI models seamlessly.
Connect Openrouter to Definable to route to the best model per task, mix providers in one workflow, fall back on rate-limits. Personas call Openrouter's 13 tools directly from chat or scheduled flows. Add it to your persona's available models and route requests to it where it fits best.
Every Openrouter action below is a callable tool any Definable persona can invoke.
Tool to generate a chat-style completion. Use after assembling messages and selecting a model. Supports streaming and function calls. Response format varies across models; use explicit prompt instructions to standardize output. Provider-level rate limits and moderation policies differ per model.
Tool to create a Coinbase charge for crypto payment to add credits to your OpenRouter account. Use when you need to purchase credits using cryptocurrency. Returns calldata needed to fulfill the transaction on the specified blockchain.
Tool to create a message using Anthropic Messages API format via OpenRouter. Use when you need Claude-compatible chat completion with support for text, images, PDFs, tools, and extended thinking.
Tool to get the current API credit balance for the authenticated user. Use before large or batch jobs to verify sufficient balance. A successful response may return total_credits=0, which confirms authentication but will cause all paid model generations to fail. Avoid polling this endpoint; call only as needed.
Tool to get information about the currently authenticated API key. Use to check usage limits, spending, and key metadata.
Tool to retrieve a generation result by its unique ID. Use after a generation completes to fetch metadata like token counts, cost, and latency.
Tool to get the total count of available models on OpenRouter. Use when you need to know how many models are available without fetching the full list.
Tool to list available models via OpenRouter API. Use after confirming authentication to fetch the model catalog. Use exact model IDs returned here in OPENROUTER_CREATE_CHAT_COMPLETION or OPENROUTER_CREATE_COMPLETION calls — hard-coded IDs may break when the catalog changes. Use exact author and slug values from this response as inputs to OPENROUTER_LIST_MODEL_ENDPOINTS. Models have varying capabilities (e.g., tools, reasoning); verify individual model capabilities before downstream use. Pricing and latency metadata may be null or approximate — handle missing values in routing logic.
Tool to list all available embeddings models via OpenRouter API. Returns a list of embeddings models with their properties including architecture, pricing, and capabilities.
Tool to list endpoints for a specific model. Use after specifying model author and slug to get endpoint details including pricing, context length, and supported parameters. Some metadata fields (e.g., latency, pricing) may be null or approximate; handle missing values in routing logic.
Tool to list all AI model providers available through the OpenRouter API. Use after authentication to retrieve available provider options for routing configuration. Providers differ in latency, context window sizes, and rate limits — switching providers affects these constraints. Newly added providers may not appear immediately due to catalog propagation delays.
Tool to list models filtered by user provider preferences, privacy settings, and guardrails. Use after authenticating to get models tailored to the user's configuration.
Tool to preview the impact of Zero Data Retention (ZDR) on the available endpoints. Use to see which model endpoints remain accessible when ZDR is enabled.
Anything Openrouter exposes through its API. Common artificial intelligence workflows on Definable include route to the best model per task, mix providers in one workflow, fall back on rate-limits. Personas can call any of the 13 Openrouter tools directly, then chain the result into another integration without you writing code.
Openrouter uses API_KEY on Definable. You connect once from the integrations page, scoped to the permissions you choose, and from then on any persona that has the integration enabled can act on your behalf. Tokens are encrypted at rest and rotated automatically.
Yes — every Definable plan, including Starter, includes access to all 13 Openrouter tools. You only need a separate Openrouter subscription if Openrouter itself charges per seat or per API call.
Every call from a persona to Openrouter is logged with the user, persona, prompt, and response. Tokens never leave Definable's secrets vault, scopes are configurable per persona, and you can revoke access at any time from the integration page.
Sign up for Definable, open the integrations page, find Openrouter, and connect via OAuth or API key. You can immediately attach Openrouter to any persona and start running workflows. The free Starter plan includes 5,000 credits/month.
Definable exposes all 13 Openrouter actions as callable tools — including `Create Chat Completion`, `Create Coinbase Charge`, `Create Message (Anthropic Format)`, plus 10 more. Each tool gets a typed parameter schema so personas know exactly how to call it.
Wire it up in minutes. No coding required.