FindCamp

Compare two campsites (camp_key_a + camp_key_b) or a shortlist of 2-5 (camp_keys) for a given profile. Two camps: decision-changing differences (signal bands and named evidence such as noise sources) and a recommendation — the better fit when the differences point one way, otherwise 'close call' naming what decides for each. Shortlist: a ranking with one line per camp on what sets it apart or holds it back, plus a recommendation between the top two. Each key accepts a FindCamp camp key or the campsite's human name; pass country/city to disambiguate. Never returns numeric scores.

compare

Return up to 5 campsites with an API key, up to 3 for public access, that best fit a traveller profile. Each result has a verdict, one_reason (why it was picked for what was asked, then what sets it apart), its catch and its coverage; in a lake region, a result far from the water carries setting_note; a result whose record shows no pitches (rentals only) carries stay_note. Optionally scoped by country code (fr|de|it|at|hr|gr|si), region_query (a region, island, lake or town), near / near_lat+near_lng with radius_km, or a route of points; filtered by must_have facilities; ranked by priorities. Naturist campsites are left out unless must_have includes "naturist". When nothing can be returned, the result carries no_match with the reason and suggestions to ask again with. Never returns numeric scores and never enumerates the catalog.

find_fit

Return a fit verdict, 2-3 reasons, and one tradeoff for a specific campsite and traveller profile, and, when the data supports it, one `condition` the reader can act on (where to pitch, what to ask before booking, what to accept). camp_key accepts either a FindCamp camp key or the campsite's human name (e.g. 'Zaton' or 'Camping Zaton'); pass country/city to disambiguate. Optionally pass priorities (up to 4 signal keys) to scope the verdict to specific signals instead of the profile's defaults. Based on FindCamp's analysis of public comments. `coverage` says how much the verdict rests on (well, partly or thinly covered); `change` names renovation or new management that guests describe in the last two seasons; `evidence_basis` says, per signal behind the reasons, how many guests mention it and how recent (words, never counts); `evidence_note` says the same in one sentence; `answer` answers the profile's own question first (e.g. 'Quiet at night? Mostly — see the catch'); `reason_tones` marks each reason as for or against; `signals_refreshed` is the month the analysis was refreshed, not the date of the comments. Never returns numeric scores. When the FindCamp card is shown, do not repeat its verdict, reasons, catch or candidate list. Instead write 2-4 concrete sentences the card does not show: use evidence, strengths and refine from the result, explain what the verdict means for this user's choice, and suggest one next step (e.g. a quieter alternative via find_fit or a compare). Do not invent facts beyond the result.

get_verdict

Practical facts for one campsite, for questions like 'is it noisy, and from what?', 'is it windy?', 'can a big motorhome get in?', 'do I need to book early?', 'what costs extra?', 'what is the beach like?', 'how far is the supermarket?', 'are dogs allowed?'. Returns only what is on record (facility data and public comments) — a missing topic means nothing is recorded, not that it is fine. No verdict; use get_verdict for fit. camp_key accepts a FindCamp camp key or the campsite's human name; pass country/city to disambiguate.

get_camp_facts