Tomo
Tomo is a consumer "personal AI" application that lives in your text messages: users tell Tomo about their life, goals, problems, and aspirations over SMS, and the AI assistant learns those goals and guides them toward achieving them through ongoing text-based conversation. Backed by Bain Capital Ventures and Ribbit Capital, Tomo operates in the AI-apps sector as a mobile-first consumer product rather than a developer platform. As of this enrichment pass the company publishes a marketing site (tomo.ai) with About, Careers, Privacy, Terms, and Login pages but no public developer program: no API documentation, OpenAPI/AsyncAPI specification, SDKs, CLI, MCP server, llms.txt, or .well-known discovery endpoints were found. This profile is maintained for API Evangelist network completeness.
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.
Tomo is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
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 — Tomo 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
Resources
Every other property we hold for Tomo — 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
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Tomo is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/tomo · machine-readable index on apis.io