Free Claude Code
Connects agents to a self-hosted gateway that exposes OpenAI Responses and Anthropic Messages across configured upstream providers.
What it provides
Connect an HTTPS API gateway with an optional scoped token. The installed client supports discovery and bounded HTTP calls.
Connection requirements
Run `fcc-server` outside the bot and publish its proxy API through HTTPS. Set `PROXY_AUTH_ENABLED=true` and a non-empty `ANTHROPIC_AUTH_TOKEN`, then keep Bearer selected and paste that token below; this Responses connection sends it as an Authorization bearer credential. Connect the server origin, not a `/v1` suffix. FCC documents OpenAI Responses at `/v1/responses` and Anthropic Messages at `/v1/messages`, but not OpenAI Chat Completions, so use the Responses example below rather than `/v1/chat/completions`. Provider credentials, routing state, and any local model runtime stay on the FCC host. Upstream quotas and availability still apply; this connector does not supply or guarantee free tokens.
- Protocol
- OpenAI-compatible REST
- Endpoint
https://fcc.example.com- Authentication
- bearer
get /v1/models?view=responsespost /v1/responses {"model":"MODEL_ID","input":"Hello"}Where to add it
Open Dashboard Tools, select a running OpenClaw or Hermes instance, then use the card’s Install or Connect action. External services may require an HTTPS endpoint and credentials; the dashboard shows those fields before anything is saved.