LIMRA
LIMRA is a member-based research and trade association for the life insurance and financial services industry, operating alongside LOMA under the LL Global umbrella. It provides industry research, sales and market data, benchmarking, experience studies, and professional development to member companies - primarily life insurers, annuity providers, and workplace benefits carriers. LIMRA does not operate a public developer API or developer portal. Its research, benchmarking, and experience-study data are delivered through the member-gated LIMRA.com portal, reports, and consortium programs rather than a programmatic interface. LIMRA's most API-relevant offering is the LIMRA Data Exchange (LDEx) Standards - free, industry-developed data exchange standards for workplace benefits (benefits enrollment management, benefits configuration management, and evidence of insurability) that define payloads in XML and JSON and, in recent releases, REST endpoints specified in OpenAPI 3.1. LDEx is a specification that insurance carriers and benefits administration platforms implement between themselves; LIMRA publishes the standard (registration required to download, membership not required) but does not host any live endpoints. This entry is an honest documentation stub kept for catalog completeness; it will be updated if LIMRA ever ships a hosted public API.
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 LIMRA 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 — LIMRA scores 12.7/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 LIMRA
Each block below is one kind of artifact we hold for LIMRA. 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.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Limra Plans Pricing
PLANSSecurity 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 LIMRA — 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 2
Reference material describing how the API behaves
Access & Security 1
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/limra · machine-readable index on apis.io