Lance
Lance (Lance AI, Inc.) is a Y Combinator Winter 2026 company building autonomous AI agents for hotel operations. Its platform handles guest interactions and back-of-house coordination end to end: a Receptionist agent answers guest calls, SMS, email, and hotel messaging platforms 24/7 in multiple languages, resolving questions and routing service requests; a Sales agent responds to booking inquiries and RFPs, qualifies leads, and follows up on opportunities; and Lance Pad is a tablet-based coordination surface that replaces walkie-talkies and tracks guest requests, housekeeping, work orders, and scheduling in real time. Lance reports use across brands including Marriott, Hilton, and Hyatt and more than 50 hotels, citing an 89% call success rate and a 30%+ reduction in front-desk call volume. Architecturally the company is notable for deliberately avoiding integration APIs: it uses computer-use and computer-vision agents to drive legacy property management, task, and reservation systems through their user interfaces rather than through vendor APIs. Lance is surfaced here as a portfolio company of Y Combinator. It publishes no public developer API, OpenAPI definition, SDKs, developer portal, or documentation surface.
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 Lance 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 — Lance 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 Lance
Each block below is one kind of artifact we hold for Lance. 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 Lance — 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 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 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/lance · machine-readable index on apis.io