Verifiable API Documentation

Name: Verifiable API Documentation API
Brand: Verifiable API Documentation
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHealthcareClinical Databearer167 EndpointsREST

For Agents

Manage provider records, licenses, credentialing requests, payer enrollments, and monitoring alerts in Verifiable. Useful for health plan, credentialing, and provider-operations agents.

Connect the Verifiable API Documentation to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Verifiable API Documentation, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Verifiable API Documentation API.

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

GET STARTED

Start building with Verifiable API Documentation API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Verifiable API Documentation, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Verifiable API Documentation API for, with concrete tasks.

★ 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.

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.

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.

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.

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 MAXsystem so the agent never holds the credential.

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

167 endpoints — verifiable powers provider data, credentialing, and enrollment workflows for health plans, hospitals, and digital health companies.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Verifiable bearer tokens (and the underlying username/password used to mint them) are stored encrypted in Jentic's MAXsystem vault. Agents call the 167 Verifiable operations through scoped Jentic sessions; the raw bearer token and credentials never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'list providers with expiring licenses' or 'submit a credentialing request') and Jentic returns the matching Verifiable operation from the 167 available, so the agent acts without browsing the Discovery reference.

Time to first call

Direct Verifiable integration: 1-3 weeks for auth, schema mapping across providers/licenses/credentialing, webhook signature handling, and pagination. Through Jentic: under 1 hour to call individual operations once credentials are in the vault.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

DrChrono

EHR and practice-management platform

Pair DrChrono for clinical EHR data with Verifiable for credentialing and provider enrollment workflows.

Complementary

Epic FHIR

Epic's FHIR API for clinical and patient data

Use Epic FHIR for patient/clinical data and Verifiable for the credentialing layer that determines which providers can deliver that care.

Alternative

Onfido

Identity verification with document and biometric checks

Choose Onfido when verifying patient or general consumer identity; choose Verifiable when verifying clinician credentials and payer enrollments.

FAQs

Specific to using Verifiable API Documentation API through Jentic.

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 the MAXsystem vault 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.