Recipe API · FinOps Profile

Recipe API Finops

FinOps mapping for Recipe API, derived from the prices Recipe API publishes (https://recipe-api.com/pricing), transcribed verbatim in plans/recipe-api-plans.yml. Nothing here is estimated.

Recipe API Finops is the FinOps profile for Recipe API on the APIs.io network, aligned with the FinOps Foundation Framework.

The provider bills by 500 image credits, as read on 2026-10-28.

It defines 1 billable meter, billed in USD, on a monthly cycle, and pricing category commitment (subscription).

The profile maps 4 FOCUS columns for cost-allocation reporting.

Tagged areas include Recipes, Food, Nutrition, Ingredients, and Data.

Pricing: Commitment (Subscription) Billing: Monthly FOCUS v1.3 Bills by: 500 image credits
Derived by API Evangelist from the provider's plans and contracts on 2026-10-28.
View Source
RecipesFoodNutritionIngredientsDataGenerative AIMCPAgents

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

FOCUS Columns

BillingCurrency
USD
PricingUnit
500 image credits
ProviderName
Recipe API
ServiceName
Recipe API

Meters

500_image_credits
Unit: 500 image credits

Sources

Work with this as data

Every finops artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for finops

4 MCP tools reach this
  • find_finopsBrowse and filter every finops artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This finops artifact 
curl "https://apis.io/api/v1/finops/recipe-api-finops"
All finops 
curl "https://apis.io/api/v1/finops?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.