Pulling a whole page into the conversation to find one number costs context on every subsequent turn of that conversation. Asking the scraping service the question means only the answer comes back. Reach for fields when you need structure across many pages, selectors when you know the markup and it is stable, and html only when the other four have failed — that order is roughly the order of increasing cost to you.
WebScraping.AI's endpoint. The tools differ by what you want back, which is the useful axis — a question, structured fields, or the markup.
- Question — ask a question about the page and get the answer
- Fields — extract named fields into structure
- Text and html — the readable text, or the raw markup
- Selected and selected_multiple — the content at a CSS selector, one or many
- Account — your usage against the plan
OAuth. Calls draw on the same usage-based API quota as their REST product, so the endpoint spends the credits you already buy.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen