unlob vs Diffbot
Diffbot runs one of the few independent commercial crawls and a structured Knowledge Graph of entities. unlob indexes passages and exposes a coverage graph over them.
Verified 5 August 2026·Figures from vendors' own pages
Price
| Provider | Own index? | $ / 1,000 queries | Source |
|---|---|---|---|
$29 per month for 50,000 requests. | Yes Our own crawl and index | $0.58 | This page |
$199 per month for 500,000 requests. | Yes Our own crawl and index | $0.40 | This page |
When Diffbot is the better choice
A comparison page that cannot name a scenario where the competitor wins is an advertisement. Here are the real ones.
Choose Diffbot
- Structured entity records with attributes — firmographics, people, products — as data rather than as text.
- Visual extraction from pages that defeat conventional parsers.
- A long-established independent crawl.
Choose unlob
- Retrieval — finding the passages that answer a question, which is not what a knowledge graph is for.
- Corroboration and story clustering across sources.
- A published flat rate per query.
The substantive differences
| Diffbot | unlob | |
|---|---|---|
| Graph contents | Entities and their attributes. | Passages, hosts, stories, topics and entities, connected by publication and subject. |
| Primary use | Data enrichment and entity resolution. | Agent retrieval and context assembly. |
Sources
Every figure on this page was read from the vendor's own pricing page or funding announcement on the date shown.
- Diffbot: Diffbot pricingread 5 August 2026
Frequently asked questions
Is Diffbot’s Knowledge Graph the same as the unlob coverage graph?
No. Diffbot models entities as structured records with attributes — a company with a headcount, a location, a founder. The coverage graph models how documents relate: which host published what, which passages report the same story, what mentions which entity. One is a database of things; the other is a map of coverage.
Check the claims yourself
The free tier is 10,000 requests a month with no card. That is enough to test coverage, latency and result quality against your own queries — which is a better comparison than this page.