Up42 Rate Limits
UP42 does not publish fixed numeric per-endpoint rate limits for the REST API. The practical governor on usage is the prepaid credit balance and, for enterprise accounts, budgets that cap credit spend rather than a per-minute request cap. Access tokens are short-lived (about 5 minutes), so clients must refresh tokens frequently and cache them for their lifetime. Long-running operations (tasking acquisitions, large orders, processing jobs) are asynchronous - clients poll order/job status or subscribe to webhooks rather than holding open a request. Callers should implement backoff on 429 responses.
Up42 Rate Limits is the machine-readable rate-limit profile for UP42 on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring requests, credits, and seconds.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Geospatial, Earth Observation, Satellite Imagery, Rate Limiting, and Quotas.
Limits
Policies
Sources
- https://docs.up42.com/developers/api
- https://docs.up42.com/getting-started/credits/pricing
- https://up42.com/pricing
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/up42-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.