logfare.ai valid

API Documentation

Point any OpenAI-compatible client at `https://logfare.ai/v1` and use your Logfare API key. Anthropic Messages and the OpenAI Responses API also work. Model IDs change often, so check [/models](/models) for what's available right now.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T18:59:02.386Z. Cached copy · Source on logfare.ai

# API Documentation

OpenAI-compatible inference with one API key.

> Point any OpenAI-compatible client at `https://logfare.ai/v1` and use your Logfare API key. Anthropic Messages and the OpenAI Responses API also work. Model IDs change often, so check [/models](/models) for what's available right now.

## Authentication

Model requests need your API key. [Register](/register) for a free account and copy the key from your dashboard. Your Discord account must stay in the Logfare server to keep access.

Send the key as a Bearer token. The `x-api-key` header also works, which is what Anthropic clients send.

```http
Authorization: Bearer YOUR_API_KEY
```

Building an app for other people? Use [App integrations](#app-integrations) so each user approves your app without sharing their key.

## Endpoints

All endpoints are under `https://logfare.ai/v1`.

| Method | Endpoint | Description |
| --- | --- | --- |
| **POST** | `/v1/chat/completions` | Chat completions (streaming supported) |
| **POST** | `/v1/responses` | OpenAI Responses API |
| **POST** | `/v1/messages` | Anthropic Messages API |
| **POST** | `/v1/completions` | Legacy text completions |
| **POST** | `/v1/images/generations` | Image generation |
| **POST** | `/v1/images/edits` | Image editing |
| **POST** | `/v1/audio/speech` | Text to speech |
| **POST** | `/v1/audio/transcriptions` | Speech to text |
| **POST** | `/v1/embeddings` | Text embeddings |
| **POST** | `/v1/videos/generations` | Video generation |
| **POST** | `/v1/decisions` | Decision models |
| **GET** | `/v1/models` | Available models (no key needed) |
| **GET** | `/v1/status` | Service and model health (no key needed) |

## Models & access

**GET** `/v1/models`

Lists the models you can use, in the OpenAI format. No key is needed; with a key, the list also includes private models your key can reach. Each entry adds these Logfare fields:

| Field | Description |
| --- | --- |
| `endpoints` | APIs the model serves, such as `chat/completions` or `images/generations` |
| `aliases` | Other names that route to the same model |
| `requires_training_optin` | `true` for premium models (see below) |
| `premium_unlocked` | Whether the key you sent can use the model right now |
| `chat_capabilities` | Input types (`input_modalities`), `reasoning` controls, and `tools` support for chat models |
| `context_length`, `max_output_tokens` | Input and output limits Logfare enforces for the model, when set. Larger inputs are rejected with `413`; larger `max_tokens` values are lowered. |
| `upstream_metadata` | Published specs such as context length, input types and supported parameters, when available. They are a general reference, so check the limits above first. |

**Premium models** are free too, but require opting in to model training at [/consent](/consent). Until you opt in, requests to them return `403` with code `training_optin_required`. Every other model works without opting in.

```bash
curl https://logfare.ai/v1/models
```
…

Machine-readable: GET /v1/resolve?q=logfare.ai · GET /v1/domain/logfare.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for logfare.ai:
1. POST https://agentwebmap.com/v1/sites/logfare.ai/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://logfare.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/logfare.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/logfare.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.