ACORD
ACORD is the global standards-setting body for the insurance industry, publishing the data standards that insurers, reinsurers, brokers, MGAs and software vendors use to exchange policy, claims, party, underwriting, accounting and settlement data: ACORD XML and AL3 for property & casualty, Life & Annuity XML and DTCC EDI, the Global Reinsurance & Large Commercial (GRLC) standards behind EBOT, ECOT, GPM and CRP, and the JSON/YAML Next-Generation Digital Standards (NGDS) aimed at REST APIs and microservices. ACORD operates no public API of its own; standards and schemas are delivered to members under licence, and its commercial subsidiary ACORD Solutions Group runs the ADEPT data exchange platform under separate agreement.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles ACORD the way a machine reads it — 85 machine-readable artifacts across 6 APIs, 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 — ACORD scores 55.3/100 (strong), with a separate agent-readiness read of 28/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
Every ACORD standards artifact — the NGDS schemas, Master Object List, Master Resource Definitions and Master Deprecation List — is published only as a /file-download/
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is ACORD's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://www.acord.org/file-download/04dcef0d-6222-46a2-911f-5c905db8e086→ HTTP 302https://www.acord.org/standards-architecture/acord-data-standards/standards-downloads→ HTTP 200https://www.acord.org/openapi.json→ HTTP 404https://standards.acord.org/openapi.json→ HTTP 403https://www.acordsolutions.com/openapi.json→ HTTP 404
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
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from ACORD'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/acord/"
title="ACORD on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/acord.svg"
alt="ACORD Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/acord/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/acord/"
title="ACORD on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/acord/card.svg"
alt="ACORD Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile ACORD
Each block below is one kind of artifact we hold for ACORD. 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.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
ACORD XML Standards API
ACORD XML Standards define data exchange formats for property & casualty, life, annuity, and reinsurance using SOAP/XML protocols. APIs enable claims inquiry, policy administrat...
ACORD Reinsurance & Large Commercial Data Standards API
ACORD Global Reinsurance & Large Commercial Data Standards define XML data exchange formats for reinsurance and large commercial lines. APIs support facultative and treaty reins...
ACORD Claims API
Claims inquiry, submission, and management
ACORD Party API
Insured party and contact management
ACORD Policy API
Policy administration and management
ACORD Underwriting API
Underwriting and risk assessment
Open Collections 6
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONACORD Next-Generation Digital Standards (NGDS) Claims API
OPEN COLLECTIONACORD Next-Generation Digital Standards (NGDS) API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Acord Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Acord Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Acord Finops
FINOPSFeatures 5
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
XML Data Standards
ACORD XML standards for property & casualty, life, annuity, and reinsurance SOAP/XML data exchange.
Next-Generation Digital Standards
JSON/YAML-based NGDS for RESTful APIs, microservices, and IoT insurance data exchange.
Reinsurance Standards
Global reinsurance and large commercial data standards for facultative and treaty transactions.
Life and Annuity Standards
Electronic data standards for life insurance and annuity products covering underwriting and policy management.
Reference Architecture
ACORD reference architecture providing structural frameworks for insurance technology implementations.
Semantic Vocabularies 2
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Acord Context
JSON-LDAcord Ngds Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
ACORD API Rules
SPECTRALACORD API Rules
SPECTRALJSON Schema 16
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ACORD Claim
JSON SCHEMAACORD Policy
JSON SCHEMAAddress
JSON SCHEMAClaimList
JSON SCHEMAClaimRequest
JSON SCHEMAContact
JSON SCHEMACoverageRequest
JSON SCHEMACoverage
JSON SCHEMAPartyList
JSON SCHEMAPartyRequest
JSON SCHEMAParty
JSON SCHEMAPolicyList
JSON SCHEMAPolicyRequest
JSON SCHEMAPolicyUpdate
JSON SCHEMAUnderwritingSubmissionResponse
JSON SCHEMAUnderwritingSubmission
JSON SCHEMAScroll within the panel for all 16 ·
JSON Structure 16
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Acord Claim Structure
JSON STRUCTUREAcord Policy Structure
JSON STRUCTURENgds Address Structure
JSON STRUCTURENgds Claim List Structure
JSON STRUCTURENgds Claim Request Structure
JSON STRUCTURENgds Contact Structure
JSON STRUCTURENgds Coverage Request Structure
JSON STRUCTURENgds Coverage Structure
JSON STRUCTURENgds Party List Structure
JSON STRUCTURENgds Party Request Structure
JSON STRUCTURENgds Party Structure
JSON STRUCTURENgds Policy List Structure
JSON STRUCTURENgds Policy Request Structure
JSON STRUCTURENgds Policy Update Structure
JSON STRUCTURENgds Underwriting Submission Response Structure
JSON STRUCTURENgds Underwriting Submission Structure
JSON STRUCTUREScroll within the panel for all 16 ·
Examples 16
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Acord Claim Example
EXAMPLEAcord Policy Example
EXAMPLENgds Address Example
EXAMPLENgds Claim List Example
EXAMPLENgds Claim Request Example
EXAMPLENgds Contact Example
EXAMPLENgds Coverage Example
EXAMPLENgds Party Example
EXAMPLENgds Party List Example
EXAMPLENgds Party Request Example
EXAMPLENgds Policy List Example
EXAMPLENgds Policy Request Example
EXAMPLENgds Policy Update Example
EXAMPLEScroll within the panel for all 16 ·
Security Posture 2
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Claims Data Exchange
Standardized ACORD XML or NGDS JSON claims transaction exchange between carriers, adjusters, and reinsurers.
Policy Administration
Automated policy issuance, endorsement, and renewal using ACORD NGDS microservices architecture.
Underwriting Automation
Straight-through processing of insurance applications using ACORD standardized data elements.
Reinsurance Settlement
Facultative and treaty reinsurance data exchange using ACORD Global Reinsurance Data Standards.
Regulatory Reporting
Compliance reporting using ACORD-standardized data formats for regulatory submissions.
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Insurance Core Systems
Integration with policy administration systems (PAS) and claims management systems (CMS).
Reinsurance Platforms
Integration with reinsurance management platforms supporting ACORD AL3 and RIBO formats.
Insurtech Solutions
Modern insurtech API platforms consuming ACORD NGDS JSON standards.
Regulatory Systems
Integration with state and national insurance regulatory reporting systems.
Resources
Every other property we hold for ACORD — 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.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 4
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 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 6
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 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/acord · machine-readable index on apis.io
This is an independent, third-party profile of ACORD, 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.