Middesk
Middesk is a business identity and verification platform providing a REST API for KYB (Know Your Business) compliance, EIN/TIN validation, business registration verification, UBO research, sanctions screening, and ongoing business monitoring. Used by fintechs, lenders, and banks to automate onboarding and compliance workflows.
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 Middesk the way a machine reads it — 60 machine-readable artifacts across 28 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 — Middesk scores 50.6/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Middesk
Each block below is one kind of artifact we hold for Middesk. 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 28
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.
Middesk subpackage_actions API
The subpackage_actions API from Middesk — 2 operation(s) for subpackage_actions.
Middesk subpackage_agents API
The subpackage_agents API from Middesk — 2 operation(s) for subpackage_agents.
Middesk subpackage_applications API
The subpackage_applications API from Middesk — 1 operation(s) for subpackage_applications.
Middesk subpackage_businessBatches API
The subpackage_businessBatches API from Middesk — 3 operation(s) for subpackage_businessbatches.
Middesk subpackage_businesses API
The subpackage_businesses API from Middesk — 3 operation(s) for subpackage_businesses.
Middesk subpackage_companies API
The subpackage_companies API from Middesk — 1 operation(s) for subpackage_companies.
Middesk subpackage_connections API
The subpackage_connections API from Middesk — 1 operation(s) for subpackage_connections.
Middesk subpackage_documents API
The subpackage_documents API from Middesk — 3 operation(s) for subpackage_documents.
Middesk subpackage_identities API
The subpackage_identities API from Middesk — 1 operation(s) for subpackage_identities.
Middesk subpackage_informationRequests API
The subpackage_informationRequests API from Middesk — 1 operation(s) for subpackage_informationrequests.
Middesk subpackage_jurisdictions API
The subpackage_jurisdictions API from Middesk — 2 operation(s) for subpackage_jurisdictions.
Middesk subpackage_liens API
The subpackage_liens API from Middesk — 2 operation(s) for subpackage_liens.
Middesk subpackage_lienTerminations API
The subpackage_lienTerminations API from Middesk — 1 operation(s) for subpackage_lienterminations.
Middesk subpackage_mail API
The subpackage_mail API from Middesk — 2 operation(s) for subpackage_mail.
Middesk subpackage_monitoring API
The subpackage_monitoring API from Middesk — 2 operation(s) for subpackage_monitoring.
Middesk subpackage_orders API
The subpackage_orders API from Middesk — 3 operation(s) for subpackage_orders.
Middesk subpackage_policyResults API
The subpackage_policyResults API from Middesk — 1 operation(s) for subpackage_policyresults.
Middesk subpackage_prefill API
The subpackage_prefill API from Middesk — 1 operation(s) for subpackage_prefill.
Middesk subpackage_questions API
The subpackage_questions API from Middesk — 1 operation(s) for subpackage_questions.
Middesk subpackage_registrationRequests API
The subpackage_registrationRequests API from Middesk — 3 operation(s) for subpackage_registrationrequests.
Middesk subpackage_reviews API
The subpackage_reviews API from Middesk — 1 operation(s) for subpackage_reviews.
Middesk subpackage_runs API
The subpackage_runs API from Middesk — 4 operation(s) for subpackage_runs.
Middesk subpackage_signals API
The subpackage_signals API from Middesk — 2 operation(s) for subpackage_signals.
Middesk subpackage_threads API
The subpackage_threads API from Middesk — 2 operation(s) for subpackage_threads.
Middesk subpackage_timeline API
The subpackage_timeline API from Middesk — 1 operation(s) for subpackage_timeline.
Middesk subpackage_tinMatch API
The subpackage_tinMatch API from Middesk — 1 operation(s) for subpackage_tinmatch.
Middesk subpackage_webhooks API
The subpackage_webhooks API from Middesk — 3 operation(s) for subpackage_webhooks.
Middesk subpackage_websites API
The subpackage_websites API from Middesk — 1 operation(s) for subpackage_websites.
Scroll within the panel for all 28 ·
Pricing 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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
FinOps 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.
Middesk Finops
FINOPSSemantic Vocabularies 1
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.
Middesk Context
JSON-LDSpectral Rules 1
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.
Middesk API Rules
SPECTRALJSON Schema 18
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.
Action
JSON SCHEMAAddress
JSON SCHEMABankruptcy
JSON SCHEMABusiness
JSON SCHEMABusinessBatch
JSON SCHEMACertification
JSON SCHEMADocument
JSON SCHEMAErrorResponse
JSON SCHEMALien
JSON SCHEMAMonitor
JSON SCHEMAOrder
JSON SCHEMAPerson
JSON SCHEMAPolicyResult
JSON SCHEMARegistration
JSON SCHEMAReview
JSON SCHEMASignal
JSON SCHEMAWatchlist
JSON SCHEMAWebsite
JSON SCHEMAScroll within the panel for all 18 ·
Examples 7
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.
Middesk Create Order Example
EXAMPLEMiddesk File Lien Example
EXAMPLEMiddesk Get Business Example
EXAMPLEScroll within the panel for all 7 ·
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.
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.
Resources
Every other property we hold for Middesk — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
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/middesk · machine-readable index on apis.io