Sfcompute Rate Limits
SF Compute does not publish specific numeric request-rate limits for the api.sfcompute.com REST API. Practical constraints are economic rather than request-rate based: order placement is bounded by available account balance, by open market liquidity for the requested instance type, and by the quantity of capacity a buyer can clear. The market-quote endpoint allows long-running requests (the CLI uses a 600s client timeout). Specific per-account RPM/RPS values are not reconciled in this artifact.
Sfcompute Rate Limits is the machine-readable rate-limit profile for SF Compute on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring requests, seconds, orders, and nodes.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include GPU, Compute, Marketplace, H100, and Spot Pricing.
Limits
Policies
Sources
- https://docs.sfcompute.com/docs/using-the-api
- https://fogdocs.sfcompute.com/api-reference
- https://github.com/sfcompute/cli
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/sfcompute-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.