Paste a schema, or let Magpie draft one.
Bring the schema you already have, or describe what you want and let Magpie propose the fields for a page you’ve scraped.
Typed JSON out, every time.
Titles come back as strings, prices as numbers, stock as true or false, ready for your code without cleanup.
Every LLM call logged, with its cost.
Extraction runs on your own key. Each call is logged with its tokens and cost, so the bill never surprises you.
Extract typed JSON in three steps.
- 01
Add your key
Paste the API key for the LLM you already pay for. It stays on your machine.
- 02
Set the schema
Paste one, or describe the fields and let Magpie draft it from a sample page.
- 03
Run and read the log
Get typed JSON back, with every call’s tokens and cost beside it.
Extraction, answered.
More in the docsWhich LLM does extraction use?
The one you choose, with your own API key. Magpie calls the provider directly from your machine and adds no markup.
Where does my API key go?
Into your OS keyring — or an encrypted file where there isn’t one — and from there only to the provider you chose. Once saved, Magpie never shows it again.
How do I know what a run costs?
Every LLM call is logged with its tokens and an estimated cost: per run in History, as you go on the Scrape screen, and as spend by provider on the Overview.