How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Olive AI website screenshot

Olive AI

Olive AI was a Columbus, Ohio healthcare automation company founded in 2012 by Sean Lane (originally as CrossChx, rebranded to Olive in 2017). The company built robotic process automation (RPA), AI, and workflow tooling aimed at the healthcare revenue cycle — including a "digital workforce" marketed as "Olive" that automated repetitive administrative tasks in hospitals and health systems. Olive's portfolio centered on clearinghouse and patient access automation, prior authorization automation, claims status checks, eligibility verification, and process mining for revenue-cycle optimization. At its peak Olive raised more than $900M and reached a $4B valuation, but a series of strategic missteps, layoffs, and cash burn forced an orderly wind-down. In late 2023 Olive sold its clearinghouse and patient access business to Waystar, and in early 2024 sold its prior authorization business to Humata Health, then ceased operations. The Olive AI brand is no longer active and there is no public developer API, SDK, or open-source release; surviving capabilities live on inside Waystar and Humata Health.

human only

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.

Kin Score

API Evangelist profiles Olive AI the way a machine reads it — 3 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 — Olive AI scores 7.0/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Olive AI Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Olive AI's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/olive-ai/"
   title="Olive AI on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/olive-ai.svg"
       alt="Olive AI Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Olive AI

Each block below is one kind of artifact we hold for Olive AI. 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 3

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.

Olive Ai Domain Security

TLSv1.3 · DMARC

SECURITY

Olive Ai Vulnerability Disclosure

disclosure policy published

SECURITY

Olive Ai Trust Center

SOC 2, PCI DSS, HIPAA

SECURITY

Resources

Every other property we hold for Olive AI — 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.

Access & Security 3

Authentication, authorization, and security posture

← All providers · Data indexed from github.com/api-evangelist/olive-ai · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Olive AI, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.