# The page loads its data from somewhere. Kaabist finds where.

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.

## Watch, match, verify

The network log of a browser run is scanned for JSON responses whose payload holds the values the program extracted. A match is checked with a validation pass before it is trusted.

## The cheaper tier, automatically

A verified endpoint becomes one more locator candidate for that site. When it answers, the next jobs run on the HTTP tier instead of a full browser.

```
{ "extract": {
  "plan": ".plan-name",
  "renewal_date": { "selector": ".renews", "type": "date" }
} }
```

## Without changing your program

You keep writing the program against the page. The endpoint Kaabist found is kept with the site, not in your program, so there is nothing extra to write or maintain.

## Questions

### Does it work on every site?

On sites whose pages load their data as JSON, which many modern ones do. When there is no such endpoint, the program simply keeps running in the browser.