Authentication

Every request needs an API key. A single Fenno key works with all three protocols — use the header that matches the endpoint you call.

Auth headers

Authorization: Bearer $FENNO_API_KEY

x-api-key: $FENNO_API_KEY
anthropic-version: 2023-06-01

x-goog-api-key: $FENNO_API_KEY

SDK setup

import os
from anthropic import Anthropic
 
client = Anthropic(
    base_url="https://api.fenno.ai",
    api_key=os.environ["FENNO_API_KEY"],
)

import { GoogleGenAI } from '@google/genai'
 
const ai = new GoogleGenAI({
  apiKey: process.env.FENNO_API_KEY,
  httpOptions: { baseUrl: 'https://api.fenno.ai' }
})

Keys and permissions

• Use separate keys for environments or applications where your account allows it.
• Access and limits follow the current account and key configuration. After a change, verify the actual request instead of assuming an immediate propagation time.
• If a key leaks, revoke or rotate it through the available console controls and update dependent applications. Do not reuse the exposed value.

Usage constraints

Usage and quota

Use the usage, balance and limit information available in your account. A response’s usage can help application statistics, but its absence or an HTTP failure alone does not establish zero cost. See usage and cost management.

When quota is exhausted, requests return 402 or 429; see Errors & retries.