DoltHub · Rate Limits

Dolthub Rate Limits

DoltHub does not publish explicit numeric rate limits for its v1alpha1 HTTP API. Read SQL queries run synchronously against hosted databases; write SQL queries, forks, and merges are asynchronous and execute as jobs/operations that are queued server-side, which naturally bounds concurrency rather than exposing a documented per-minute quota. Specific limits are not reconciled in this artifact.

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

It captures 3 rate-limit definitions, measuring requests, operations, and jobs.

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

Tagged areas include Database, SQL, Version Control, Git for Data, and MySQL.

3 Limits Throttle: 429
DatabaseSQLVersion ControlGit for DataMySQLRate LimitingQuotasThrottling

Limits

Read SQL Query account
requests
see provider documentation
Synchronous read queries; no documented numeric limit.
Write SQL Query account
operations
queued asynchronously
Executes as an async operation/job; poll until done rather than retrying tightly.
Jobs / Operations account
jobs
queued asynchronously
Write, fork, merge, import, and migrate run as queued jobs/operations.

Policies

Asynchronous Execution
Write, fork, and merge calls return an operation_name; poll the corresponding status endpoint until done is true.
Backoff Strategy
Clients should poll with reasonable intervals and implement exponential backoff with jitter, honoring Retry-After if returned.

Sources