Search
Search API — endpoints, requests, and responses.
For AI agents: https://bytekit.com/llms.txt — every docs page is available as markdown by appending .md
The Search API. 1 endpoint:
POST /v1/schemaSchema-driven structured extraction
Fetches `url` and extracts structured JSON conforming to the supplied JSON Schema (draft 2020-12) using an LLM. Fast-path only — slow-path rendering options (`wait_until=networkidle`, `delay_ms`, `wait_for_selector`) cause a `400 unsupported_option`. Dual-axis billing: a fixed per-request credit charge **plus** the underlying page's bandwidth, billed at its upstream wire bytes with no endpoint factor (a 100 KiB estimate is pre-charged, then reconciled). The bandwidth is still billed when the scrape succeeds but extraction later fails; both axes are refunded only when the scrape itself never runs.
POST /v1/searchSearch the web
Runs a web search for `query` and returns ranked organic results with contiguous `position` values from 1. Use `limit` (1–100, default 10) to request more results in a single call. Results are fetched in pages of 10, so a call consumes `ceil(limit / 10)` credits (capped at 10) from the account's monthly credits bucket — for example `limit=10` costs 1 credit and `limit=35` costs 4. Credits are charged for every page fetched regardless of how many results a page returns. The credit count is reported as `credits_used` in the response.