Featherless AI Provider
기준일: 2026-07-26
난이도: 중급
공식 기준: Featherless AI
개요
이 페이지는 OpenClaw Featherless AI provider의 인증, 모델 ref, 온보딩 플래그, 설정 키를 공식 문서 기준으로 정리합니다.
공식 요약: Featherless AI setup, model selection, and tool calling
model ref는 보통 provider/model 형식입니다. API key·endpoint·model id는 아래 원문 값을 그대로 쓰세요. 임의로 키나 엔드포인트를 만들지 마세요.
빠른 참조
| Property | Value |
|---|---|
| Provider id | featherless |
| Package | @openclaw/featherless-provider |
| Auth env var | FEATHERLESS_API_KEY |
| Onboarding flag | --auth-choice featherless-api-key |
| Direct CLI flag | --featherless-api-key <key> |
| API | OpenAI-compatible (openai-completions) |
| Base URL | https://api.featherless.ai/v1 |
| Default model | featherless/Qwen/Qwen3-32B |
공식 문서 기반 상세
아래는 공식 providers/featherless 문서를 Mintlify 컴포넌트만 정리하고 공통 제목을 한국어로 맞춘 내용입니다. 설정 키, env, model ref, CLI 플래그는 원문 그대로 유지합니다.
Featherless AI serves open models through an OpenAI-compatible API. OpenClaw installs Featherless as an official external provider plugin and keeps the built-in catalog small while accepting exact model ids from Featherless at runtime.
| Property | Value |
|---|---|
| Provider id | featherless |
| Package | @openclaw/featherless-provider |
| Auth env var | FEATHERLESS_API_KEY |
| Onboarding flag | --auth-choice featherless-api-key |
| Direct CLI flag | --featherless-api-key <key> |
| API | OpenAI-compatible (openai-completions) |
| Base URL | https://api.featherless.ai/v1 |
| Default model | featherless/Qwen/Qwen3-32B |
설정
Install the plugin and restart the Gateway:
openclaw plugins install @openclaw/featherless-provider
openclaw gateway restart
Run onboarding:
openclaw onboard --auth-choice featherless-api-key
For non-interactive setup:
openclaw onboard --non-interactive \
--mode local \
--auth-choice featherless-api-key \
--featherless-api-key "$FEATHERLESS_API_KEY"
Or expose the key to the Gateway process:
export FEATHERLESS_API_KEY="<your-featherless-api-key>" # pragma: allowlist secret
Verify the provider:
openclaw models list --provider featherless
기본 모델
The plugin uses Qwen/Qwen3-32B as the setup default because Featherless
documents native tool calling for the Qwen 3 family. OpenClaw configures its
32,768-token context window, a conservative 4,096-token output limit, and
Qwen chat-template thinking controls.
The catalog cost fields are zero because Featherless supports multiple billing modes and OpenClaw does not embed account-specific plan or request-pricing rates.
Other Featherless models
Use the exact Featherless model id after the featherless/ provider prefix:
{
agents: {
defaults: {
model: {
primary: "featherless/moonshotai/Kimi-K2-Instruct",
},
},
},
}
OpenClaw deliberately does not copy Featherless's full public model index into the picker. The index is large and does not expose enough structured capability metadata to classify every text, vision, embedding, and reasoning model safely. Unknown ids therefore resolve with conservative text-only, non-reasoning defaults: a 4,096-token context window and 1,024-token output limit.
Add an explicit provider model entry when a model needs different metadata:
{
models: {
mode: "merge",
providers: {
featherless: {
baseUrl: "https://api.featherless.ai/v1",
apiKey: "${FEATHERLESS_API_KEY}",
api: "openai-completions",
models: [
{
id: "google/gemma-3-27b-it",
name: "Gemma 3 27B",
input: ["text", "image"],
reasoning: false,
contextWindow: 32768,
maxTokens: 4096,
},
],
},
},
},
}
Check Featherless's model catalog for current model availability and capability tags before adding custom metadata.
문제 해결
401or403: confirmFEATHERLESS_API_KEYis visible to the Gateway process, or run onboarding again.- Unknown model: use the exact case-sensitive id from Featherless after the
featherless/prefix. - Tool calls returned as text: choose a model family Featherless documents for native function calling, such as Qwen 3.
- Managed Gateway cannot see the key: put it in
~/.openclaw/.envor another environment source loaded by the service, then restart the Gateway.
관련 문서
검증 체크리스트
-
openclaw models list --provider featherless로 모델이 보이는지 확인 - 기본 model alias를
agents.defaults.model.primary에 설정했는지 확인 - API key / OAuth / 로컬 런타임 인증 경로를 공식 문서와 대조했는지 확인
- failover 시 데이터가 다른 provider로 이동할 수 있는지 검토