Endpoint
Authentication
Replace the Anthropic API key with your Chucky JWT token in thex-api-key header:
Creating Tokens
Tokens are created server-side with your HMAC secret:Supported Endpoints
Request Format
The request body follows the Anthropic Messages API format exactly:Response Format
Responses match the Anthropic API format:Streaming
Enable streaming by setting"stream": true:
Multi-Provider Support
The Channeling API supports multiple AI providers through model routing:Anthropic (Default)
OpenAI
Requires OpenAI API key configured in your project settings.
OpenRouter
Use theor: prefix for explicit routing, or any unknown model name:
Requires OpenRouter API key configured in your project settings.
Using with Anthropic SDKs
TypeScript/JavaScript
Python
Budget Enforcement
The Channeling API enforces budgets embedded in JWT tokens:- AI Budget: Limits total AI spend per user
- Compute Budget: Not applicable (no sandbox execution)
429 error:
Cost Tracking
Every request is tracked against the user’s budget. Costs are calculated based on:- Model used
- Input/output tokens
- Custom pricing (if configured)
Use Cases
Direct API Access
Use HTTP calls without the Chucky SDK:Existing Anthropic Integrations
Point existing Anthropic SDK code to Chucky by changing the base URL:Third-Party Tools
Any tool that supports custom Anthropic endpoints can use Channeling:- VS Code extensions
- CLI tools
- Automation platforms
Error Handling
Next Steps
Authentication
Create JWT tokens with budgets
Models & Providers
Configure multi-provider support
Billing
Understand costs and pricing
Dashboard
View usage and manage projects