Compatible (BYOK)

Use Anthropic SDK with GlideflowAI.

The Anthropic client library through GlideflowAI's compatible Messages endpoint. Connect it through GlideflowAI's Anthropic-compatible API with a key you control.

Get a key

What this connection is for

The Anthropic SDK is the direct client library for applications written around the Messages API shape. It is for teams whose application code already creates message requests, handles content blocks, and manages model selection through the Anthropic client interface. Keeping that interface can be more useful than converting working application code to a different SDK solely to change an endpoint.

Choose this route when the surrounding application is genuinely built around Messages requests and you can test compatible behavior in your own workload. It is not a blanket adapter for every Anthropic feature or hosted service. Start with a plain text request, inspect the returned content structure, and only then introduce advanced message patterns, tool calls, or project-specific middleware.

The client accepts a baseURL override. Set it to GlideflowAI's Anthropic-compatible host without /v1, store the key in the server environment, and use a catalog model ID in a bounded messages.create request. Keep the endpoint setting alongside other deployment configuration so staging and production do not silently diverge. Anthropic SDK is an independent project; this is a user-managed connection, not an endorsement or partnership.

Why pair it with GlideflowAI

The Anthropic SDK lets a Messages-based application preserve its familiar request shape while pointing at GlideflowAI's compatible host.

This is useful when Claude Code and an application service should share an endpoint convention without putting an Anthropic-specific credential into each environment.

Setup

Use a new API key for the tool, select a model from the catalog, and begin with a small task. Do not put a key in a repository, screenshot, or shared configuration file.

1
Store the gateway key as a secret
Use an environment variable or your platform's secret store; do not include it in a client-side bundle.
```
GLIDEFLOW_API_KEY=sk-your-key
```

Create an Anthropic SDK client

Pass the host without /v1 to baseURL, then make a bounded Messages request.

import Anthropic from "@anthropic-ai/sdk";

const client = new Anthropic({
  apiKey: process.env.GLIDEFLOW_API_KEY,
  baseURL: "https://api.glideflowai.com"
});

const message = await client.messages.create({
  model: "glm-5.2", max_tokens: 512,
  messages: [{ role: "user", content: "Say OK" }]
});

Need the endpoint basics? Read authentication, browse the model catalog, or compare pricing.

Frequently asked questions

Why must the Anthropic SDK baseURL omit /v1?

GlideflowAI's Anthropic-compatible base URL is https://api.glideflowai.com; appending /v1 here would not match the documented client configuration.

Which key option should I pass to the client?

Pass your GlideflowAI key as apiKey from a protected environment variable; the client sends it through its normal compatible authentication path.

Should I begin with tools or a plain message?

Begin with a small plain messages.create request so you can distinguish connection behavior from tool-schema or application middleware issues.

Is this an official integration?

No. The connection is configured by you using a compatible API and does not imply sponsorship, endorsement, or a partnership.

Ready to connect Anthropic SDK?

Create a key, use the setup above, and verify the connection on a small task before you scale it up.