Four patterns cover most of what people do with public web data. Each one below is a real endpoint, a real response shape, and the call you would actually write.
1 API key · 1 schema · every pattern below
One call returns businesses for a niche and city with phone, email, website, rating, and review count already resolved. Filter to the ones missing a website and you have a web-design lead product on day one.
A lead list product, without owning a single proxy pool.
curl "https://sensecollect.com/v1/maps/no-website?query=restaurants&location=Hamburg" \
-H "x-api-key: $SENSECOLLECT_KEY"Pull reviews for any public ASIN and pipe the text into sentiment scoring, objection mining, or a support knowledge base. The complaints-only endpoint filters to 1- and 2-star records server-side, so you skip the paging entirely.
Structured customer language, ready for a model or a dashboard.
curl "https://sensecollect.com/v1/amazon/complaints?asin=B09G9FPHY6" \
-H "x-api-key: $SENSECOLLECT_KEY"67% of records are complaints
Poll a hashtag on a schedule and diff the engagement counts between runs. Plays, likes, comments, and shares arrive as numbers rather than formatted strings, so velocity is a subtraction instead of a parse.
Velocity alerts on topics your competitors notice a week later.
curl "https://sensecollect.com/v1/tiktok/hashtag?hashtag=fitnesscoach" \
-H "x-api-key: $SENSECOLLECT_KEY"Run the same question against maps, reviews, and posts, then join the answers on the unified record shape. One schema means one join key and one storage table instead of three pipelines that drift apart.
A single table your analysts can query without a translation layer.
curl "https://sensecollect.com/v1/maps/search?query=coworking&location=Lisbon" \
-H "x-api-key: $SENSECOLLECT_KEY"The catalog is public. Read it, price your calls, and build the pattern you actually need.