Skip to main content

Use Zeldoc.ai with any AI tool

Zeldoc.ai isn't limited to a specific agent harness. As long as your tool or framework lets you configure a custom base URL and API key, you can use Zeldoc.ai.

Base URL​

All requests should be sent to:

https://api.zeldoc.ai/v1

Authentication​

Set your Zeldoc.ai API key as a bearer token or in the tool's API key field:

export ZELDOC_API_KEY=your-api-key

With the Zeldoc CLI, you save the key once with zeldoc auth login and set the variable from it instead: export ZELDOC_API_KEY="$(zeldoc auth token)".

Need an API key?

If you don't have one yet, see Generate an API key.

Supported API formats​

Zeldoc.ai supports the most common API formats, so you can connect it to tools and frameworks that expect any of the following:

  • OpenAI Chat Completions (/chat/completions)
  • OpenAI Responses (/responses)
  • Anthropic Messages (/messages)

This means most AI tools, frameworks, and libraries that let you point to a custom endpoint will work with Zeldoc.ai out of the box.

Anthropic-style clients want the base URL without /v1

Tools built on the Anthropic SDK — Claude Code among them — append /v1/messages to the base URL themselves. For those, set the base URL to https://api.zeldoc.ai instead of https://api.zeldoc.ai/v1. OpenAI-style clients append /chat/completions or /responses to a base URL that already includes /v1.

Quick test​

You can verify your connection with a simple request:

curl https://api.zeldoc.ai/v1/chat/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $ZELDOC_API_KEY" \
  -d '{
    "model": "zdev",
    "messages": [
      {"role": "user", "content": "Hello!"}
    ]
  }'
note

Don't see your tool listed in our guides? As long as it supports custom base URLs and one of the API formats above, you can connect it to Zeldoc.ai. See Supported Agent Harnesses for the tools we have step-by-step guides for, and check back as we add more.