Typo-tolerant fuzzy search over foods (API key, rate-limited)
GET /foods/search · API key required
Postgres pg_trgm word_similarity() over food_name, so a misspelled Malawian food name (e.g. "Chinagwa" for "Chinangwa") still resolves - unlike GET /foods?search=, which requires an exact substring. Runs between the exact-ilike local match and the external cache/API cascade inside /foods/lookup and everything built on it.
Parameters
q(query, required)max_results(query)min_similarity(query) - Per-word similarity floor, 0-1.
Responses
200400429