Upstream request spend and the policy governing it: requests used today, the daily allowance (null when the quota is disabled — that is unlimited, not zero remaining), overshoot, accounting status, operation spacing, queue depth, the estimated wait for a new operation, and the circuit-breaker state. Local and free. Read this before planning work that costs many requests, and after a budget error. Example: budget() -> {"daily_limit": null, "used_today": 39, "remaining_today": null, "accounting_status": "reconciled", "operation_spacing_seconds": 6, "next_slot_seconds": 6, "circuit": {"state": "closed"}}

What this backend can actually do right now, per feature and per engine, with the evidence behind each claim. Local and free: it never contacts Google. Call it once at the start of a session and believe it over any other description — a feature absent here is unsupported no matter what another tool's text implies. Also reports the place kinds, currency and locale allowlists, limits, per-tool upstream cost, active ports and effective configuration. Example: features() -> {"features": {"search.one_way": {"supported": true, "supported_engines": ["page"], ...}, "explore.destinations": {"supported": false, ...}}, "currency_allowlist": ["MYR","SGD","USD"]}

Turn free text into place candidates — airports, cities and countries. Local data and previously resolved places answer for free; a miss asks Google and COSTS ONE UPSTREAM REQUEST, then remembers the answer permanently, so any country works without anyone editing a list. A place you have not looked up yet is simply unresolved, never unsupported. Ambiguous text returns several candidates and no session; you pick, then pass the `id` straight to `search`. Read `searchable`: a place can resolve and still not be searchable, because Google addresses cities and countries by its own place id and only verified ones are recorded. When it is false, `search_note` says why. The dataset is a partial seed, so no candidate means a dataset gap, not a place that does not exist. Example: resolve_place(text="Japan", kind="country") -> id "country:JP", searchable true; pass that id as a leg's `to` and search returns Japan flights. resolve_place(text="Vietnam") -> resolves, searchable false, with the reason.