Daring Foods
Daring Foods is an American plant-based food company, founded in 2018 by Ross Mackay and Eliott Kessas, that makes 100% plant-based chicken from a deliberately short ingredient list with soy as the protein base. Trading simply as "Daring", it sells retail Plant Chicken in shredded, diced and breaded-pieces formats plus a line of ready-to-heat Plant Chicken Bowls and Plant Chicken Wings through more than 15,000 US grocery stores, and runs a separate foodservice business supplying bulk and gluten-free product to restaurants, campus dining and institutional kitchens. The company raised over $120 million across 2020-2021 during the plant-based protein boom and was acquired by the Australian plant-based meat manufacturer v2food in 2025, under which it retains its own brand. Daring Foods is a consumer packaged goods business, not a software vendor: it operates no developer program, publishes no product API, and offers no portal, SDKs or developer support. The only machine-readable interface it exposes is the WordPress REST content API behind daring.com, which is anonymously readable and unusually well-stocked for a CPG site - 208 recipes classified by cooking method, 14 retail products, 7 foodservice products, 17 marketing pages and a 749-item media library - captured here for discovery purposes.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Daring Foods the way a machine reads it — 33 machine-readable artifacts across 14 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 — Daring Foods scores 32.6/100 (thin), with a separate agent-readiness read of 45/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.
Put this on your own site. The badge is drawn live from Daring Foods's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/daring-foods/"
title="Daring Foods on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/daring-foods.svg"
alt="Daring Foods Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/daring-foods/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/daring-foods/"
title="Daring Foods on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/daring-foods/card.svg"
alt="Daring Foods Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Daring Foods
Each block below is one kind of artifact we hold for Daring Foods. 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 14
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.
Daring Foods Recipes API
Public, unauthenticated read access to the Daring recipe library via the site's custom `recipes` WordPress post type. Verified live at 208 published recipes, each classified by ...
Daring Foods Retail Products API
Public, unauthenticated read access to the Daring retail plant-chicken catalog via the custom `products` post type - Original Shredded and Diced Plant Chicken, the Plant Chicken...
Daring Foods Foodservice Products API
Public, unauthenticated read access to the Daring foodservice (B2B) product line via the custom `foodservice-products` post type - the bulk and gluten-free product sold to resta...
Daring Foods Pages API
Public, unauthenticated read access to the 17 static marketing pages of daring.com - Our Mission, Ingredients, How To Cook, Locator, FAQ, Careers, Terms & Conditions and the Foo...
Daring Foods Media API
Public, unauthenticated read access to the media library behind daring.com - packaging and product photography, recipe imagery and site assets. Verified live at 749 attachments,...
Daring Foods Search API
Public, unauthenticated cross-content search over daring.com, returning lightweight id / title / url / type / subtype records spanning recipes, retail products, foodservice prod...
Daring Foods Discovery API
The self-describing metadata layer - route index (222 routes across 10 namespaces), registered post types, taxonomies, statuses and authors - that makes the whole daring.com sur...
Daring Foods Posts API
Public, unauthenticated read access to the standard WordPress `post` collection and its comment thread. Daring Foods runs no editorial blog - the collection holds one post, the ...
Daring Foods oEmbed API
Public oEmbed 1.0 provider endpoint for daring.com URLs, returning embeddable rich metadata - title, author, thumbnail and iframe markup - for any recipe, product or marketing p...
Daring Foods SEO Metadata API
Public Yoast SEO head endpoint returning the rendered SEO metadata and full schema.org JSON-LD graph for any daring.com URL - the most structured description of a Daring recipe ...
Daring Foods Categories API
The `category` taxonomy - cooking methods for the recipe library.
Daring Foods Comments API
Comments attached to posts. 41 approved, predominantly automated spam.
Daring Foods Metadata API
Post types, taxonomies, statuses and authors.
Daring Foods Tags API
The `post_tag` taxonomy. Registered but empty on this site (0 terms).
Scroll within the panel for all 14 ·
Open Collections 15
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONDaring Foods Taxonomy Categories API
OPEN COLLECTIONDaring Foods Posts Comments API
OPEN COLLECTIONDaring Foods Discovery API
OPEN COLLECTIONDaring Foods Products Foodservice API
OPEN COLLECTIONDaring Foods Media API
OPEN COLLECTIONDaring Foods Discovery Metadata API
OPEN COLLECTIONDaring Foods O Embed API
OPEN COLLECTIONDaring Foods Pages API
OPEN COLLECTIONDaring Foods Posts API
OPEN COLLECTIONDaring Foods Retail Products API
OPEN COLLECTIONDaring Foods Recipes API
OPEN COLLECTIONDaring Foods Search API
OPEN COLLECTIONDaring Foods Metadata SEO API
OPEN COLLECTIONDaring Foods Taxonomy Tags API
OPEN COLLECTIONScroll within the panel for all 15 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
daring-foods-mcp.yml
MCP SERVERSecurity 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 Daring Foods — 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.
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 8
The organization behind the API
Scroll within the panel for all 8 ·
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/daring-foods · machine-readable index on apis.io
This is an independent, third-party profile of Daring Foods, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.