Depot · Rate Limits

Depot Dev Rate Limits

Depot does not publish explicit numeric request-per-second rate limits for its Connect/gRPC API (api.depot.dev). In practice, account usage is governed by plan allotments and overage billing (Docker build minutes, GitHub Actions minutes, Depot CI minutes, and cache storage) rather than hard per-second request caps, with concurrency of in-flight builds bounded by plan and organization configuration. Standard gRPC/Connect error codes are returned on throttling or resource-exhaustion conditions.

Depot Dev Rate Limits is the machine-readable rate-limit profile for Depot on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring minutes, vcpu_seconds, storage_gb, and concurrent_builds.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled and grpcResourceExhausted.

Tagged areas include Container Builds, Docker, BuildKit, Remote Cache, and CI/CD.

5 Limits Throttle: 429
Container BuildsDockerBuildKitRemote CacheCI/CDGitHub ActionsRate LimitingQuotasThrottling

Limits

Docker Build Minutes organization
minutes
plan allotment then per-minute overage
500 (Developer) / 5,000 (Startup) included; $0.04/min thereafter.
GitHub Actions Minutes organization
minutes
plan allotment then per-minute overage
2,000 (Developer) / 20,000 (Startup) included; from $0.004/min thereafter.
Depot CI organization
vcpu_seconds
plan allotment then per-second overage
2,000 / 20,000 minutes included; $0.00005/sec/vCPU thereafter.
Cache Storage organization
storage_gb
plan allotment then per-GB overage; no hard cap
25 GB / 250 GB included; $0.20/GB/month thereafter, sampled hourly.
Build Concurrency organization
concurrent_builds
see provider documentation
Concurrent in-flight builds bounded by plan and organization configuration.

Policies

Usage-Based Governance
Usage is bounded by plan allotments and overage billing rather than fixed per-second request limits.
Backoff Strategy
Clients should implement exponential backoff with jitter on RESOURCE_EXHAUSTED / 429 responses and honor any Retry-After hint.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/depot-dev-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.