canonical: https://jentic.com/apis/discovery.verifiable.com/verifiable # Discovery Verifiable Verifiable API Documentation Verifiable powers provider data, credentialing, and enrollment workflows for health plans, hospitals, and digital health companies. The Discovery API exposes 167 operations covering provider records, licenses, datasets, payer plans, credentialing requests, provider enrollments, monitoring alerts, audit logs, files, notes, webhooks, and integrations. Healthcare operations and provider-data teams use it to automate primary-source verification, monitor license status, and orchestrate credentialing pipelines. ## For AI agents Manage provider records, licenses, credentialing requests, payer enrollments, and monitoring alerts in Verifiable. Useful for health plan, credentialing, and provider-operations agents. ## Scope Does not handle clinical EHR data, patient scheduling, or medical billing - use for provider credentialing, license tracking, and payer enrollment workflows only. ## Capabilities - Manage provider records and provider profiles via /providers and `/providers/{providerId}` - Track licenses, certifications, and primary-source verification status through /licenses - Orchestrate credentialing requests and provider enrollments across payer plans - Monitor provider status changes via /alerts and configure /webhooks for downstream systems - Run reports and aggregate provider data through `/providers/aggregations` and /reports - Manage users, datasets, files, and notes attached to provider records - Audit data changes through /audit and review integrations via /integrations ## Use cases ### Automated Primary-Source Verification for Provider Credentialing Health plans and CVOs can automate primary-source verification of physician licenses, board certifications, and DEA registrations by submitting credentialing requests to Verifiable and polling for status. The /credentialing-requests, /licenses, and /providers endpoints orchestrate the lifecycle from intake to verified record. This compresses credentialing cycles from weeks to days and removes manual follow-up with state boards. Example prompt: Submit a new credentialing request via POST /credentialing-requests for provider ID 9876 and poll GET `/credentialing-requests/{id}` until status is 'completed'. ### Continuous License and Sanction Monitoring Provider operations teams need to know within hours when a clinician's license is suspended, sanctioned, or about to expire. Verifiable's monitoring system surfaces these events via /alerts; configuring /webhooks streams them into compliance ticketing or PagerDuty. This avoids the spreadsheet-based monthly check that misses mid-cycle changes. Example prompt: Configure POST /webhooks to deliver new alerts to the compliance ticketing system, and pull GET /alerts daily for any backlog. ### Payer Enrollment Tracking Health plan operations and physician practices can track payer enrollment status across Medicare, Medicaid, and commercial plans via /provider-enrollments and /payer-plans. Querying enrollments by status (submitted, approved, denied) drives revenue-cycle dashboards and prevents claim denials caused by lapsed enrollments. Joined with /providers, it gives a single view per clinician. Example prompt: GET /provider-enrollments filtered by status='submitted' for the past 90 days and aggregate counts by payer plan for the operations dashboard. ### Provider Data Reporting and Aggregations Network-management teams can pull aggregations and reports from Verifiable to power network-adequacy analyses, leadership dashboards, and regulatory submissions. `/providers/aggregations` groups providers by attribute, and /reports endpoints generate scoped exports. This is faster than rebuilding the same logic against a raw database extract. Example prompt: Call GET `/providers/aggregations` grouped by license type and state, and persist the result for the network-adequacy dashboard. ### AI Agent for Credentialing Operations AI agents can act as credentialing operations copilots - drafting status updates, checking outstanding requirements, and triggering renewal credentialing 90 days before license expiry. Through Jentic, the 167 Verifiable operations are searchable as tools, and the bearer token sits in your Jentic One instance so the agent never holds the credential. Example prompt: Search Jentic for 'list providers with expiring licenses', load the relevant /providers and /licenses operations, and execute them to generate a 30-day renewal worklist. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/auth/token/password` | Obtain a bearer token via username/password | | GET | `/providers` | List providers | | GET | `/providers/{providerId}` | Retrieve a single provider record | | POST | `/providers` | Create a new provider record | | GET | `/providers/aggregations` | Group providers by attributes for reporting | | POST | `/providers/{providerId}/report` | Generate a report scoped to a provider | | GET | `/providertypes` | List supported provider types | ## Key resources - **Providers** — Provider records, profiles, types, and aggregations - **Licenses** — License records and primary-source verification status - **Credentialing Requests** — Lifecycle of credentialing requests from intake to completion - **Provider Enrollments** — Payer enrollment records linking providers and payer plans - **Payers & Payer Plans** — Payer organisations and the plans that providers enroll with - **Alerts & Monitoring** — Continuous monitoring and alert delivery for license and sanction changes - **Webhooks** — Outbound event delivery to subscribed systems - **Reports & Audit** — Reporting endpoints and audit log access ## Why Jentic - **Setup:** Wiring Verifiable by hand means minting a bearer token from a password grant, refreshing it, and navigating a large credentialing surface yourself. Through Jentic you install once, import the Verifiable API from the API Directory, store the credentials once, and your agent calls it. - **Permission scoping:** Verifiable puts the provider id in the URL path (`/providers/{providerId}`), so a rule can pin your agent to one provider: it can read that provider's record and reports and nothing else. You choose the operations it may call, so creating new providers is not included unless you add it. - **Credential handling:** Your Verifiable bearer token and the username and password used to mint it are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'list providers with expiring licenses' or 'pull a provider report', and Jentic returns the matching Verifiable operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **DrChrono** — EHR and practice-management platform - **Epic FHIR** — Epic's FHIR API for clinical and patient data - **Onfido** — Identity verification with document and biometric checks ## FAQ ### What authentication does the Verifiable Discovery API use? Verifiable uses bearer tokens, obtained via POST `/auth/token/password` with username and password (or POST `/auth/token/google` for Google identities). Tokens can be invalidated through `/auth/token/invalidate.` Through Jentic, the bearer token is held in your Jentic One instance and refreshed at execution; agents never see the raw token. ### Can I run primary-source verification with the Verifiable API? Yes, submit a credentialing request via the /credentialing-requests endpoints with the provider ID and the items to verify. Verifiable performs primary-source verification against state boards and other authoritative sources, then updates the linked /licenses records with verification status. ### What are the rate limits for the Verifiable API? Verifiable does not publish a single rate limit in this OpenAPI spec; limits are tier-dependent and set per customer contract. Production tenants typically receive higher quotas than sandbox accounts. Contact your Verifiable account team to confirm the limits applied to your bearer token. ### How do I monitor provider license expiry through Jentic? Search Jentic for 'list licenses expiring soon' or 'get provider monitoring alerts', load the /licenses or /alerts operations, and execute them with a date-range filter. Combine with POST /webhooks to forward future expiry alerts directly into your compliance system. ### Can I configure webhooks for credentialing events? Yes, POST /webhooks creates a subscription to events such as credentialing-request.completed, license.updated, or alert.created. Verifiable signs payloads so subscribers can verify origin. Use this instead of polling /alerts to reduce request volume. ### Is the Verifiable API free? No. Verifiable is a paid B2B service for health plans, hospitals, and digital health companies. API access is provisioned as part of a Verifiable contract; pricing is contract-based and not published. Contact Verifiable sales for plan details. ### Can I limit what my agent is allowed to do with the Verifiable API? Yes. Jentic One is self-hosted by you, so your own rules decide which Verifiable operations and credentials the agent may use. Because Verifiable puts the provider id in the URL path, such as `/providers/{providerId}`, a rule can pin the agent to a single provider so it only reads that provider's record and reports. You also choose the operations it may call, so write actions like POST /providers to create new provider records are excluded unless you explicitly add them.