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.
Aclaimant’s developer surface includes documentation, API reference, support, engineering blog, pricing, authentication, changelog, and 29 more developer resources.
What this lets a business do 1
Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →
Kin Score
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.
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
Pricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Aclaimant Rate Limits
RATE LIMITSOpenAPI 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
GENERATEDSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll for all 7
Operate 5
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.