How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Lily AI website screenshot

Lily AI

Lily AI, Inc. is a retail product-intelligence company whose platform, Lily Max, enriches e-commerce product catalogs so that products are legible to advertising platforms, search engines, onsite search, and AI shopping agents. Agents identify gaps in a retailer's product data, generate consumer-centric attributes and copy, run controlled tests against a holdout, and deploy the winning enrichments across Google Merchant Center feeds, Meta Commerce Manager catalogs, AI discovery and agentic commerce surfaces, and onsite PDP, search, and faceting. Lily AI sells to enterprise retailers, brands, and agencies and positions itself as a layer over the existing commerce stack rather than a replacement for a PIM or feed manager. The company raised a $25M Series B with participation from Canaan Partners, Conductive Ventures, Sorenson Ventures, and NEA. Lily AI operates no developer program: there is no developer portal, no published API reference, no SDK, no GitHub organization, and no self-service credential path, and the platform is sold and onboarded through enterprise sales. It does, however, publicly serve the OpenAPI 3.0.0 contract for the LilyApp middleware that backs its customer application at app.lily.ai — 63 paths and 100 operations behind an Azure AD B2C bearer JWT, with a public Swagger UI. That contract is captured here as the company's only machine-readable API surface.

agent aware

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.

Kin Score

API Evangelist profiles Lily AI the way a machine reads it — 26 machine-readable artifacts across 2 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 — Lily AI scores 40.1/100 (developing), with a separate agent-readiness read of 24/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Composite quality — 40.1/100 · developing
Contract Quality 11.4 / 25
Access Clarity 9.5 / 20
Discoverability 7.6 / 10
Lily AI Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Lily AI'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/lily-ai/"
   title="Lily AI on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/lily-ai.svg"
       alt="Lily AI Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Lily AI

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

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.

Lily AI Auth API

The Auth API from Lily AI — 5 operation(s) for auth.

Lily AI Batch API

The Batch API from Lily AI — 1 operation(s) for batch.

Lily AI Config API

The Config API from Lily AI — 6 operation(s) for config.

Lily AI Enrichment Platform Proxy API

The Enrichment Platform Proxy API from Lily AI — 1 operation(s) for enrichment platform proxy.

Lily AI Faqs API

The Faqs API from Lily AI — 1 operation(s) for faqs.

Lily AI Health API

The Health API from Lily AI — 1 operation(s) for health.

Lily AI Integration API

The Integration API from Lily AI — 2 operation(s) for integration.

Lily AI LilyApp API Nest Based Application API

The LilyApp API Nest Based Application API from Lily AI — 1 operation(s) for lilyapp api nest based application.

Lily AI Metrics API

The Metrics API from Lily AI — 1 operation(s) for metrics.

Lily AI Mock Data API

The Mock Data API from Lily AI — 7 operation(s) for mock data.

Lily AI Pi Api Proxy API

The Pi Api Proxy API from Lily AI — 1 operation(s) for pi api proxy.

Lily AI Pi Config Proxy API

The Pi Config Proxy API from Lily AI — 1 operation(s) for pi config proxy.

Lily AI Pi Connector Proxy API

The Pi Connector Proxy API from Lily AI — 1 operation(s) for pi connector proxy.

Lily AI Productcopy API

The Productcopy API from Lily AI — 11 operation(s) for productcopy.

Lily AI Productcopy V2 API

The ProductcopyV2 API from Lily AI — 6 operation(s) for productcopyv2.

Lily AI Products API

The Products API from Lily AI — 1 operation(s) for products.

Lily AI Search API

The Search API from Lily AI — 11 operation(s) for search.

Lily AI Subsidiary API

The Subsidiary API from Lily AI — 2 operation(s) for subsidiary.

Lily AI Superset API

The Superset API from Lily AI — 2 operation(s) for superset.

Lily AI Tce Api Proxy API

The Tce Api Proxy API from Lily AI — 1 operation(s) for tce api proxy.

Scroll within the panel for all 20 ·

Open Collections 1

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).

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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.

Published pricing tiers and plan structures.

Lily Ai Plans Pricing

0 plans

PLANS

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.

Lily Ai Rate Limits

3 limits

RATE LIMITS

Security Posture 3

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.

Lily Ai Authentication

http/openIdConnect · 2 schemes

SECURITY

Lily Ai Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Lily Ai Trust Center

trust center published

SECURITY

Resources

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

Get Started 1

Portal, sign-up, and the first successful call

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Other 3

Properties that don't map to a standard resource type

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

Where this information came from

This is an independent, third-party profile of Lily AI, 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.