Read pages behind your own login
Dashboards, member areas and account pages on sites where you have an account. Copy your session cookies from the browser, send them with the request, and Spidra loads the page as you.
Paste them as they are
{
"urls": [{ "url": "https://app.example.com/reports" }],
"prompt": "Extract the monthly traffic summary",
"cookies": "session_id\tabc123xyz\t.example.com…"
}
Rows copied from DevTools are read as they are: Spidra takes each cookie's name, value, domain and path and ignores the other columns.
Three steps, no browser automation to write
Sign in as you normally would
In Chrome, Firefox or Edge, on the site where you have an account.
Copy the cookies
DevTools, then Application (or Storage in Firefox), then Cookies. Select the rows and copy, or copy just the session ones.
Send them with the request
Put them in the cookies field. Spidra loads the page as you.
Two formats, detected for you
A standard cookie string, or rows pasted straight from the DevTools cookie table. You don't say which.
1{2 "urls": [{ "url": "https://app.example.com/reports" }],3 "prompt": "Extract the monthly traffic summary",4 "output": "json",5 "cookies": "session_id=abc123xyz; auth_token=eyJhbGciOiJ..."6}
The values above are placeholders. Never commit real cookies to code.
Works on
Scrape
1 to 3 pages, with a prompt or schema if you like.
Batch scrape
Up to 50 pages. Retries need the cookies again, since they're never stored.
Crawl
Every page the crawl visits on that site, behind the same login.
Map
List the URLs of a site whose pages need a sign-in.
Never stored
Your cookies go to the job that uses them and nowhere else. Nothing is kept afterwards.
Your accounts only
Use it on sites where you have an account and their terms allow it. You're responsible for how it's used.
Popular sites stay logged out
Built-in readers for sites like LinkedIn and Instagram never send your cookies there.
Questions, answered
Logged-in pages
No. They're passed to the job that uses them and aren't kept afterwards. That's also why a batch retry needs them sent again; without them, the retry runs logged out and the response warns you.
You build the product.
Spidra handles the data work.
Start with 300 free credits, about 300 pages. No credit card required.