Common questions
What Buckle does, and what it is allowed to touch.
What is Buckle?
An agent that does the chores people forget. When your docs, dependencies, cloud config, monitoring or SEO drift, Buckle notices and creates the pull request that fixes it.
What does Buckle keep up to date?
Five areas: docs that no longer match the product, dependencies and SDK versions, cloud config, problems your monitoring picks up, and the site staying indexed and findable.
Does Buckle change anything without me?
Its fixes arrive as pull requests for you to review. For everything else an agent does, you set the rule: allow, hold for human approval, or block.
Where do I work with Buckle?
On the web, in the terminal, or in Slack, with the same permissions and audit trail everywhere.
How does Buckle keep API keys away from agents?
Agents never hold keys. Each agent runs in an isolated sandbox, and the gateway attaches a scoped credential to each request, so a key is never in an environment variable, a prompt or a log.
What can I enforce?
Block specific endpoints, rate-limit per agent, and require human approval for sensitive operations. Rules are enforced at the network layer, outside the agent and the model.
Is Buckle an MCP gateway?
No, it covers more. Buckle enforces at the network layer, so the same rules and audit log apply to MCP tool calls, CLI commands, curl, and HTTP requests from code the agent writes.
Can I self-host Buckle?
On the Enterprise plan, yes: the full platform runs in your own cloud, VPC, or on-prem. Talk to us to scope it.
How long does setup take?
A few minutes. Start free with $5 in model credits and 500 integration calls a month, no credit card required.