BigOven
BigOven is a recipe and meal planning platform providing access to over 1,000,000 recipes via a REST API. Developers can search recipes, retrieve nutritional information, manage cloud-based grocery lists, and build diet and meal planning features. The API is offered by Aisle Ahead, Inc. and supports commercial food, nutrition, diet, and grocery applications.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles BigOven the way a machine reads it — 137 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — BigOven scores 45.4/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile BigOven
Each block below is one kind of artifact we hold for BigOven. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
BigOven Collection API
The Collection API from BigOven — 3 operation(s) for collection.
BigOven GroceryList API
The GroceryList API from BigOven — 8 operation(s) for grocerylist.
BigOven Images API
The Images API from BigOven — 6 operation(s) for images.
BigOven Me API
The Me API from BigOven — 6 operation(s) for me.
BigOven Note API
The Note API from BigOven — 3 operation(s) for note.
BigOven Recipe API
The Recipe API from BigOven — 21 operation(s) for recipe.
BigOven Review API
The Review API from BigOven — 6 operation(s) for review.
Scroll within the panel for all 7 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Bigoven Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Bigoven Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Bigoven Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
BigOven API Rules
SPECTRALJSON Schema 56
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
API2.Controllers.WebAPI.MeController.Option
JSON SCHEMAAPI2.GroceryListDepartmentResult
JSON SCHEMAAPI2.Models.Accounting
JSON SCHEMAAPI2.Models.BigOvenUser
JSON SCHEMAAPI2.Models.Counts
JSON SCHEMAAPI2.Models.Location
JSON SCHEMAAPI2.Models.Personal
JSON SCHEMAAPI2.Models.Preference
JSON SCHEMAAPI2.Models.Profile
JSON SCHEMAAPI2.Models.Recipes.FeedbackDTO
JSON SCHEMAAPI2.Models.Recipes.RecipeResponse
JSON SCHEMAAPI2.Models.Recipes.RecipeVideoResponse
JSON SCHEMAAPI2.Result
JSON SCHEMABigOven.Model.API.Grocery.GroceryList
JSON SCHEMABigOven.Model.API.Grocery.Item
JSON SCHEMABigOven.Model.API.Image
JSON SCHEMABigOven.Model.API.Ingredient
JSON SCHEMABigOven.Model.API.IngredientInfo
JSON SCHEMABigOven.Model.API.NutritionInfo
JSON SCHEMABigOven.Model.API.Recipe
JSON SCHEMABigOven.Model.API.RecipeInfo
JSON SCHEMABigOven.Model.API.RecipeNote
JSON SCHEMABigOven.Model.API.RecipeNoteList
JSON SCHEMABigOven.Model.API.Reply
JSON SCHEMABigOven.Model.API.Review
JSON SCHEMABigOven.Model.API.UserInfo
JSON SCHEMABigOven.Model.API.UserInfoTiny
JSON SCHEMABigOven.Model.API2.CollectionInfo
JSON SCHEMABigOven.Model.API2.GroceryList
JSON SCHEMABigOven.Model.API2.Photo
JSON SCHEMABigOven.Model.API2.Recipe
JSON SCHEMABigOven.Model.API2.RecipeInfox
JSON SCHEMABigOven.Model.API2.RecipeNote
JSON SCHEMABigOven.Model.API2.RecipeSearchResult
JSON SCHEMABigOven.Model.API2.UserInfoTinyx
JSON SCHEMABigOven.Model.InstructionStep
JSON SCHEMABigOven.Model.RecipeCategory
JSON SCHEMABigOven.Model.RecipeInfoDateTuple2
JSON SCHEMABigOven.Model.RecipeInfoReviewTuple2
JSON SCHEMABigOven.Model.RecipeInfoTiny
JSON SCHEMABigOven.Model.ShoppingListLine
JSON SCHEMABigOven.Result
JSON SCHEMASystem.Object
JSON SCHEMAScroll within the panel for all 56 ·
Examples 66
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Collection_Collections
EXAMPLECollection_Getcollection
EXAMPLECollection_Getcollectionmeta
EXAMPLEGrocerylist_Addrecipe
EXAMPLEGrocerylist_Delete
EXAMPLEGrocerylist_Deleteitembyguid
EXAMPLEGrocerylist_Department
EXAMPLEGrocerylist_Get
EXAMPLEGrocerylist_Post
EXAMPLEImages_Get
EXAMPLEImages_Getpendingbyuser
EXAMPLEImages_Getrecipephotos
EXAMPLEImages_Getscanimages
EXAMPLEImages_Uploadrecipeimage
EXAMPLEImages_Uploaduseravatar
EXAMPLEMe_Getoptions
EXAMPLEMe_Index
EXAMPLEMe_Putme
EXAMPLEMe_Putmepersonal
EXAMPLEMe_Putmepreferences
EXAMPLEMe_Skinny
EXAMPLENote_Delete
EXAMPLENote_Get
EXAMPLENote_Getnotes
EXAMPLENote_Post
EXAMPLENote_Put
EXAMPLERecipe_Autocomplete
EXAMPLERecipe_Autocompletemyrecipes
EXAMPLERecipe_Categories
EXAMPLERecipe_Delete
EXAMPLERecipe_Feedback
EXAMPLERecipe_Get
EXAMPLERecipe_Getactiverecipe
EXAMPLERecipe_Getrandomrecipe
EXAMPLERecipe_Getrecipewithsteps
EXAMPLERecipe_Getstep
EXAMPLERecipe_Getstepnumber
EXAMPLERecipe_Getsteps
EXAMPLERecipe_Getv2
EXAMPLERecipe_Post
EXAMPLERecipe_Put
EXAMPLERecipe_Raves
EXAMPLERecipe_Recentviews
EXAMPLERecipe_Recipesearch
EXAMPLERecipe_Recipesearchrandom
EXAMPLERecipe_Related
EXAMPLERecipe_Scan
EXAMPLERecipe_Zaprecipe
EXAMPLEReview_Delete
EXAMPLEReview_Deletereply
EXAMPLEReview_Get
EXAMPLEReview_Getreplies
EXAMPLEReview_Getreviews
EXAMPLEReview_Post
EXAMPLEReview_Postreply
EXAMPLEReview_Put
EXAMPLEReview_Putlegacy
EXAMPLEReview_Putreply
EXAMPLEGet Recipe Recipeid Review
EXAMPLEGet Recipe Review Reviewid
EXAMPLEPost Grocerylist Item
EXAMPLEPut Me Profile
EXAMPLEScroll within the panel for all 66 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for BigOven — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/bigoven · machine-readable index on apis.io