Aclaimant

Aclaimant is a Chicago-based risk management information system (RMIS) used by policyholders, insurance brokers, carriers and third-party administrators to run incident reporting and first notice of loss (FNOL), claims management and analytics, safety and loss control, OSHA logs, policy management, and assets and exposures from one workflow platform. Its machine-readable surface is the Aclaimant Platform API — a Swagger 2.0 contract published at api.aclaimant.com/api with a live Swagger UI console — which lets integrators create and upsert answer bundles, incidents, claims, claim reports, events, files, companies, policies, policy programs, exposures and exposure summations, including bulk jobs with a status endpoint. A separate Partner / Third-party API at api.aclaimant.com/partner lets carriers, TPAs and brokers acknowledge claim receipt and post loss-run claim financial updates back into Aclaimant.

Aclaimant publishes 8 API contracts indexed on the APIs.io network, including Answers API, Bulk API, Companies API, and 5 more. Tagged areas include Risk Management, Insurance, Claims Management, Incident Management, and Safety.

The Aclaimant catalog on APIs.io includes 1 Spectral governance ruleset.

Aclaimant’s developer surface includes documentation, API reference, support, engineering blog, pricing, authentication, changelog, and 29 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

57.2/100 strong ▬ flat Agent 27/100 agent aware Front door AI 2/6 trace Heartbeat 40/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessEnterprise

1 published contract 3 Agent Skills

Risk Management Insurance Claims Management Incident Management SafetyRMISWorkers Compensation OSHAEnterprise Risk ManagementInsurtech

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Enterprise Risk Management

BC-120

Policiespolicy-programs

POST /v2/policy POST /v2/program

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 57.2/100 · strong

Contract Quality 7.6 / 19

Developer Ergonomics 8.1 / 15

Access Clarity 12.8 / 15

Operational Transparency 4.4 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 4.7 / 15

Create-or-Update Ergonomics 2.2 / 10

Agent readiness — 27/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 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

MCP Tool Quality 6 / 6

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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/aclaimant/"><img src="https://apis.io/badge/aclaimant/card.svg" alt="Aclaimant 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):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks

6 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 40.6 — up to +14.9 composite points
Contract Governance scores 18.2 — up to +9.8 composite points
Developer Ergonomics scores 54.2 — up to +9.2 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/aclaimant/apis.yml: open an issue on github.com/api-evangelist/aclaimant 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 →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Insurance and Insurtech	builds-on	34.5 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 8

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

Aclaimant Partner / Third-party API

Callback API for TPAs, carriers, brokers and other Aclaimant partners working claims on behalf of an Aclaimant customer. Base URL https://api.aclaimant.com/partner, bearer-token...

Aclaimant Answers API

The answers API from Aclaimant — 15 operation(s) for answers.

Aclaimant Bulk API

The bulk API from Aclaimant — 8 operation(s) for bulk.

Aclaimant Companies API

The companies API from Aclaimant — 1 operation(s) for companies.

Aclaimant Exposures API

The exposures API from Aclaimant — 2 operation(s) for exposures.

Aclaimant Incidents API

The incidents API from Aclaimant — 1 operation(s) for incidents.

Aclaimant Policies API

The policies API from Aclaimant — 2 operation(s) for policies.

Aclaimant Policy Programs API

The policy-programs API from Aclaimant — 2 operation(s) for policy-programs.

Scroll for all 8

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

aclaimant-bulk-policy-load

AGENT SKILL

aclaimant-incident-to-claim

AGENT SKILL

aclaimant-partner-loss-run

AGENT SKILL

Aclaimant API pricing

Prices published by Aclaimant, read 2026-10-28 from www.aclaimant.com/plans-and-pricing.

Plan	Price
RMIS Basics	See a demo Includes: Incident Management & Claim Submission; add-on: OSHA Logs
RMIS Core	See a demo Includes: Everything in RMIS Basics plus Claim Management & Analytics, Safety Reporting; add-ons: SSO, Claim D
RMIS Enterprise	See a demo Includes: Everything in Basics and Core plus Policy Management, Assets and Exposures; add-ons: AI Insights, Be

Plan details, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

Aclaimant Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Aclaimant Rate Limits

0 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Aclaimant

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Aclaimant Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Aclaimant API Rules

44 rules · 40 errors 3 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Aclaimant Platform Api Overlay

28 actions · documentation

DERIVED

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Aclaimant Authentication

apiKey/http-bearer · 2 schemes

SECURITY

Aclaimant Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Aclaimant Vulnerability Disclosure

contact published

SECURITY

Aclaimant Trust Center

SOC 2, GDPR, Penetration test report

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Login

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

Conformance

ErrorCatalog

Lifecycle

DataModel

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

Access & Security 7

Authentication, authorization, and security posture

TrustCenter

TrustCenter

Security

Compliance

Authentication

DomainSecurity

VulnerabilityDisclosure

VulnerabilityDisclosure

Scroll for all 7

Operate 5

Status, limits, changes, and where to get help

Support

StatusPage

ChangeLog

ChangeLog

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

Plans

Company 3

The organization behind the API

Website

Website

Blog

Blog

BlogRSS

BlogRSS

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: aclaimant
name: Aclaimant
description: Aclaimant is a Chicago-based risk management information system (RMIS) used by policyholders, insurance brokers,
  carriers and third-party administrators to run incident reporting and first notice of loss (FNOL), claims management and
  analytics, safety and loss control, OSHA logs, policy management, and assets and exposures from one workflow platform. Its
  machine-readable surface is the Aclaimant Platform API — a Swagger 2.0 contract published at api.aclaimant.com/api with
  a live Swagger UI console — which lets integrators create and upsert answer bundles, incidents, claims, claim reports, events,
  files, companies, policies, policy programs, exposures and exposure summations, including bulk jobs with a status endpoint.
  A separate Partner / Third-party API at api.aclaimant.com/partner lets carriers, TPAs and brokers acknowledge claim receipt
  and post loss-run claim financial updates back into Aclaimant.
url: https://raw.githubusercontent.com/api-evangelist/aclaimant/refs/heads/main/apis.yml
accessModel:
  pricing: enterprise
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Enterprise
  confidence: high
  source:
  - plans
  - authentication
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://www.aclaimant.com/hubfs/Aclaimant_February2020/Images/favicon.ico
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-09-06'
modified: '2026-09-06'
position: Producing
tags:
- Risk Management
- Insurance
- Claims Management
- Incident Management
- Safety
- RMIS
- Workers Compensation
- OSHA
- Enterprise Risk Management
- Insurtech
tags_raw:
- risk-management
- insurance
- claims-management
- incident-management
- safety
- rmis
- workers-compensation
- osha
- enterprise-risk-management
- insurtech
apis:
- name: Aclaimant Partner / Third-party API
  description: Callback API for TPAs, carriers, brokers and other Aclaimant partners working claims on behalf of an Aclaimant
    customer. Base URL https://api.aclaimant.com/partner, bearer-token authorization issued by Aclaimant. Two documented endpoints
    - POST /claims/{claim-id}/receipt to acknowledge a submitted claim with the partner's own claim number and receipt status,
    and PUT /claims/{claim-id} to post claim status and the latest loss-run claim-report financials (medical, indemnity, expense,
    legal, vocational, recovery, general, property-damage, cargo-loss, cargo-damage) back into Aclaimant. Documented on the
    public developer portal; no machine-readable contract is published for this surface.
  humanURL: https://developer.aclaimant.com/partner/index.html
  baseURL: https://api.aclaimant.com/partner
  tags:
  - Claims Management
  - Insurance
  - Risk Management
  tags_raw:
  - claims-management
  - insurance
  - risk-management
  properties:
  - type: Documentation
    url: https://developer.aclaimant.com/partner/index.html
  - type: APIReference
    url: https://developer.aclaimant.com/partner/index.html
  - type: ErrorCatalog
    url: errors/aclaimant-problem-types.yml
  - type: Authentication
    url: authentication/aclaimant-authentication.yml
- aid: aclaimant:aclaimant-answers-api
  name: Aclaimant Answers API
  description: The answers API from Aclaimant — 15 operation(s) for answers.
  humanURL: https://api.aclaimant.com/api/index.html
  baseURL: https://api.aclaimant.com/api
  tags:
  - Answers
  tags_raw:
  - answers
  properties:
  - type: OpenAPI
    url: openapi/aclaimant-answers-api-openapi.yml
  - type: APIReference
    url: https://api.aclaimant.com/api/index.html
  - type: Authentication
    url: authentication/aclaimant-authentication.yml
  - type: Conventions
    url: conventions/aclaimant-conventions.yml
  - type: DataModel
    url: data-model/aclaimant-data-model.yml
  - type: ErrorCatalog
    url: errors/aclaimant-problem-types.yml
  - type: Sandbox
    url: sandbox/aclaimant-sandbox.yml
- aid: aclaimant:aclaimant-bulk-api
  name: Aclaimant Bulk API
  description: The bulk API from Aclaimant — 8 operation(s) for bulk.
  humanURL: https://api.aclaimant.com/api/index.html
  baseURL: https://api.aclaimant.com/api
  tags:
  - Bulk
  tags_raw:
  - bulk
  properties:
  - type: OpenAPI
    url: openapi/aclaimant-bulk-api-openapi.yml
  - type: APIReference
    url: https://api.aclaimant.com/api/index.html
  - type: Authentication
    url: authentication/aclaimant-authentication.yml
  - type: Conventions
    url: conventions/aclaimant-conventions.yml
  - type: DataModel
    url: data-model/aclaimant-data-model.yml
  - type: ErrorCatalog
    url: errors/aclaimant-problem-types.yml
  - type: Sandbox
    url: sandbox/aclaimant-sandbox.yml
- aid: aclaimant:aclaimant-companies-api
  name: Aclaimant Companies API
  description: The companies API from Aclaimant — 1 operation(s) for companies.
  humanURL: https://api.aclaimant.com/api/index.html
  baseURL: https://api.aclaimant.com/api
  tags:
  - Companies
  tags_raw:
  - companies
  properties:
  - type: OpenAPI
    url: openapi/aclaimant-companies-api-openapi.yml
  - type: APIReference
    url: https://api.aclaimant.com/api/index.html
  - type: Authentication
    url: authentication/aclaimant-authentication.yml
  - type: Conventions
    url: conventions/aclaimant-conventions.yml
  - type: DataModel
    url: data-model/aclaimant-data-model.yml
  - type: ErrorCatalog
    url: errors/aclaimant-problem-types.yml
  - type: Sandbox
    url: sandbox/aclaimant-sandbox.yml
- aid: aclaimant:aclaimant-exposures-api
  name: Aclaimant Exposures API
  description: The exposures API from Aclaimant — 2 operation(s) for exposures.
  humanURL: https://api.aclaimant.com/api/index.html
  baseURL: https://api.aclaimant.com/api
  tags:
  - Exposures
  tags_raw:
  - exposures
  properties:
  - type: OpenAPI
    url: openapi/aclaimant-exposures-api-openapi.yml
  - type: APIReference
    url: https://api.aclaimant.com/api/index.html
  - type: Authentication
    url: authentication/aclaimant-authentication.yml
  - type: Conventions
    url: conventions/aclaimant-conventions.yml
  - type: DataModel
    url: data-model/aclaimant-data-model.yml
  - type: ErrorCatalog
    url: errors/aclaimant-problem-types.yml
  - type: Sandbox
    url: sandbox/aclaimant-sandbox.yml
- aid: aclaimant:aclaimant-incidents-api
  name: Aclaimant Incidents API
  description: The incidents API from Aclaimant — 1 operation(s) for incidents.
  humanURL: https://api.aclaimant.com/api/index.html
  baseURL: https://api.aclaimant.com/api
  tags:
  - Incidents
  tags_raw:
  - incidents
  properties:
  - type: OpenAPI
    url: openapi/aclaimant-incidents-api-openapi.yml
  - type: APIReference
    url: https://api.aclaimant.com/api/index.html
  - type: Authentication
    url: authentication/aclaimant-authentication.yml
  - type: Conventions
    url: conventions/aclaimant-conventions.yml
  - type: DataModel
    url: data-model/aclaimant-data-model.yml
  - type: ErrorCatalog
    url: errors/aclaimant-problem-types.yml
  - type: Sandbox
    url: sandbox/aclaimant-sandbox.yml
- aid: aclaimant:aclaimant-policies-api
  name: Aclaimant Policies API
  description: The policies API from Aclaimant — 2 operation(s) for policies.
  humanURL: https://api.aclaimant.com/api/index.html
  baseURL: https://api.aclaimant.com/api
  tags:
  - Policies
  tags_raw:
  - policies
  properties:
  - type: OpenAPI
    url: openapi/aclaimant-policies-api-openapi.yml
  - type: APIReference
    url: https://api.aclaimant.com/api/index.html
  - type: Authentication
    url: authentication/aclaimant-authentication.yml
  - type: Conventions
    url: conventions/aclaimant-conventions.yml
  - type: DataModel
    url: data-model/aclaimant-data-model.yml
  - type: ErrorCatalog
    url: errors/aclaimant-problem-types.yml
  - type: Sandbox
    url: sandbox/aclaimant-sandbox.yml
- aid: aclaimant:aclaimant-policy-programs-api
  name: Aclaimant Policy Programs API
  description: The policy-programs API from Aclaimant — 2 operation(s) for policy-programs.
  humanURL: https://api.aclaimant.com/api/index.html
  baseURL: https://api.aclaimant.com/api
  tags:
  - policy-programs
  properties:
  - type: OpenAPI
    url: openapi/aclaimant-policy-programs-api-openapi.yml
  - type: APIReference
    url: https://api.aclaimant.com/api/index.html
  - type: Authentication
    url: authentication/aclaimant-authentication.yml
  - type: Conventions
    url: conventions/aclaimant-conventions.yml
  - type: DataModel
    url: data-model/aclaimant-data-model.yml
  - type: ErrorCatalog
    url: errors/aclaimant-problem-types.yml
  - type: Sandbox
    url: sandbox/aclaimant-sandbox.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/aclaimant-capability-edges.yml
  name: Aclaimant Business Capability Map
- type: TrustCenter
  url: security/aclaimant-trust-center.yml
- type: Website
  url: https://www.aclaimant.com/
- type: DeveloperPortal
  url: https://developer.aclaimant.com/
- type: Documentation
  url: https://developer.aclaimant.com/
- type: APIReference
  url: https://api.aclaimant.com/api/index.html
- type: Support
  url: https://support.aclaimant.com/hc/en-us
- type: Blog
  url: https://www.aclaimant.com/blog
- type: BlogRSS
  url: https://www.aclaimant.com/blog/rss.xml
- type: Pricing
  url: https://www.aclaimant.com/plans-and-pricing
- type: Login
  url: https://dashboard.aclaimant.com/login
- type: TermsOfService
  url: https://www.aclaimant.com/service-agreement
- type: PrivacyPolicy
  url: https://www.aclaimant.com/privacy-policy
- type: GitHubOrganization
  url: https://github.com/aclaimant
- type: StatusPage
  url: https://status.aclaimant.com/
- type: TrustCenter
  url: https://trust.aclaimant.com/
- type: Security
  url: https://www.aclaimant.com/responsible-disclosure
- type: Compliance
  url: conformance/aclaimant-conformance.yml
- type: Authentication
  url: authentication/aclaimant-authentication.yml
- type: Conventions
  url: conventions/aclaimant-conventions.yml
- type: Idempotency
  url: conventions/aclaimant-conventions.yml
- type: Conformance
  url: conformance/aclaimant-conformance.yml
- type: ErrorCatalog
  url: errors/aclaimant-problem-types.yml
- type: Lifecycle
  url: lifecycle/aclaimant-lifecycle.yml
- type: ChangeLog
  url: changelog/aclaimant-changelog.yml
- type: ChangeLog
  url: https://support.aclaimant.com/hc/en-us/sections/4406733144859-Product-Updates-Releases
- type: DataModel
  url: data-model/aclaimant-data-model.yml
- type: Packages
  url: packages/aclaimant-packages.yml
- type: Plans
  url: plans/aclaimant-plans-pricing.yml
- type: RateLimits
  url: rate-limits/aclaimant-rate-limits.yml
- type: Sandbox
  url: sandbox/aclaimant-sandbox.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/aclaimant-llms.txt
- type: Overlay
  url: overlays/aclaimant-platform-api-overlay.yaml
- type: DomainSecurity
  url: security/aclaimant-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/aclaimant-vulnerability-disclosure.yml
x-enrichment:
  date: '2026-09-06'
  status: enriched
  artifacts_added: 24
  pass: local-v3

Aclaimant API — frequently asked questions

Does Aclaimant have an API?

Yes. APIs.io lists 8 APIs from Aclaimant, including Aclaimant Partner / Third-party API, Aclaimant Answers API and Aclaimant Bulk API, and 5 more.

Is there an OpenAPI specification for the Aclaimant API?

Yes. APIs.io indexes 7 OpenAPI specifications for Aclaimant, each linked for download from this page.

How do I authenticate with the Aclaimant API?

Aclaimant uses bearer-token authentication (apiKey/http-bearer · 2 schemes). The details are profiled on APIs.io as Aclaimant Authentication.

How much does the Aclaimant API cost?

Aclaimant publishes its prices; its RMIS Basics plan is See a demo as of 2026-10-28. APIs.io lists 3 pricing plans for Aclaimant, with each plan's price, limits and inclusions under Pricing on this page.

Is the Aclaimant API ready for AI agents?

Aclaimant has a Kin Score of 57.2 out of 100 (strong) and an Agent Readiness score of 27.0 (agent-aware), scored by API Evangelist on 2026-11-06.

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/aclaimant"

All providers

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

Every operation they expose

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

How their score was established

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

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.