Evaluate the data before building the pipeline

Estimate a request budget

Versioned API plan observations; checked dates shown per plan. Local arithmetic only; no account connection, recommendation or upload.

Markets and days: whole numbers. Seconds and hours: fractional values allowed within bounds. Daily sessions reset at t=0: poll times 0, interval, … strictly before session end. One request per market per complete sweep; no batching, retries or pagination included. Additional clients share the quota.

211,200 requests from 480 complete polls per market per daily session. Schedule resets at day-start; t=0 is included, session end is excluded. Final sweep window 60.000 seconds. Average active rate 0.333 requests/second; assumed peak 1 requests in one second. Developer meets numerical monthly and rate capacity only. History and endpoint entitlements are a separate gate.

Daily session-start model: reset the schedule each day, poll every market at t=0 and each interval strictly before session end. Overnight time is not prorated. Spread mode queues each sweep before the next poll or session end; its final window can be shorter than the interval, and peak-rate checks use that shortest window; burst mode dispatches the entire sweep at each start. One request per market per sweep; 30/31-day monthly allowance as documented, no batching. Retries, pagination and concurrent clients add requests. Numerical capacity alone does not establish endpoint/history entitlement. A capacity pass is not a recommendation or verification of data rights.