|
|
|
|
|
|
by warrior44
208 days ago
|
|
|
hit the curl. ~800ms TTFB. if this is truly "real-time" and not a cached graph, how do you handle rate limiting and CAPTCHAs at scale? Even with "public" data, on-demand scraping usually requires massive residential proxy rotation which eats that $0.03 margin alive. |
|
|
if you tried the curl command then yes this is indeed fast. the example curl command is hardcoded, john.smith@example.com is used with a static response for the purposes of allowing users to test the shape of the api without needing to be authed. low time to first test was my aim.
keen to hear if you have a use case for something like this?