EIS Group
EIS Group (EIS Ltd) is a United States core-systems vendor for insurance, founded in 2008 out of Exigen Insurance Solutions and headquartered in San Francisco, California. EIS sells the EIS Platform and EIS OneSuite — a cloud-native, microservices core suite covering customer management, policy administration, billing, and claims — across group benefits, property and casualty / general, protection, life and annuities, and pet insurance. EIS markets itself as API-first and claims thousands of open REST APIs (1,100 digital APIs announced in 2019, 9,000+ claimed for OneSuite) fronted by the EIS DXP API middleware, but none of that surface is public. There is no self-serve developer portal on eisgroup.com; the documentation host docs.eisgroup.com answers HTTP 401 behind an HTTP Basic realm named "EIS Group Users", so the entire API reference is a customer/partner login wall. No OpenAPI, Swagger, GraphQL, AsyncAPI, or public Postman collection could be retrieved. The only public code EIS ships is two open-source GitHub repositories (kraken-rules, ui-render), which are libraries rather than APIs. ACORD is attested only indirectly — an analyst evaluation hosted on eisgroup.com states the system integrates using "web services, APIs, RESTful APIs, ACORD and certified ACORD" — with no ACORD artifacts, AL3 mappings, or IVANS/agency-download detail published. What EIS does publish is a substantial certification posture — a certified MACH Alliance membership (Microservices, API-first, Cloud-native SaaS, Headless) and a full ISO stack covering 27001, 27701, 22301, 27017, 27018, 27035-1, 12207, 15288, 25000 and ISO/IEC 42001, which EIS announced in June 2025 as the first cloud-native insurance core platform provider to obtain. One first-party package is public, eis-ui-render on npm. This is the canonical United States core-systems posture — the APIs exist and are sold, but they are reachable only through a licensed implementation.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles EIS Group 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 — EIS Group scores 21.7/100 (emerging), 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 EIS Group
Each block below is one kind of artifact we hold for EIS Group. 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 EIS Group — 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 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 7
The organization behind the API
Scroll within the panel for all 7 ·
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/eis-group · machine-readable index on apis.io