Privacy-search keyword discovery
Use Startpage endpoints to turn privacy-search keyword discovery into repeatable API requests with documented inputs and JSON responses.
Retrieve the public phrases Startpage suggests for a search prefix, preserving position for privacy-search keyword research while keeping full Startpage SERP extraction outside the current contract.
Collect Startpage-ranked autocomplete suggestions as structured JSON, with a bounded count and explicit empty-result behavior.
Endpoint families
1
Documented params
3
Examples
1
Live catalog snapshot
Active endpoints
1
Methods
GET
Required params
2
Schema refs
1
{
"platform": "Startpage",
"endpoint": "startpage-suggest",
"method": "GET",
"path": "/startpage/suggest",
"auth": "apiKey"
}Use cases
Collect Startpage-ranked autocomplete suggestions as structured JSON, with a bounded count and explicit empty-result behavior.
Use Startpage endpoints to turn privacy-search keyword discovery into repeatable API requests with documented inputs and JSON responses.
Use Startpage endpoints to turn autocomplete trend monitoring into repeatable API requests with documented inputs and JSON responses.
Use Startpage endpoints to turn query expansion into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Startpage endpoint catalog — 1 endpoints, 3 documented request parameters, and 1 published response schemas — the same catalog Docs and Playground run against.
1 documented Startpage endpoints, all in the Suggest family.
3 request parameters are documented across those Startpage endpoints, 2 of them required — the full input contract is public before you write any integration code.
1 of the 1 Startpage endpoints ship a recorded example response, and 1 carry a documented response schema — you can code against the real JSON before the first request.
Startpage endpoints document their error responses (400, 429, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
1 hosted MCP tool backs the Startpage endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/startpage/suggest
Endpoint catalog
/startpage/suggestReturns Startpage search-box autocomplete completions for a query prefix, in Startpage's own ranking order. Startpage never returns more than 10 suggestions per prefix.
Response notes
- A prefix with no completions, including most non-Latin prefixes, returns a valid empty `suggestions` array, not an error. - Duplicate (case-insensitive) and empty suggestions are removed.
MCP tool startpage_suggest
Related APIs
Search & Web Discovery
Use a Google Trends API — an API for Google Trends data — to track search demand, trending terms, interest over time, regional interest, related and rising queries, plus Google Suggest discovery, as structured JSON for demand research and trend monitoring.
Search & Web Discovery
Extract Google News results — headlines, source names, article URLs, snippets, thumbnails, and recency — as structured JSON for media monitoring, brand mention tracking, and news aggregation workflows.
Search & Web Discovery
Extract Google Jobs results — job titles, listing snippets, and locations — as structured JSON for job-market intelligence, hiring-trend analysis, and recruitment sourcing workflows.
How to scrape Startpage
Startpage's current official about page describes a Netherlands-based private search product that delivers unprofiled results and does not retain search history. Crawlora's current public contract is narrower: /startpage/suggest returns autocomplete phrases only. It accepts a required prefix and optional count from 1 to 10, removes duplicate or blank rows, and can legitimately return an empty array. Full Startpage web search is not offered because its result pages use a proof-of-work challenge.
GET /startpage/suggest with required q. Use a partial phrase such as privacy to collect the suggestions displayed for that prefix.
Set count from 1 through 10. Startpage does not return more than 10 suggestions through this contract, and the endpoint removes blank and case-insensitive duplicate rows.
Keep each suggestion's position and the run date. Autocomplete is an ordered, changing publisher surface; a 2026 example should not become permanent product copy.
A valid prefix with no completions returns a successful empty suggestions array. Full web-result scraping is a separate unavailable surface here, because the current upstream pages use proof-of-work.
FAQ
The current catalog exposes autocomplete suggestions: query, ordered suggestion positions, and phrases. It does not expose Startpage organic web-search rows.
The committed endpoint documentation says Startpage result pages are behind a proof-of-work challenge, so the public Crawlora surface remains suggestions only instead of claiming unreliable SERP coverage.
Yes. A valid prefix can return a successful empty suggestions array. In the 2026-10-06 sample, privacy returned five English completions, while the sampled Chinese prefix 人工 returned zero.
No. Startpage's official privacy claims describe searches performed with Startpage. Crawlora is a separate API service with its own key, terms, and data handling; this endpoint only returns the supported public suggestion list.