LIVEKINDLY
LIVEKINDLY Collective (thelivekindlyco.com) is a global plant-based food company founded in March 2020 by Roger Lienhard around a mission to make plant-based living the new norm. It is a house of alternative-protein brands — Fry's Family Food Co., Like Meat, Oumph! and The No Meat Company — sold across Europe, the UK, South Africa and North America, and it also runs a B2B Solutions arm supplying plant-based protein to other food businesses. The Collective raised over half a billion dollars across its early rounds, reported profitability in November 2025, announced it was joining forces with TiNDLE Foods in December 2025, and was certified as a B Corp in June 2026. LIVEKINDLY publishes no developer platform, no documentation portal and no OpenAPI. The machine-readable surface on thelivekindlyco.com is its WordPress REST API (wp/v2), which serves the corporate newsroom, the brand and partner directories, the careers listings, pages and media library as anonymously readable JSON, alongside a WordPress MCP Adapter endpoint that is live and fronted by a real RFC 8414 OAuth authorization server — but is authentication-gated to a single "mcp" scope. The company is tracked on the Forge Global secondary market.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles LIVEKINDLY the way a machine reads it — 31 machine-readable artifacts across 13 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 — LIVEKINDLY scores 21.2/100 (emerging), with a separate agent-readiness read of 29/100 (agent aware). 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 LIVEKINDLY'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/livekindly/"
title="LIVEKINDLY on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/livekindly.svg"
alt="LIVEKINDLY Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/livekindly/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/livekindly/"
title="LIVEKINDLY on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/livekindly/card.svg"
alt="LIVEKINDLY 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 LIVEKINDLY
Each block below is one kind of artifact we hold for LIVEKINDLY. 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 13
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.
LIVEKINDLY MCP Server (WordPress MCP Adapter)
A Model Context Protocol server advertised in the thelivekindlyco.com WordPress REST route index under the "mcp" namespace, with two endpoints — mcp-adapter-default-server and m...
LIVEKINDLY Brands API
The Brands API from LIVEKINDLY — 2 operation(s) for brands.
LIVEKINDLY Careers API
The Careers API from LIVEKINDLY — 2 operation(s) for careers.
LIVEKINDLY Comments API
The Comments API from LIVEKINDLY — 2 operation(s) for comments.
LIVEKINDLY Discovery API
The Discovery API from LIVEKINDLY — 7 operation(s) for discovery.
LIVEKINDLY Media API
The Media API from LIVEKINDLY — 4 operation(s) for media.
LIVEKINDLY Pages API
The Pages API from LIVEKINDLY — 4 operation(s) for pages.
LIVEKINDLY Partners API
The Partners API from LIVEKINDLY — 2 operation(s) for partners.
LIVEKINDLY Posts API
The Posts API from LIVEKINDLY — 4 operation(s) for posts.
LIVEKINDLY Search API
The Search API from LIVEKINDLY — 1 operation(s) for search.
LIVEKINDLY Settings API
The Settings API from LIVEKINDLY — 1 operation(s) for settings.
LIVEKINDLY Taxonomy API
The Taxonomy API from LIVEKINDLY — 6 operation(s) for taxonomy.
LIVEKINDLY Users API
The Users API from LIVEKINDLY — 6 operation(s) for users.
Scroll within the panel for all 13 ·
Open Collections 13
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 COLLECTIONLIVEKINDLY Content API (WordPress REST wp/v2) Brands API
OPEN COLLECTIONLIVEKINDLY Content API (WordPress REST wp/v2) Careers API
OPEN COLLECTIONLIVEKINDLY Content API (WordPress REST wp/v2) Comments API
OPEN COLLECTIONLIVEKINDLY Content API (WordPress REST wp/v2) Discovery API
OPEN COLLECTIONLIVEKINDLY Content API (WordPress REST wp/v2) Media API
OPEN COLLECTIONLIVEKINDLY Content API (WordPress REST wp/v2) Pages API
OPEN COLLECTIONLIVEKINDLY Content API (WordPress REST wp/v2) Partners API
OPEN COLLECTIONLIVEKINDLY Content API (WordPress REST wp/v2) Posts API
OPEN COLLECTIONLIVEKINDLY Content API (WordPress REST wp/v2) Search API
OPEN COLLECTIONLIVEKINDLY Content API (WordPress REST wp/v2) Settings API
OPEN COLLECTIONLIVEKINDLY Content API (WordPress REST wp/v2) Taxonomy API
OPEN COLLECTIONLIVEKINDLY Content API (WordPress REST wp/v2) Users API
OPEN COLLECTIONScroll within the panel for all 13 ·
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.
livekindly-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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 LIVEKINDLY — 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 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
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 2
Pricing, plans, and the legal terms of use
Company 7
The organization behind the API
Scroll within the panel for all 7 ·
Other 7
Properties that don't map to a standard resource type
Scroll within the panel for all 7 ·
← All providers · Data indexed from github.com/api-evangelist/livekindly · machine-readable index on apis.io
This is an independent, third-party profile of LIVEKINDLY, 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.