Skip to main content

AI Extract

AI Extract loads one page and turns it into the data you asked for. You give it a URL and a description of what you need — optionally a JSON Schema — and it returns the fields, not the page. It is synchronous: one call, one result, no session to poll. A run costs a flat 5 points.

When to use it

Use AI Extract when the source is known and the shape of the answer matters:
  • fields from a company website: pricing, offices, contacts, legal entity
  • a profile, listing or product page turned into a record
  • one-off scraping where writing a parser is not worth it
  • intake pipelines that must produce the same JSON every time
If you don’t know which page holds the answer, start with Search or let AI Research find and read pages for you. If the source is a provider we already cover — LinkedIn, a marketplace, a company registry — a Data Source returns a stable schema with no prompt to write.

Example request

Without a schema, the fields come back as readable text in human and machine is null:

Asking for a schema

Pass a JSON Schema as a string in settings.extract_schema_json and the same page comes back as machine, shaped exactly like your schema. This is the mode to use in a pipeline — the response stays stable even when the page is redesigned.
A field the page does not state comes back null rather than guessed — team and location above are not on that page.

Request reference

Response reference

Notes worth knowing

  • One page per run. AI Extract does not follow links or paginate. For many pages, call it per URL, or use AI Research with a page budget.
  • Pages behind hard anti-bot defences may fail. When a page cannot be loaded the run fails rather than returning an empty object, so a failed load is never silently an empty record.
  • The schema is a contract, not a filter. Asking for a field the page lacks yields null; it does not drop the key.

Next steps