Hey everyone! 👋 I'm Saran, the maker of SearchResult API.
The short version: One API endpoint. You give it any website URL + a search query. It gives you back clean, structured results as JSON, Markdown, or HTML tables. No scrapers, no browser automation, no per-site config.
Why I built this:
I was deep into building a research agent that needed to pull data from arXiv, Hacker News, Google Scholar, and a bunch of other sites. Every single site meant writing a new scraper, defining a new schema, and fixing it two weeks later when the DOM changed. I kept thinking — why isn't there just one endpoint that handles all of this?
So I built it.
What makes it different from tools like SerpAPI or Firecrawl:
Those are great for Google results or raw page scraping. SearchResult does something different — it runs the query on the target site's own search and returns structured results in that site's native schema, auto-detected. You're not getting Google's interpretation of arXiv. You're getting arXiv's actual results, structured and clean.
What's under the hood:
Optimized adapters for 100+ popular sites, plus a generic extractor that handles the rest. We respect robots.txt and rate limits across the board. Average response time is around 1–2 seconds.
Getting started takes 30 seconds:
Free tier gives you 50 queries, no credit card needed. Hit the playground on our site, throw a URL at it, and see what comes back.
Where I'd love your help:
If you try a site and the results come back messy or incomplete — that's gold for me. Drop it in the comments or shoot me a message. That's the single most useful feedback I can get right now.
Excited to hear what you all think. I'll be here all day answering questions!
Hey everyone! 👋 I'm Saran, the maker of SearchResult API.
The short version: One API endpoint. You give it any website URL + a search query. It gives you back clean, structured results as JSON, Markdown, or HTML tables. No scrapers, no browser automation, no per-site config.
Why I built this:
I was deep into building a research agent that needed to pull data from arXiv, Hacker News, Google Scholar, and a bunch of other sites. Every single site meant writing a new scraper, defining a new schema, and fixing it two weeks later when the DOM changed. I kept thinking — why isn't there just one endpoint that handles all of this?
So I built it.
What makes it different from tools like SerpAPI or Firecrawl:
Those are great for Google results or raw page scraping. SearchResult does something different — it runs the query on the target site's own search and returns structured results in that site's native schema, auto-detected. You're not getting Google's interpretation of arXiv. You're getting arXiv's actual results, structured and clean.
What's under the hood:
Optimized adapters for 100+ popular sites, plus a generic extractor that handles the rest. We respect robots.txt and rate limits across the board. Average response time is around 1–2 seconds.
Getting started takes 30 seconds:
Free tier gives you 50 queries, no credit card needed. Hit the playground on our site, throw a URL at it, and see what comes back.
Where I'd love your help:
If you try a site and the results come back messy or incomplete — that's gold for me. Drop it in the comments or shoot me a message. That's the single most useful feedback I can get right now.
Excited to hear what you all think. I'll be here all day answering questions!