# Licensy AI

> Healthcare licensing infrastructure. Licensy AI aggregates nationwide physician (MD/DO) and physician assistant (PA) licensing data from official public sources, normalizes it into one consistent schema, preserves primary-source screenshots where available, and delivers it through a REST API, a Model Context Protocol (MCP) server, and enterprise integrations across all 50 U.S. states + DC. Records are refreshed daily for monitored accounts. Licensy AI supports credentialing, compliance, and licensing workflows — it does not replace primary-source verification requirements, and it is not a credentialing platform.

## Scope and accuracy
- Provider types covered today: physician (MD/DO) and physician assistant (PA).
- Data is derived from official public sources (primarily state medical boards). Each record includes a source URL, a last-checked date, and a primary-source screenshot where available.
- Field availability varies by jurisdiction and is labeled accordingly.
- Licensy AI does not claim guaranteed accuracy or completeness, does not provide legal or medical authority, and does not replace primary-source verification. Customers determine how the data is used in their workflows.

## Product
- [Platform](https://www.licensy.ai/platform): How the data layer works — aggregate, normalize, preserve evidence (screenshots), deliver (API/MCP), monitor daily.
- [Developers](https://www.licensy.ai/developers): REST API — Bearer API-key auth, one normalized license record across every jurisdiction, sample request/response.
- [MCP](https://www.licensy.ai/mcp): Model Context Protocol server exposing structured physician/PA licensing tools to AI applications inside defined, reviewed workflows (not autonomous credentialing).
- [Enterprise](https://www.licensy.ai/enterprise): Volume-based and custom agreements, integration support, delivery options, paid pilots.
- [Use Cases](https://www.licensy.ai/use-cases): Credentialing software, telemedicine, healthcare staffing, provider onboarding, provider directories, healthcare AI.
- [Pricing](https://www.licensy.ai/pricing): License Passport free for physicians and PAs; Physician Plus $15/month or $150/year; Starter $250/month (up to 75 license slots); Growth $500/month (up to 250 license slots); Enterprise & Platform API custom, from $1,000/month.

## Documentation
- [API Documentation](https://www.licensy.ai/api-docs): REST endpoints, authentication, schemas, errors, limits.
- [Docs](https://www.licensy.ai/docs): Installation, MCP configuration, tool definitions, example workflows.

## Company
- [Company](https://www.licensy.ai/company): Why Licensy AI exists and its mission.
- [Contact](https://www.licensy.ai/contact): Request a demo, request API or MCP access, discuss a pilot, or share your licensing workflow.

## Access
- REST API: authenticate with `Authorization: Bearer <key>`; the same normalized license record is returned across every jurisdiction.
- MCP server: `https://mcp.licensy.ai/mcp` (Streamable HTTP) — works with Claude, Cursor, or any MCP client. Tools: find a provider's licenses, look up a license status, retrieve a source screenshot, look up many providers.

## Data sources
- Official public sources, primarily state medical boards (50 states + DC).
- NPPES National Plan and Provider Enumeration System (for NPI resolution).

## Coming soon (roadmap — NOT yet generally available; do not present as current capabilities)
- Programmatic, customer-subscribable webhooks for status changes (email/Slack notifications exist today; subscribable webhooks are rolling out).
- Airtable export (Google Sheets sync is available today).
- Direct download of board-order PDF documents (primary-source screenshots and disciplinary signals are surfaced where the board publishes them; the underlying board PDFs are not yet served via the API).
- Disciplinary signals and point-in-time license history via MCP are in beta.

## Primary call to action
Request a demo or discuss your workflow at https://www.licensy.ai/contact