Skip to content

chutes.md

Latest commit

 

History

History
59 lines (39 loc) · 2.04 KB

chutes.md

File metadata and controls

59 lines (39 loc) · 2.04 KB
Raw
summary Chutes provider: API key setup, subscription usage, and quota windows.
read_when
Configuring Chutes usage
Debugging Chutes subscription or quota requests

Chutes Provider

CodexBar reads subscription and quota usage from Chutes' management API with a manually configured API key.

Service context

Chutes' terms are governed by the laws of Nevis, Saint Kitts and Nevis, and its decentralized backend uses independent miners. Its pricing surface has changed over time and should be treated as historically unstable; check the current pricing page before relying on a plan or rate.

Authentication

Create a Chutes API key using the official authentication guide, then add it in CodexBar Settings → Providers → Chutes.

You can also set the environment variable:

export CHUTES_API_KEY="cpk_..."

Or configure it through the CLI:

printf '%s' "$CHUTES_API_KEY" | codexbar config set-api-key --provider chutes --stdin

Data Source

CodexBar requests:

  • GET https://api.chutes.ai/users/me/subscription_usage
  • GET https://api.chutes.ai/users/me/quotas when subscription data does not contain every usage window
  • GET https://api.chutes.ai/users/me/quota_usage/{chute_id} for quota details when available

All requests use Authorization: Bearer cpk_.... Subscription usage is required; quota-detail requests are best-effort.

Display

The provider prefers the rolling four-hour window as the primary meter and monthly subscription usage as the secondary meter. Accounts without a subscription can still show available pay-as-you-go quota data.

CLI Usage

codexbar --provider chutes

Troubleshooting

  • Confirm the key can read https://api.chutes.ai/users/me/subscription_usage.
  • A 401 or 403 means Chutes rejected the key.
  • CHUTES_API_URL can override the management API base URL, but CodexBar accepts HTTPS endpoints only.