UNIFIED AI MODEL ACCESS & MANAGEMENT

Your next ideabelongs here.

Everyday coding, content creation, or application development can all start here. Access AI models through Dev.dog and focus on what you really want to accomplish.

OpenAI, Anthropic, and Gemini API protocols.

dev.dog

MORE MODELS, MORE CHOICE

Find the right model for your work.

From coding to document processing, compare capabilities and choose for your needs and budget.

Focus to pause. Use arrow keys to browse; Space toggles automatic scrolling.

Check the catalog and selected group for specific versions, supported features, and prices.

Browse models & group pricing

BUILT FOR EVERYDAY USE

From connecting to working with AI.

Keep keys, usage, and spending clear as your projects grow.

Keep your familiar workflow

Configure the Dev.dog endpoint, key, and model ID in a tool that supports custom APIs. Explore more models with the tools you already use.

Manage each project separately

Create separate keys for everyday tools, testing, and production. Rotate or revoke one without affecting your other projects.

Understand each request’s cost

View requests, token usage, and charges in the console. Compare results and spending to find an approach that works for you.

GET CONNECTED

Make your first request work.

Configure your client’s connection settings, or start with the code example to build your own application.

  1. 1

    Choose a model and group

    Sign in, compare capabilities and group prices, and choose a suitable option. Confirm that your account has available credit.

  2. 2

    Create a project key

    Create an API key for your chosen group. Enter it in your client, or store it in a server environment variable for your application.

  3. 3

    Configure and verify

    Set the endpoint and exact model ID from the guide. Send a short request, confirm the response, and check its usage and charge.

OpenAI-compatible example
import os
from openai import OpenAI

client = OpenAI(
    api_key=os.environ["DEV_DOG_KEY"],
    base_url="https://dev.dog/v1",
)

response = client.chat.completions.create(
    model="YOUR_MODEL_ID",
    messages=[{"role": "user",
               "content": "Hello!"}],
)
print(response.choices[0].message.content)
SDK setuppip install openai

Set DEV_DOG_KEY to your key and YOUR_MODEL_ID to a model ID supported by your group.

Different tools may expect different endpoint formats. View setup details

BEFORE YOU CONNECT

Frequently asked questions

About tool compatibility, model groups, and usage charges.

Need setup or troubleshooting details?

Read the connection guide
Can I connect my existing coding tools and clients?

If your tool supports a custom endpoint, API key, and model name, follow the Dev.dog guide and choose the matching OpenAI, Anthropic, or Gemini protocol. Streaming, tool calls, and image input depend on the model and channel. Verify the features you need before making it part of your daily workflow.

Which endpoint should I use?

For the OpenAI SDK, use https://dev.dog/v1. For Anthropic or Gemini clients, use the corresponding address in the guide. Some tools add /v1 automatically, so check their Base URL requirements to avoid repeating the version prefix.

How do groups for the same model differ?

Groups represent different access channels, with potentially different prices, features, and limits. Compare them in the catalog, then create a key for your chosen group. Test your actual tasks and review their costs before choosing a group for ongoing use.

How are requests billed, and can I see the charges?

The console shows request history and charges. Text models are usually billed by tokens, the units of text a model processes. Input, output, and cached tokens may have different prices. See the selected model and group for exact rates and other billing methods. Start with a short request to check actual usage.

Give your next idea a start.

Choose a model, create a key, and bring AI into your tools and projects.

Get started

API connection guide

Choose the configuration for your client or protocol. For an SDK, use the Base URL. For a raw HTTP request, append the request path to https://dev.dog without repeating the version prefix.

Client / protocolSDK base URLRequest path
OpenAIhttps://dev.dog/v1/v1/chat/completions
/v1/responses
Anthropichttps://dev.dog/v1/messages
Geminihttps://dev.dog/v1beta/models/…

Some clients add the version prefix automatically. Follow their instructions to avoid adding /v1 twice. Gemini clients usually set the Base URL in HTTP options; the operation path also needs the model ID.

Authentication

OpenAI-compatible requests use Authorization: Bearer YOUR_API_KEY. Anthropic Messages uses x-api-key: YOUR_API_KEY and the anthropic-version header required by your client. Use a Dev.dog API key in both cases.

Copy the exact model ID from the catalog and confirm that your group supports the model and the features you need.

Client compatibility

Find the custom API or endpoint setting in your tool and enter the Dev.dog address, key, and model ID from the guide. OpenAI-compatible clients usually use https://dev.dog/v1; refer to the matching protocol instructions for Anthropic and Gemini.

Some tools require specific interfaces or model features. Test first before moving your full workflow. ChatGPT and Claude website subscriptions are separate from Dev.dog API credit and cannot be used interchangeably.

Troubleshooting requests

Use the status code to narrow down the issue: 401 means checking the key and authentication header; 403, permissions and group access; 404, endpoint and model ID; 429, rate limits. Reduce concurrency and allow time between retries where needed.

Also check your credit and request history. For 5xx errors or timeouts, retry a short request later. Keep the request time, model, status code, and request ID if returned. Do not include the full key when sharing diagnostic information.

Keys and request data

Store keys in server environment variables or secure local storage, not public repositories or browser code. Use separate keys for projects, and revoke and replace any key you believe has been exposed.

Requests pass through Dev.dog to the selected upstream provider. Before sending sensitive material, review both services’ data policies and send only what the task requires.

View code examples