Scopes & permissions
End users grant fine-grained scopes over their FoodAPI partition.
Common scopes
foodapi:recipes:read/foodapi:recipes:writefoodapi:nutrition:readfoodapi:pantry:read/foodapi:pantry:writefoodapi:mealplans:read/foodapi:mealplans:writefoodapi:shopping:read/foodapi:shopping:writefoodapi:menus:read(write, ground, visualize, enhance, publish, and delete scopes exist for later phases)
Failures agents should handle
- Missing scope — authorization error; tool may be hidden and denied on call
- Ambiguous food — domain codes such as
NORMALIZATION_AMBIGUOUS - Quota —
402 QUOTA_EXCEEDED(shared with REST) - Rate limit —
429with backoff