Fast-path lookups — no credentials needed
For these sites, common questions resolve in 1-4 seconds because we maintain structured indexes against them. Just phrase the question naturally; stablebrowse figures out the best data path.Hacker News
top, new, best, ask, show, jobs; story details; comments
Wikipedia
search, article, summary, sections, references, recent changes, random
Stack Overflow
search, question, answers, tags, users
Steam
search, app details, reviews, featured, categories
Yelp
search, business details, autocomplete
Amazon
search, product, deals, bestsellers, departments
Airbnb
search, listing, dates, guests, amenities
Craigslist
search by city + category
GitHub
repos, issues, PRs, code search
Google Flights
search by origin / destination / dates
LeetCode
problems, filters, difficulty, tags
Redfin
listings, properties, sale / rent
Starbucks
locations, hours, menu
Uber
fare estimates, ride types
Walmart
search, products, deals
Zillow
listings, properties, sale / rent
Authenticated platforms
For these platforms stablebrowse uses each site’s internal APIs through an authenticated browser session. You supply the end-user’s cookies via the credentials endpoint, the system calls the right API for the question, and results come back in 5-30 seconds.Twitter / X
Twitter / X
Cookies needed:
twitter_auth_token, twitter_ct0Capabilities: searching tweets, fetching a user’s timeline or replies, user profiles, home timeline, trending topics, following lists.How to get the cookies: log in to x.com in a browser → DevTools → Application → Cookies → copy auth_token and ct0.Reddit
Cookies needed:
reddit_session (only for authenticated features like fetching your own profile)Capabilities: browsing subreddits, searching posts, reading comment threads. Most features work without any cookies.TikTok
TikTok
Cookies needed for auth-gated features:
tiktok_session_id, tiktok_csrf_tokenCapabilities: hashtag pages, trending, user profiles, video detail, comments, search users, followers/following, your own profile. Public features (hashtag, trending, video, profile) work without cookies.YouTube
YouTube
Cookies needed for auth-gated features:
youtube_sid, youtube_hsid, youtube_ssid, youtube_sapisidCapabilities: search, video detail, comments, channels, home feed, subscriptions feed, watch history, playlists. Search, video detail, comments, and channel pages work without cookies.Instagram
Cookies needed:
instagram_session_id, instagram_csrf_token, instagram_ds_user_idCapabilities: profiles, full profiles, searching reels, hashtag posts, and more.LinkedIn
Credentials needed: an Exa API key (for search) + optional LinkedIn session cookies for richer profile data.Tooling uses Exa’s LinkedIn index as primary, with Apify as a real-time fallback when the cache misses.
DoorDash
DoorDash
Cookies needed for auth-gated features:
doordash_session_id, doordash_csrf_tokenCapabilities: search food, get restaurant menus.Everything else on the web
Any site not listed above runs through the full browser agent — the system reads the page, plans its next action, clicks, scrolls, and extracts. Works for most of the public web: blogs, news, dashboards, one-off research. Typically 10-60 seconds per task. This is also the fallback when a site IS in the fast-path list but the specific question doesn’t fit a pre-indexed pattern.Credential storage
All credentials are encrypted at rest via AWS KMS. They’re attached to a specific(businessId, endUserId) pair and never returned in any GET response — the status endpoint only says “configured: true/false” per platform. Delete them at any time via DELETE /v1/end-users/{id}/credentials.