Lato
Lato (LATO Labs) is a San Francisco company building an agent-native research and simulation platform for investors. Its agents source and conduct hundreds of voice interviews with verified domain experts and customers in any language, each returned with a recording, transcript and thematic analysis, then combine those interviews with thousands of documents from public sources and a fund's own proprietary knowledge into a single commercial study. The study becomes a live simulation of the market that analysts can question and run scenarios against to predict where a market is headed. Investors use Lato for commercial due diligence, expert interviews, market sizing, competitive mapping, customer interviews, pricing studies, deal sourcing, inbound screening and portfolio value creation, compressing research that traditionally costs hundreds of thousands of dollars and takes weeks into hours. The product integrates with the tools investment teams already run on, including Outlook, SharePoint, Gmail, Google Drive, Slack, Teams, Excel, Affinity, Attio, Harmonic and Granola. Lato was founded by Tymek Staniszewski (CEO) and Tien Chu (CTO), is backed by Y Combinator (Summer 2026), and builds on Anthropic, OpenAI and ElevenLabs. As of this profile Lato publishes no public developer API, documentation or SDKs; the company surface is captured here for discovery and the repository will be re-enriched when a developer program appears.
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 Lato the way a machine reads it — 2 machine-readable artifacts, 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 — Lato scores 13.2/100 (minimal), with a separate agent-readiness read of 7/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 Lato
Each block below is one kind of artifact we hold for Lato. 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 2
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 Lato — 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
Access & Security 4
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
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/lato · machine-readable index on apis.io