TrustLayer
TrustLayer is a vendor risk management and certificate of insurance (COI) tracking platform that automates the collection, verification, and ongoing monitoring of compliance documents. It uses AI-powered OCR field extraction, real-time carrier connections, and NIPR license verification to process COIs, W9s, and business licenses across a network of 500,000+ companies. The TrustLayer Platform API lets teams programmatically manage parties (vendors), contacts, projects, documents, and compliance profiles, request documents, and receive real-time webhook notifications as compliance status changes. Backed by Craft Ventures. Sector: insurtech / fintech.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles TrustLayer the way a machine reads it — 26 machine-readable artifacts across 21 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 — TrustLayer scores 51.2/100 (developing), with a separate agent-readiness read of 61/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
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.
How we profile TrustLayer
Each block below is one kind of artifact we hold for TrustLayer. 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 21
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.
TrustLayer Auth API
The Auth API from TrustLayer — 1 operation(s) for auth.
TrustLayer branding API
The branding API from TrustLayer — 2 operation(s) for branding.
TrustLayer compliance-profiles API
The compliance-profiles API from TrustLayer — 8 operation(s) for compliance-profiles.
TrustLayer contacts API
The contacts API from TrustLayer — 4 operation(s) for contacts.
TrustLayer Context Objects API
The Context Objects API from TrustLayer — 2 operation(s) for context objects.
TrustLayer Context Records API
The Context Records API from TrustLayer — 7 operation(s) for context records.
TrustLayer custom-fields API
The custom-fields API from TrustLayer — 4 operation(s) for custom-fields.
TrustLayer Document Types API
The Document Types API from TrustLayer — 2 operation(s) for document types.
TrustLayer documents API
The documents API from TrustLayer — 15 operation(s) for documents.
TrustLayer Parties API
The Parties API from TrustLayer — 20 operation(s) for parties.
TrustLayer party-types API
The party-types API from TrustLayer — 1 operation(s) for party-types.
TrustLayer Policies API
The Policies API from TrustLayer — 11 operation(s) for policies.
TrustLayer Primary Objects API
The Primary Objects API from TrustLayer — 2 operation(s) for primary objects.
TrustLayer Primary Records API
The Primary Records API from TrustLayer — 12 operation(s) for primary records.
TrustLayer Projects API
The Projects API from TrustLayer — 9 operation(s) for projects.
TrustLayer reports API
The reports API from TrustLayer — 2 operation(s) for reports.
TrustLayer Request Records API
The Request Records API from TrustLayer — 7 operation(s) for request records.
TrustLayer Requirements API
The Requirements API from TrustLayer — 2 operation(s) for requirements.
TrustLayer tags API
The tags API from TrustLayer — 4 operation(s) for tags.
TrustLayer Views API
The Views API from TrustLayer — 2 operation(s) for views.
TrustLayer Workspaces API
The Workspaces API from TrustLayer — 1 operation(s) for workspaces.
Scroll within the panel for all 21 ·
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.
trustlayer-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Trustlayer Webhooks
ASYNCAPISecurity 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.
Resources
Every other property we hold for TrustLayer — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/trustlayer · machine-readable index on apis.io