Reference & Lookup Data · Integration
Nutrition
Add Nutrition to your product for your customers, and give your AI agents governed access to it.
Embed the Nutrition connector so your product can answer food and nutrition questions from a real dataset instead of one you would have to build and keep current. The connector calls the Spoonacular food API, which covers recipe search and detail, ingredient lookup and substitutes, nutrition analysis for a dish or a recipe, meal plans, shopping lists, and grocery product and menu item data. Each customer supplies their own API key, so request volume and cost are attributable to the tenant that caused them rather than pooled through one key you have to meter. fastn owns the credential storage, retries, throttling and API upkeep, and the same governed connection is what your AI agents call.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Add recipe and ingredient search to your product, with each customer's own API key used for their requests.
Return nutrition analysis for a dish or a recipe so your product can show macro and calorie detail without you curating a food database.
Generate meal plans and shopping lists inside your product from the constraints a user actually set.
Keep request volume attributable per tenant so a heavy customer's usage does not show up as your platform's bill.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent looks up the nutrition profile of a dish before it answers a user's question, with the call logged.
An agent builds a week of meals against a user's stated constraints and returns the shopping list.
An agent suggests an ingredient substitute and explains the nutritional difference, using only that tenant's key.
Example prompt
Build a week of dinners under 600 calories each from these ingredients and give me the shopping list.
Set up Nutrition in 4 steps
- 01Enable the Nutrition connector in your fastn dashboard.
- 02Have each customer supply their own API key so lookups run against their own allowance.
- 03Decide which lookups your product exposes and map the response fields onto your own schema.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Nutrition integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Nutrition integration without building it. Your customers connect their own Nutrition account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Nutrition update is not your on-call problem.
- One integration serves your product and your agents. The same governed Nutrition connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
Weather API
OANDAOften used alongside
Tools the same teams tend to run next to Nutrition, across other categories.
Salesforce
HubSpot
Notion
SnowflakeNutrition integration FAQ
How do I add a Nutrition integration to my product?
Enable the Nutrition connector in your fastn dashboard, then let each customer authenticate their own Nutrition account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Nutrition client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Nutrition account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Nutrition account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Nutrition integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent looks up the nutrition profile of a dish before it answers a user's question, with the call logged.
Who maintains the Nutrition integration?
fastn does. When Nutrition changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does a Nutrition lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should Nutrition results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Nutrition is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the Nutrition integration?
A common starting point: add recipe and ingredient search to your product, with each customer's own API key used for their requests. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Nutrition integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Nutrition does not change your per-connector cost. You can start free with 3 connected accounts.
Add Nutrition to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.