Developers
Built to integrate.
Add provider licensing data to onboarding, monitoring, credentialing, staffing, and healthcare software workflows — through one API instead of dozens of board-specific integrations.
Authentication
Bearer API key. Send Authorization: Bearer <key> with each request.
Consistent schema
The same normalized license record across every jurisdiction, so you parse one shape.
Access paths
REST API and the MCP server — the same data, two delivery methods.
Sample request
POST /api/v2/licenses/lookup
Authorization: Bearer <key>
Content-Type: application/json
{ "npi": "1234567890", "state": "CA" }Sample response
{
"full_name": "Jane A. Smith",
"license_number": "A1234567",
"state": "California",
"profession": "Physician (MD)",
"status": "active",
"expired": "2028-05-31",
"last_checked": "2026-07-20",
"screenshot_url": "… (where available)"
}Integration patterns
Fit licensing data into the flows you already run.
Verify a provider during onboarding
Refresh monitored providers on a schedule
Call the same data from AI workflows via MCP
Request access to the API.
Licensy AI provides licensing information derived from official public sources. Customers remain responsible for determining how the information is used within their credentialing, compliance, legal, or operational workflows.