Skip to content

Spoonacular API Pricing: What 150 Free Points Really Get You

Published July 17, 2026

Spoonacular API pricing confuses developers because it is not priced per request — it is priced in points. Every endpoint costs a different number of points, so your real capacity depends on which calls you make. This guide explains the model and a simpler alternative when you only need nutrition data. Confirm current numbers on Spoonacular's site before committing.

The Points Model

  • Free tier: roughly 150 points per day.
  • Points per call: each request costs a base point value plus extra points for the data returned, so a recipe-with-nutrition call costs more than a simple lookup.
  • Paid tiers: raise the daily points allotment for a monthly fee.

The catch: "150 points/day" is not 150 requests. A handful of nutrition-heavy recipe calls can consume your daily budget, which makes capacity planning hard.

Why It Is Hard to Forecast

FactorEffect on cost
Points vary by endpointSame request count, different spend
Nutrition adds pointsMacro data costs more per call
Daily resetBursty traffic exhausts the day early

When You Only Need Nutrition Data

Spoonacular bundles recipes, meal planning, and nutrition. If you only need food and nutrition lookup, a flat request-quota API is cheaper and far easier to forecast. The Calorie API charges by request, not points:

curl "https://api.calorieapi.com/api/v1/search/foods?q=oatmeal" \
  -H "X-API-Key: YOUR_API_KEY"
Spoonacular (free)Calorie API (free)
UnitPoints (~150/day)Requests (1,000/mo)
ForecastingHard (varies by call)Simple (1 call = 1 request)
ScopeRecipes + nutritionFood + nutrition
Credit cardVariesNot required

Start Building

Frequently Asked Questions

How does Spoonacular API pricing work?

Spoonacular prices in points, not requests. Each endpoint costs a base point value plus extra points for the data returned, and your plan grants a daily points allowance rather than a request count.

What is the Spoonacular free tier limit?

The free tier is roughly 150 points per day. Because endpoints cost different point amounts, that is not 150 requests, and nutrition-heavy calls consume points faster.

Why is Spoonacular hard to budget?

Point cost varies by endpoint and by whether you include nutrition, so the same number of requests can cost very different amounts. A request-based API is easier to forecast.

What is a simpler alternative for nutrition data?

If you only need food and nutrition lookup, the Calorie API charges per request with a free tier of 1,000 requests per month, so one call equals one request and budgeting is straightforward.

← Back to all articles

Start building with the Calorie API

Get a free API key and access 4M+ foods with search, barcode lookup, and full macro data.