Skip to content

Products

AgentKitAuto

Run Agent Kits unattended in the cloud — on demand, on a schedule, or from a webhook.

AgentKitAuto (auto.agentkitproject.com) runs Agent Kits autonomously — with no human in the per-step loop. Use it for scheduled jobs, event-driven runs, and one-off background work.

What you need

  • Signed in to AgentKitProject.
  • An inference path configured — managed credits or your own Anthropic key (see Billing below).
  • At least one kit in your library to authorize and run (it doesn't need to be published).

Standing approvals

Auto gates every run behind a standing approval for a kit. The approval is where you set the safety envelope:

  • Tool allowlist — which tools the run may use (e.g. file tools, HTTP fetch).
  • Budget ceiling — a required maxBudgetCents; per-run budgets must stay within it.
  • Network policy — default deny_all, or an allowlist of egress hosts. HTTP egress is only permitted when the policy is an allowlist, http_fetch is in the approval's tool allowlist, and the host is on the list.

Triggers

  • On demand — start a run from the Auto section.
  • Scheduled — create a cron schedule with a timezone; the next run time is computed server-side.
  • Webhook — create an inbound webhook with a per-webhook secret (shown once); each fire is validated against the standing approval.

Runs execute in isolated, ephemeral workspaces. You can cancel an active run, and optionally receive results by email or signed webhook.

Billing

  • Managed credits — pay for compute: $0.01 per run + $0.01 per active minute, with a one-time 60 free active minutes for new accounts. Model tokens are billed at cost (no markup). No commitment.
  • Bring your own Anthropic key — connect your own key and pay Anthropic directly for tokens; the same $0.01/run + $0.01/active-minute compute fee applies. The key is encrypted at rest. You can set your inference-mode preference (auto / managed / BYO).

Common mistakes

  • Attempting a run without a standing approval.
  • Leaving the budget blank — it is required and enforced.
  • Assuming schedules or webhooks bypass the standing approval — they don't.

Self-hosting

AgentKitAuto can be self-hosted on Kubernetes today, with a Job-per-run worker. See Self-hosting on Kubernetes.