Lily Camera
The domain lily.camera currently serves "Lily Camera", a consumer-facing marketplace that connects clients with certified drone pilots for aerial photography and videography across real estate, events, agriculture, construction, and media production. It is a client-rendered single-page application: every requested path returns the same HTML shell, and the routes defined in its JavaScript bundle cover browsing pilots and drones, comparisons, bookings, messaging, a pilot dashboard, and a drone raffle. There is no public API, no developer portal, no documentation, no OpenAPI or other machine-readable specification, no SDKs, and no /.well-known discovery surface. The site is built on Lovable (GPT Engineer), monetized with Google AdSense, and backed by a hosted Supabase project. No API artifacts could be harvested because the provider publishes none.
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.
API Evangelist profiles Lily Camera 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 — Lily Camera scores 10.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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Lily Camera
Each block below is one kind of artifact we hold for Lily Camera. 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.
Resources
Every other property we hold for Lily Camera — 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 2
Portal, sign-up, and the first successful call
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/lily · machine-readable index on apis.io