Lexius
Lexius is a Y Combinator-backed AI loss-prevention platform that turns a retailer's existing security cameras into proactive, revenue-protecting systems. It detects shoplifting in real time (concealment, product sweeping, known-offender entry), sends instant mobile alerts with video clips, and offers traceback search — natural-language search across every connected camera feed. Lexius also builds case files for law enforcement, flags known offenders chain-wide, and detects slip-and-fall events for liability protection. It connects to existing NVR/VMS systems from any brand, including Hikvision, Axis, Dahua, Hanwha, Bosch, Honeywell, Uniview, Lorex, LTS, Avigilon, and Genetec, and is typically deployed remotely in under 24 hours without replacing hardware. Lexius publishes no public developer API, SDK, or documentation surface as of this profile; it is delivered as a hosted dashboard plus camera/NVR integrations.
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 Lexius 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 — Lexius scores 13.6/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 Lexius
Each block below is one kind of artifact we hold for Lexius. 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 Lexius — 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
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 1
Authentication, authorization, and security posture
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/lexius · machine-readable index on apis.io