Integrations
Put Bytefuse in your stack
Beyond the per-tool endpoints, Bytefuse gives you the platform pieces to run it in production — keys you can scope and budget, notifications for async work, an MCP server for AI agents, and predictable rate limits.
Integration surfaces
Four surfaces cover most integration needs. Each has its own guide.
API keysIssue scoped dt_live_ keys with per-key monthly credit budgets, and rotate or revoke them from the dashboard.Guide coming below
WebhooksGet notified when long-running work finishes, with signed, verifiable delivery payloads.Guide coming below
MCP serverExpose Bytefuse tools to AI agents over the Model Context Protocol, authenticated with your key.Guide coming below
Rate limitsUnderstand per-tier and anonymous limits, the 429 response, and the Retry-After header.Guide coming below
API keys & scopes
Every integration authenticates with a self-serve API key (prefixed dt_live_) sent in the X-API-Key header — see Authentication for the full header chain. Two controls make keys safe to hand to a single service:
- Scopes — restrict a key to specific operations; an out-of-scope call returns
403. - Per-key budgets — cap the credits a single key can spend per month; exceeding it returns
402, checked before any work so a blocked call costs nothing.
Where to start
New here? Read the Quickstart to make your first call, then come back to wire in keys, webhooks, or MCP. The Credits & billing page explains the metering guarantees that every integration inherits.
More guides landing here
Detailed pages for API keys, webhooks, the MCP server and rate limits are being published — they’ll appear in the sidebar as they go live.