Acrisure
Acrisure is a global fintech and insurance brokerage headquartered in Grand Rapids, Michigan, founded in 2005 and grown from $38M to roughly $5B in revenue with more than 19,000 colleagues across 500+ offices in over 20 countries. It sells commercial and personal insurance, employee benefits, payroll and HR, reinsurance, surety bonds, trade credit, mortgages, managed IT and cybersecurity through a partner-agency model rather than a developer platform. Acrisure publishes no developer portal, no API reference and no machine-readable specification of any kind, but it does operate an undocumented, OAuth-protected Model Context Protocol server at api.acrisure.com/v1/mcp behind Microsoft Entra ID — discoverable only from the `mcp_user` scope in its RFC 8414 authorization-server metadata.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Acrisure the way a machine reads it — 6 machine-readable artifacts across 1 API, 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 — Acrisure scores 31.0/100 (thin), with a separate agent-readiness read of 23/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
Acrisure runs a live OAuth-protected MCP server at api.acrisure.com/v1/mcp — proven by an application-level 403 on tools/list against a control sibling path that 404s — but publishes no OpenAPI, no tool list and no documentation for it anywhere, and its llms.txt and /ai/*.json endpoints still serve the unshipped Sitecore XM Cloud demo fixture for a fictional "Skate Park" skate-brand wholesaler instead of anything about Acrisure.
The documentation is public — a person can read it, but a machine cannot. This one is Acrisure's to change: publishing an OpenAPI (or AsyncAPI for events) at a stable URL would make the same surface consumable by a crawler, a linter, and an AI agent.
What we probed
https://api.acrisure.com/v1/mcp→ HTTP 403https://api.acrisure.com/v1/mcpZZZ→ HTTP 404https://api.acrisure.com/.well-known/oauth-authorization-server→ HTTP 200https://api.acrisure.com/.well-known/oauth-protected-resource→ HTTP 404https://www.acrisure.com/llms.txt→ HTTP 200https://www.acrisure.com/ai/summary.json→ HTTP 200https://api.acrisure.com/v1/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.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Acrisure'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/acrisure/"
title="Acrisure on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/acrisure.svg"
alt="Acrisure Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/acrisure/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/acrisure/"
title="Acrisure on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/acrisure/card.svg"
alt="Acrisure 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 Acrisure
Each block below is one kind of artifact we hold for Acrisure. 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 1
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.
Acrisure MCP Server
Hosted Model Context Protocol server operated by Acrisure at https://api.acrisure.com/v1/mcp. Production and live, protected by Microsoft Entra ID via an authorization-code + PK...
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
acrisure-mcp.yml
MCP SERVERSecurity 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.
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.
Resources
Every other property we hold for Acrisure — 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 1
Portal, sign-up, and the first successful call
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 6
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 5
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/acrisure · machine-readable index on apis.io
This is an independent, third-party profile of Acrisure, 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.