Vendo Docs

Claude family of models. Vendo holds the upstream credential and bills per token (including cache reads / writes) through the proxy.

Drop-in Anthropic Messages API. Use the official Anthropic SDK with Vendo's proxy as the base URL — no Anthropic console signup, no key management. Prompt caching is fully tracked: cached reads and cache-creation tokens are metered as separate line items so you can see the savings.

Auth modes

Profile	Default	How it works
`vendo_managed_pool` (Vendo-managed pool)	Yes	Vendo holds the upstream credential and bills per call against the tenant's Vendo balance. No tenant signup with the provider required.

Environment variables

These are the env vars Vendo injects into your deployment at boot when this integration is bound. Source values are resolved by resolveConnectionEnvVars in packages/integrations/lib/ from the connection record (credential, metadata) and deployment context (proxy URL, Vendo-issued API key).

Variable	Profiles	Source	Secret
`ANTHROPIC_API_KEY`	all	Vendo-issued API key (`vendo_sk_*`)	Yes
`ANTHROPIC_BASE_URL`	all	Vendo proxy base URL (`https://<slug>-proxy.vendo.run/v1`)	No

Reading the credential at runtime

Vendo writes ANTHROPIC_API_KEY (and any companion vars above) into your deployment's environment at boot — the official Anthropic SDK auto-discovers it, so most code just instantiates the client with no extra wiring. vendo.token(slug) is the resolution-chain-aware alternative that reads the same value in Vendo mode and falls back to whatever you set in OSS mode; use whichever fits your style. See Two modes for the full resolution chain.

Proxy endpoint

Calls to Anthropic are brokered through Vendo's proxy at:

https://anthropic-proxy.vendo.run

Point the official Anthropic SDK at this base URL; Vendo authenticates, meters per call, and forwards upstream. Your code never sees the upstream credential.

Quickstart

import vendo

# Native Claude API access through Vendo. Same Anthropic SDK, billed via your Vendo balance.
token = vendo.token("anthropic")

# Use `token` wherever you would have used the provider's API key —
# pass it to the official SDK or set it as the env var the SDK reads.
print(token)

import { Vendo } from "@vendodev/sdk";

const vendo = new Vendo();
// Native Claude API access through Vendo. Same Anthropic SDK, billed via your Vendo balance.
const anthropicToken = await vendo.token("anthropic");

// Use `anthropicToken` wherever you would have used the provider's API
// key — pass it to the official SDK or read it as the env var the SDK expects.
console.log(anthropicToken);

import VendoSDK

let vendo = Vendo()
// Native Claude API access through Vendo. Same Anthropic SDK, billed via your Vendo balance.
let token = try await vendo.token("anthropic")

// Use `token` wherever you would have used the provider's API key.
print(token)

Learn more

Concepts: connections & integrations — how connections, bindings, and credentials fit together.
Build a tool: SDK — full vendo.token and vendo.data.execute semantics.
Anthropic API docs