Polish web search
Polskilang=plSeven cases and rich inflection; semantic retrieval avoids the stemming problem entirely.
Example
# Polish sources only
curl -H "x-api-key: $UNLOB_API_KEY" \
"https://api.unlob.com/search?q=polityka%20klimatyczna&lang=pl&limit=10"
# The same meaning, sources in any language
curl -H "x-api-key: $UNLOB_API_KEY" \
"https://api.unlob.com/search?q=polityka%20klimatyczna&mode=semantic&limit=10"How multilingual retrieval works here
The conventional approach runs a separate index per language and translates queries between them, which multiplies infrastructure and loses meaning at every boundary. A single multilingual embedder places all 101 supported languages in one shared space, so texts with the same meaning land near each other regardless of the language they are written in.
The practical consequence is that a query in English can retrieve a Polish passage directly, and vice versa — with no translation step, no per-language index, and no additional resident memory. Only semantic and hybrid modes do this; keyword mode matches tokens, and tokens are monolingual.
Common questions
How do I search Polish web content?
Set lang=pl on any search request. You can also leave it unset — the embedding space holds 101 languages at once, so a query in any language retrieves relevant Polish passages directly.
Do I need to translate my query into Polish?
No. Semantic and hybrid modes cross languages natively. Translating would search for the translation rather than the meaning, which is usually worse. Use lang only when the results must be readable to a Polish-speaking user.
Does keyword mode work for Polish?
Within Polish it does. What keyword mode cannot do is cross languages — token matching is monolingual by construction. Use semantic or hybrid mode if you want Polish sources from a query in another language.
Search Polish sources
10,000 free requests a month, no card. All 101 languages are available on every plan.