Skip to content

feat(providers): add CoralBricks - #502

Open
divyvasal wants to merge 1 commit into
charmbracelet:mainfrom
divyvasal:add-coralbricks-provider
Open

feat(providers): add CoralBricks#502
divyvasal wants to merge 1 commit into
charmbracelet:mainfrom
divyvasal:add-coralbricks-provider

Conversation

@divyvasal

Copy link
Copy Markdown

What

Adds CoralBricks as an inference provider — an OpenAI-compatible gateway serving open models with up to 1M context.

Models: GLM 5.2 (glm-5.2-fp4), Kimi K3 (kimi-k3), GPT-OSS 120B (gpt-oss-120b). Endpoint https://inference.coralbricks.ai/v1, key $CORALBRICKS_API_KEY, type openai-compat.

Notable: cost_per_1m_in_cached: 0 on every model — cached input tokens are free on the gateway.

Follows the existing pattern

  • internal/providers/configs/coralbricks.json (mirrors the other openai-compat configs)
  • //go:embed + coralBricksProvider() + providerRegistry entry in internal/providers/providers.go

Verified

  • go build ./... clean
  • go test ./internal/providers/ green
  • Confirmed the provider loads via GetAll() with 3 models, correct endpoint, and free cached-input pricing

Pricing source: https://www.coralbricks.ai/pricing. Reasoning is declared (can_reason: true); per-request effort levels are intentionally omitted for now.

🤖 Generated with Claude Code

CoralBricks is an OpenAI-compatible inference gateway for open models
(GLM 5.2, Kimi K3, GPT-OSS 120B) with up to 1M context and free cached
input (cost_per_1m_in_cached: 0). Follows the openai-compat config
pattern; loads via GetAll(), build + provider tests green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@divyvasal

Copy link
Copy Markdown
Author

Friendly ping @andreynering, this adds CoralBricks as an OpenAI-compat provider (config JSON + providers.go wiring, build + tests green, loads via GetAll()). Mergeable and ready when you have a moment. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant