Savvly
Savvly offers the Longevity Benefit, an SEC-registered security (NOT an annuity) that provides longevity protection by investing contributions into a low-cost S&P 500 index ETF and paying structured milestone cash payouts at ages 80, 85, 90, and 95. When participants withdraw before a milestone, their allocation transfers to remaining investors — a longevity-pool / mortality-credit mechanism that can lift returns above pure market performance. Accounts are portable across jobs and require no health screening. Savvly publishes an open, rate-limited Public API (OpenAPI 3.1) for product information, eligibility, FAQ, comparisons, and retirement/lump-sum/monthly projections, plus a first-party MCP server, an llms.txt, an ai-plugin manifest, and an RFC 9727 api-catalog for agent-native consumption. Backed by Techstars.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Savvly the way a machine reads it — 6 machine-readable artifacts across 3 APIs, 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 — Savvly scores 30.4/100 (thin), with a separate agent-readiness read of 60/100 (agent ready). 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 Savvly
Each block below is one kind of artifact we hold for Savvly. 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.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Savvly Comparisons API
The Comparisons API from Savvly — 2 operation(s) for comparisons.
Savvly Product API
The Product API from Savvly — 6 operation(s) for product.
Savvly Projections API
The Projections API from Savvly — 4 operation(s) for projections.
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
savvly-mcp.yml
MCP SERVERSecurity 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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Savvly — 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.
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Company 1
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/savvly · machine-readable index on apis.io