Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cloro.dev/llms.txt

Use this file to discover all available pages before exploring further.

cloro routes each request through infrastructure in the country you target. The supported list and granularity per provider live on the GET /v1/countries endpoint — call it with ?model=<provider> for a provider-specific list. This page covers the questions the endpoint page doesn’t: how to verify the proxy actually applied, and how language interacts with country.

​
Language behavior

country controls geo-routing. It does not force a response language. Most providers infer language from the prompt itself, so if you want a Spanish response from a Mexico-targeted request, write the prompt in Spanish. Mixed-language prompts (English prompt + non-English country) often work but can produce inconsistent localisation. For best results, match the prompt language to the target country.

​
Verifying the proxy was applied

A common support question is “I targeted country X but the response references country Y — is the proxy broken?” The proxy almost always applied correctly. What you’re seeing is LLM behavior, not routing:
  1. Pre-trained answers leak through. If a model was trained heavily on US English content, it will sometimes default to US-centric references even when served from a different region. The proxy was applied; the model just ignored the regional context.
  2. The prompt overrides the geography. A prompt like “best pizza in Cincinnati” will return Cincinnati results from any proxy. The location parameter affects what the search layer sees, not what the user asked for.
  3. Sources are the strongest signal. Inspect result.sources (or the provider’s equivalent). Sources from the targeted country’s domains (.de, .fr, .com.ua) confirm the proxy worked. If sources are diverse but the prose is US-centric, that’s a model bias, not a routing bug.
  4. HTML proof. Request include.html: true and inspect the rendered page. The page chrome (language, currency, regional UI) reflects where the request was actually made from.
If sources, HTML chrome, and response language all point to the wrong region, that’s worth a support ticket — include the taskId and the country you submitted.

​
Common questions

​
A country worked last month but now returns 400 errors. What changed?

Provider availability can shift week to week as upstream products roll out regional changes. Refresh /v1/countries?model=<provider> before assuming a regression — the supported list is the source of truth and it does change. If the country still appears in the list but requests keep failing, contact support@cloro.dev with the taskId.