Check your usage and limits
You are viewing in-progress documentation for v2. Switch to the stable version for the current production release.
Your account has usage quotas — ceilings on how many jobs you can run at once, how many resources you can own, how many bytes they store, and how long they are kept. This guide shows how to read your own live numbers: two endpoints report them, and they are the authoritative answer to “what are my limits, and how close am I?” Never hard-code limit values into client code — read them here, because tiers and per-account overrides mean your numbers can differ from anyone else’s and can change over time.
For the concepts behind these numbers — what each dimension means and why it exists — see the explanation page About usage quotas. This guide is the procedural companion: the calls and how to read them.
Prerequisites
Section titled “Prerequisites”- An API key. Create one in the FastFuels web app under your account settings. Set it once here: my-api-key. It propagates to every code block on this page.
See your limits
Section titled “See your limits”GET /users/me returns who you are, your tier, and your fully-resolved
limits — the tier defaults with any per-account overrides already merged
in. This is the canonical list of ceilings your account is held to. The example
response below shows the standard-tier defaults. Your own call returns
whatever applies to your account.
curl -X 'GET' \ 'https://api.fastfuels.silvxlabs.com/v2/users/me' \ -H 'accept: application/json' \ -H 'api-key: my-api-key'import fastfuels_sdk.v2 as ff
ff.set_api_key("my-api-key")
# get_quotas() returns your fully-resolved limits as a typed Quotas object.quotas = ff.get_quotas()
max_grid_jobs = quotas.max_active_gridsmax_domains = quotas.max_domainsgrid_storage_limit = quotas.max_grid_storage_bytes # bytes; GiB = value / 2**30{ "id": "owner-abc123", "kind": "user", "tier": "standard", "quotas": { "max_active_grids": 25, "max_active_exports": 10, "max_active_inventories": 10, "max_active_features": 10, "max_active_pointclouds": 5, "max_domains": 50, "max_grids": 1000, "max_exports": 500, "max_inventories": 500, "max_features": 500, "max_pointclouds": 50, "max_api_keys": 50, "max_applications": 5, "max_grid_storage_bytes": 53687091200, "max_export_storage_bytes": 26843545600, "max_inventory_storage_bytes": 10737418240, "max_feature_storage_bytes": 1073741824, "max_pointcloud_storage_bytes": 53687091200, "resource_ttl_days": 180, "failed_resource_ttl_days": 14 }}In the SDK, ff.get_quotas() returns this quotas object directly as a typed
Quotas — read its fields as attributes (quotas.max_active_grids). The raw
GET /users/me shown in the curl and Response tabs additionally carries your
tier and id. The quotas fields group into the dimensions the
explanation page
describes:
max_active_*— how many jobs of a type may be in progress at once.max_domains,max_grids, … — how many of each type you may own.max_*_storage_bytes— total stored bytes per type (the human number is bytes ÷ 2³⁰ = GiB).max_weekly_*_dispatches— how many jobs of a type you may start per ISO week.resource_ttl_days/failed_resource_ttl_days— how long resources are retained before automatic reclamation (nullmeans never).
See your usage against those limits
Section titled “See your usage against those limits”GET /users/me/usage pairs each limit with your current usage, so you can
see the headroom left before any ceiling — plus a lifecycle block echoing your
retention settings.
curl -X 'GET' \ 'https://api.fastfuels.silvxlabs.com/v2/users/me/usage' \ -H 'accept: application/json' \ -H 'api-key: my-api-key'usage = ff.get_usage()
# Can I start more grid jobs right now?grid_headroom = usage.grids.active.limit - usage.grids.active.usage
# Am I running low on grid storage?grid_storage = usage.grids.storagegrid_storage_fraction = grid_storage.usage_bytes / grid_storage.limit_bytes
# How many more domains can I create?domain_headroom = usage.domains.total.limit - usage.domains.total.usage{ "grids": { "active": { "usage": 3, "limit": 25 }, "total": { "usage": 214, "limit": 1000 }, "storage": { "usage_bytes": 8123400000, "limit_bytes": 53687091200 } }, "exports": { "active": { "usage": 0, "limit": 10 }, "total": { "usage": 5, "limit": 500 }, "storage": { "usage_bytes": 402653184, "limit_bytes": 26843545600 } }, "inventories": { "active": { "usage": 1, "limit": 10 }, "total": { "usage": 40, "limit": 500 }, "storage": { "usage_bytes": 1073741824, "limit_bytes": 10737418240 } }, "features": { "active": { "usage": 0, "limit": 10 }, "total": { "usage": 8, "limit": 500 }, "storage": { "usage_bytes": 160972, "limit_bytes": 1073741824 } }, "pointclouds": { "active": { "usage": 0, "limit": 5 }, "total": { "usage": 0, "limit": 50 }, "storage": { "usage_bytes": 0, "limit_bytes": 53687091200 } }, "domains": { "total": { "usage": 12, "limit": 50 } }, "applications": { "total": { "usage": 1, "limit": 5 } }, "api_keys": { "total": { "usage": 2, "limit": 50 } }, "lifecycle": { "resource_ttl_days": 180, "failed_resource_ttl_days": 14, "next_expiry_on": null }}Each resource entry pairs a usage with the limit it counts against:
active— jobs in progress now (usage) vs the concurrency limit (limit). This is the number that clears on its own as jobs finish.total— resources owned (usage) vs the count limit (limit).storage—usage_bytesvslimit_bytes.
Count-only types — domains, applications, and api_keys — carry only a
total. The top-level lifecycle block repeats your two retention TTLs and
next_expiry_on.
Read the numbers
Section titled “Read the numbers”The usage response answers these questions:
- “Can I start more grid jobs right now?” — compare
grids.active.usagetogrids.active.limit. The difference is how many more grid jobs can be in progress at once. A count, storage, or weekly-budget limit can still refuse a create before that. - “Am I running low on storage?” — compare each type’s
storage.usage_bytestolimit_bytes. - “How many domains can I still create?” —
domains.total.limitminusdomains.total.usage.
When you’re near a limit
Section titled “When you’re near a limit”If a create call is refused, the API returns a structured
429 QUOTA_EXCEEDED
naming the exact quota, your current value, and the limit. How you free
capacity depends on the dimension:
- Active-job limit — the response carries a
Retry-Afterheader. Wait for in-flight jobs to finish (or delete a running one you don’t need), then retry. - Count or storage limit — no
Retry-After. Delete resources you no longer need to free slots or bytes. Idle resources also expire automatically on the retention clock. - Weekly job budget — the detail carries
window_reset_on, the UTC time the budget resets, which is Monday 00:00 UTC. Deleting resources does not restore it. Wait for the reset. See Weekly job budget. - Need more headroom permanently — contact
support.fastfuels@silvxlabs.comto have your tier or a specific limit raised.
Where to go next
Section titled “Where to go next”- About usage quotas — the concepts behind
every number on this page: the five dimensions, tiers and overrides,
retention, and the full
429 QUOTA_EXCEEDEDmodel. - Create a domain — the first resource you create under your account, and the first place a quota can apply.