Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Apeel website screenshot

Apeel

Apeel Sciences is a food technology company headquartered in Santa Barbara, California that develops plant-based protective coatings which extend the shelf life of fresh fruits and vegetables. The company uses food-grade ingredients derived from the peels, pulp, and seeds of plants to create a thin, edible layer that reinforces produce's natural peel, slowing water loss and oxidation. This extends peak taste, juiciness, and nutrient retention while reducing reliance on refrigeration, waxes, pesticides, and plastic packaging across the fresh-produce supply chain. Apeel positions itself as a sustainability and food-waste leader, reporting that since 2021 its technology has prevented millions of pieces of fruit from spoiling, avoided tens of thousands of metric tons of CO2-equivalent emissions, and conserved billions of liters of water. Its products have undergone regulatory review in the United States, European Union, and other markets. Apeel is a portfolio company of Andreessen Horowitz (a16z) and was added to the API Evangelist network as a venture-portfolio lead. It publishes no public developer API, developer portal, or machine-readable API specification as of this profile.

human only

Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.

Kin Score

API Evangelist profiles Apeel the way a machine reads it — 1 machine-readable artifact, 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 — Apeel scores 12.3/100 (minimal), with a separate agent-readiness read of 0/100 (human only). 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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 12.3/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 1.3 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Apeel

Each block below is one kind of artifact we hold for Apeel. 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.

Security Posture 1

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.

Apeel Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for Apeel — 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.

Access & Security 1

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 2

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/apeel · machine-readable index on apis.io