Video · 0:44
API discovery
On a browser run, Kaabist watches the network for the JSON response that carries the values you extract. Once it has verified that endpoint, later runs read it directly on the HTTP tier: faster, and cheaper in credits.
Key moments
Transcript
A browser run reads the page. The program loads the product page in a browser and reads the prices from the screen. A browser run costs five credits.
Behind the page, requests fly. While the page loads, Kaabist watches the JSON responses it receives from its own server.
One of them carries the data. The prices on the screen came from an API call. Kaabist notices the same values in its response.
It checks that they match. Field by field, a validation run checks the response against what the page showed before the endpoint is used.
The next run skips the browser. Later runs read the endpoint directly over plain HTTP: no browser, no rendering, faster.
Same data, a fifth of the cost. The result has the same fields and types. An HTTP request costs one credit instead of five.