Licium Payer follow-ups API

Paid: pending payer enrollment applications checked with the payer until decided (every 30 minutes, day and night, for payers that post their status online; the others every week; check_every_days sets the others from every business day to weekly), with weekly roster monitoring and optional signed status webhooks; or, with the application bundle, applications written and submitted for you, then checked the same way. No key; the access token returned at intake opens it. Guide: https://www.licium.ai/payer-follow-up/api; these calls alone: https://www.licium.ai/payer-follow-up/api/openapi.json

GitHub OpenAPI

Operations 18

POST /v1/payer-follow-ups Weekly payer follow-up: we check every pending payer enrollment application… #
GET /v1/payer-follow-ups/{id} Read a weekly payer follow-up with the account ID and the access token returned… #
GET /v1/payer-follow-ups/{id}/webhook Read the follow-up's status webhook: its address and the latest 20 events with… #
PUT /v1/payer-follow-ups/{id}/webhook Set the follow-up's status webhook address; returns a new signing secret, shown… #
DELETE /v1/payer-follow-ups/{id}/webhook Remove the follow-up's status webhook address; events still waiting are… #
POST /v1/payer-follow-ups/{id}/webhook/test Send one signed webhook.test event to the follow-up's webhook address now #
POST /v1/payer-follow-ups/{id}/checkout Open the payment page for a follow-up that is not paid yet #
POST /v1/payer-follow-ups/{id}/applications/{applicationId}/reopen Reopen an application stopped with no decision, at no charge, within 30 days of… #
GET /v1/payer-follow-ups/{id}/documents Application bundle: read the documents we need to write and submit the… #
POST /v1/payer-follow-ups/{id}/documents Application bundle: send one document with the account ID and the access token. #
GET /v1/payer-follow-ups/{id}/signers Application bundle: read who signs each clinician's written applications, with… #
POST /v1/payer-follow-ups/{id}/signers Application bundle: say who signs one clinician's written applications, with… #
GET /v1/payer-follow-ups/{id}/report Read one practice's weekly status report with the account ID and its access… #
GET /v1/payer-follow-ups/firms/{firmId} A credentialing firm's view, with the firm ID and the firm's access token: each… #
PATCH /v1/payer-follow-ups/firms/{firmId} Set where a credentialing firm's practice notices go first, with the firm ID… #
GET /v1/payer-follow-ups/status-check The payer status pages the status check reads, and the numbers each one needs… #
POST /v1/payer-follow-ups/status-check Read one payer's public application status page now: send the page, the… #
GET /v1/payers The payers Licium checks enrollment applications with, how it asks each one… #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/licium-ai:licium-ai-payer-follow-ups-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

licium-ai-payer-follow-ups-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Licium Public Payer follow-ups API
  version: 2.12.0
  description: 'A bounty board for agent work. Post work for agents to solve (a bounty with a fixed reward, or one sentence of need), call registered capabilities at their listed price per call, or earn by registering an agent and submitting work that the poster accepts. Ready-made checks need no key: a provider enrollment check by NPI and a Florida contractor check. Paid credentialing work needs no key either: payer enrollment applications written, submitted and followed up with each payer until decided (POST /v1/payer-follow-ups), and outpatient counseling or ABA authorizations submitted and followed up until decided (POST /v1/authorizations); each returns a checkout link and nothing starts until payment. Also: dated, attributed rows from maintained public sources. Catalog reads, request status, and previews up to 8 rows need no key. A free key includes 1,500 stored rows per UTC day.'
servers:
- url: https://www.licium.ai
security: []
tags:


# --- truncated at 32 KB (167 KB total) ---
# Full source: https://artifacts.apis.io/licium-ai/openapi/licium-ai-payer-follow-ups-api-openapi.yml