Claim.Revolution

Claim.Revolution is a medical claims clearinghouse for providers, offering a platform that enables healthcare teams to submit cleaner claims, verify eligibility, track claim status, and manage revenue cycles. It supports high‑volume batch submissions, complex payer environments, and integrates with EMR systems like OpenEMR and Healthie. The service aims to reduce denials, accelerate payments, and provide real‑time insights into claim processing for clinics, billing companies, and tribal health programs.

Claim.Revolution is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Healthcare, Claims, API, and Billing.

The Claim.Revolution catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Claim.Revolution’s developer surface includes changelog, documentation, API reference, getting-started guide, support, engineering blog, pricing, and 17 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

42.3/100 developing Agent 21/100 agent aware Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

2 APIs

Company Healthcare ClaimsAPIBilling

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 42.3/100 · developing

Contract Quality 4.5 / 21

Developer Ergonomics 7.7 / 17

Access Clarity 13.4 / 17

Operational Transparency 2.9 / 11

Contract Governance 2.0 / 10

Discoverability 4.9 / 9

Regulatory Posture 3.2 / 15

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 4 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

Regulatory Posture applies to this provider. Its tags matched the Insurance regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/claimrev/"><img src="https://apis.io/badge/claimrev/card.svg" alt="Claim.Revolution on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)

10 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 21.4 — up to +19.7 composite points
Developer Ergonomics scores 45.2 — up to +11.0 composite points
Operational Transparency scores 26.3 — up to +9.6 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/claimrev/apis.yml: open an issue on github.com/api-evangelist/claimrev to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

ClaimRev API

REST API for medical claims processing, as documented in the developer portal.

Claim.Revolution API

Claim.Revolution API as documented publicly: 40 operations. Contract generated from the documentation by API Evangelist (2026-10-27); not the provider's own document.

Pricing Plans 1

Published pricing tiers and plan structures.

Claimrev Plans Pricing

7 plans

PLANS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Claimrev Context

6 classes · 1 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Claim.Revolution API Rules

8 rules · 7 errors 1 info

SPECTRAL

JSON Schema 9

Standalone JSON Schema definitions for this provider's data models.

GetApiAimodelconfigV1ResolvemodelResponse

1 properties

JSON SCHEMA

PostApiAttachment275V1IdStatusResponse

SOC 2, HIPAA, GDPR

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

Conformance

Access & Security 4

Authentication, authorization, and security posture

Compliance

Security

TrustCenter

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

ChangeLog

ChangeLog

Support

Support

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: claimrev
name: Claim.Revolution
image: https://www.claimrev.com/wp-content/uploads/2024/02/Stacked-Logo-e1722441851106.png
description: Claim.Revolution is a medical claims clearinghouse for providers, offering a platform that enables healthcare
  teams to submit cleaner claims, verify eligibility, track claim status, and manage revenue cycles. It supports high‑volume
  batch submissions, complex payer environments, and integrates with EMR systems like OpenEMR and Healthie. The service aims
  to reduce denials, accelerate payments, and provide real‑time insights into claim processing for clinics, billing companies,
  and tribal health programs.
url: https://raw.githubusercontent.com/api-evangelist/claimrev/refs/heads/main/apis.yml
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-27 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-26'
modified: '2026-10-26'
tags:
- Company
- Healthcare
- Claims
- API
- Billing
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/claimrev-plans-pricing.yml
- type: Spectral
  url: rules/claimrev-rules.yml
- type: JSONLD
  url: json-ld/claimrev-context.jsonld
- type: Vocabulary
  url: vocabulary/claimrev-vocabulary.yml
- type: DataModel
  url: data-model/claimrev-data-model.yml
- type: Compliance
  url: https://www.claimrev.com/security/
- type: Conformance
  url: conformance/claimrev-conformance.yml
- type: LLMsTxt
  url: llms/claimrev-llms.txt
- type: Hosts
  url: hosts/claimrev-hosts.yml
- type: Vendors
  url: vendors/claimrev-vendors.yml
- type: Security
  url: https://www.claimrev.com/security/
- type: ChangeLog
  url: https://developer.claimrev.com/changelog
- type: TrustCenter
  url: security/claimrev-trust-center.yml
- type: DomainSecurity
  url: security/claimrev-domain-security.yml
- type: Website
  url: https://www.claimrev.com/
- type: DeveloperPortal
  url: https://developer.claimrev.com/
- type: Documentation
  url: https://developer.claimrev.com/
- type: APIReference
  url: https://developer.claimrev.com/reference/
- type: GettingStarted
  url: https://developer.claimrev.com/quickstart/
- type: Support
  url: https://www.claimrev.com/contact-us/
- type: Blog
  url: https://www.claimrev.com/blog/
- type: Pricing
  url: https://www.claimrev.com/pricing/
- type: TermsOfService
  url: https://www.claimrev.com/terms-and-conditions/
- type: PrivacyPolicy
  url: https://www.claimrev.com/privacypolicy/
apis:
- name: ClaimRev API
  description: REST API for medical claims processing, as documented in the developer portal.
  humanURL: https://developer.claimrev.com/reference
  baseURL: null
  aid: claimrev:claimrev-api-2
- aid: claimrev:claimrev-api
  name: Claim.Revolution API
  description: 'Claim.Revolution API as documented publicly: 40 operations. Contract generated from the documentation by API
    Evangelist (2026-10-27);

    not the provider''s own document.'
  humanURL: https://developer.claimrev.com/reference/post-api-inputfile-v-1
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/claimrev-openapi-generated.yml
    x-provenance: generated
  - type: JSONSchema
    url: json-schema/claimrev-post-api-attachment275-v1-id-status-response-schema.json
  - type: JSONSchema
    url: json-schema/claimrev-post-api-module-v1-checkversion-response-schema.json
  - type: JSONSchema
    url: json-schema/claimrev-post-api-claimview-v1-searchclaims-response-schema.json
  - type: JSONSchema
    url: json-schema/claimrev-post-api-ocrreview-v1-flagocrreview-response-schema.json
  - type: JSONSchema
    url: json-schema/claimrev-post-api-tickets-v1-search-response-schema.json
  - type: JSONSchema
    url: json-schema/claimrev-get-api-aimodelconfig-v1-resolvemodel-response-schema.json
x-submission-probe: 301 (-> https://www.claimrev.com) 2026-10-25
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: Developer portal provides HTML reference pages but no OpenAPI/AsyncAPI/GraphQL spec is publicly available.
  evidence:
  - url: https://developer.claimrev.com/reference
    status: 200
  checked: '2026-10-27'
x-enrichment:
  date: '2026-10-27'
  status: enriched
  artifacts_added: 24
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Claim.Revolution API — frequently asked questions

Does Claim.Revolution have an API?

Yes. APIs.io lists 2 APIs from Claim.Revolution, including ClaimRev API and Claim.Revolution API.

Is there an OpenAPI specification for the Claim.Revolution API?

Yes. APIs.io indexes 1 OpenAPI specification for Claim.Revolution, each linked for download from this page.

How much does the Claim.Revolution API cost?

APIs.io lists 7 pricing plans for Claim.Revolution, with each plan's price, limits and inclusions under Pricing Plans on this page.

Is the Claim.Revolution API ready for AI agents?

Claim.Revolution has a Kin Score of 42.3 out of 100 (developing) and an Agent Readiness score of 20.6 (agent-aware), scored by API Evangelist on 2026-10-31.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/claimrev"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/claimrev/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/claimrev/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.