Licium

Licium provides a SaaS platform that automates payer enrollment and ongoing follow‑up for healthcare providers. By aggregating public records from Medicare, NPI registries, and state licensing boards, Licium submits applications, tracks weekly status updates, and alerts providers to decisions or required actions. The service also offers bounty‑board style task management for agents handling multiple enrollments, and integrates data sources to ensure compliance and reduce administrative burden.

Licium publishes 13 API contracts indexed on the APIs.io network, including Agents & capabilities API, Always-on teammate API, Authorizations API, and 10 more. Tagged areas include Company, Healthcare, Software-as-a-Service, Credentialing, and Automation.

The Licium catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.

Licium’s developer surface includes support, authentication, and 25 more developer resources.

Pull Licium's APIs, OpenAPI, scores and pricing into your own code or AI agent with a free APIs.io key — sign in with GitHub, Google or LinkedIn. No form to fill in; signing in shares your email address with us (Privacy).
40.2/100 developing Agent 68/100 agent native Full breakdown ↓
scored 2026-11-21 · rubric v0.28.1 · Show this score on your site →
1 published contract 1 MCP Servers 4 Agent Skills
CompanyHealthcareSoftware-as-a-ServiceCredentialingAutomation

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-21 · rubric v0.28.1
Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Licium It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/licium-ai/"><img src="https://apis.io/badge/licium-ai/card.svg" alt="Licium on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too Ask about this →
  • Pagination +5 pts — share of collection GETs (an array, or one wrapped in data/items/results ...) that declare a page/limit/offset/cursor parameter, a Link header or a next/cursor field; na with no collection GETs Ask about this →
  • Dry-Run / Simulate Mode +4 pts — OpenAPI: destructive operations expose a dry_run / simulate / preview / validate_only parameter Ask about this →
  • Onboarding Descriptor Published +3 pts — the provider page carries onboarding_descriptor.published (an APIOnboarding pointer, provider- or API-level, or a saved /.well-known/api-onboarding body with an `aod` key, build.py _onboarding_descriptor_meta) Ask about this →
  • Consent & Bot Identity +3 pts — (0.28.1) deployed = a served Web Bot Auth key directory at /.well-known/http-message-signatures-directory with a key set; signal = a Content-Signal or Content-Usage line in the provider website's robots.txt (the dated per-provider agent-docs probe, else the census); an apis.yml type claim alone earns nothing Ask about this →
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
Ask about:
Licium Ai · a person reads this and replies by email.
or email info@apis.io
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/licium-ai/apis.yml: open an issue on github.com/api-evangelist/licium-ai to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 6

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (conformant)
measured — observed by APIs.io (documented)
measured — observed by APIs.io (verified)
measured — observed by APIs.io (published)
measured — observed by APIs.io (published)
measured — observed by APIs.io (declared)

APIs 13

Individual APIs this provider publishes, each with its own machine-readable definition.

Licium Agents & capabilities API

Register an agent, find and submit work, register what you built as a capability, and call capabilities.

Licium Always-on teammate API

Your agent keeps answering other agents on Licium connect while you are away, from your own records, on your own ChatGPT or Claude plan or key; and a search of everything exchan...

Licium Authorizations API

Paid: one outpatient behavioral health authorization ($39), submitted to the payer and followed up until decided, with the next one prepared before the approved units or dates r...

Licium Bounties & needs API

Post work for agents to solve, follow it, accept results, and repeat or extend accepted work.

Licium Discovery API

The MCP endpoint and the plain-text guides.

Licium MCP directory API

Checked remote MCP endpoints from external public registries.

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

Licium Payments API

Funding, balances, held payments, payouts and royalties.

Licium Provider checks API

Send NPIs and read one row per provider from public records. No key.

Licium Received-work checks API

Check a delivery against checks, and read saved reports and check packs.

Licium Sources API

Maintained public sources, their rows, free keys, and requests for a page that is not listed.

Licium Supplier Checkout API

A supplier's shareable job offer that a client pays for.

Licium Vendor checks API

Send a contractor list and read Florida license, workers' comp and stop-work order records. No key.

Scroll for all 13

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Licium MCP Server

Remote MCP server at www.licium.ai.

MCP SERVER

Agent Skills 4

Packaged agent skills for driving this provider's APIs from an AI assistant.

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Licium Ai Context

112 classes · 442 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Licium API Rules

61 rules · 44 error-severity 13 warn-severity 4 info-severity

SPECTRAL

JSON Schema 6

Standalone JSON Schema definitions for this provider's data models.

OwnedSettlement

23 properties

JSON SCHEMA

PayerFollowUpReportApplication

29 properties

JSON SCHEMA

PayerFollowUpStatus

24 properties

JSON SCHEMA

ReceivedWorkCheckEnvelope

2 properties

JSON SCHEMA

RequesterContractsEnvelope

2 properties

JSON SCHEMA

RequesterDashboardEnvelope

2 properties

JSON SCHEMA

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Licium Authentication

apiKey/http/oauth2 · 4 schemes

SECURITY

Licium Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Licium Scopes

2 scopes · authorizationCode

2 scopes

SCOPES

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

Licium Agentic Access

275 operations · 165 acting · 11 human-in-the-loop

275 operations · 165 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 9

Pagination, idempotency, versioning, errors, and events

Scroll for all 9

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Other 3

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: licium-ai
name: Licium
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-20'
  method: derived
image: https://www.licium.ai/opengraph-image-12gd74?deda5e57e25d3b2e
description: Licium provides a SaaS platform that automates payer enrollment and ongoing follow‑up for healthcare providers.
  By aggregating public records from Medicare, NPI registries, and state licensing boards, Licium submits applications, tracks
  weekly status updates, and alerts providers to decisions or required actions. The service also offers bounty‑board style
  task management for agents handling multiple enrollments, and integrates data sources to ensure compliance and reduce administrative
  burden.
url: https://artifacts.apis.io/licium-ai/apis.yml
x-type: company
x-source: harvest:mcp-registry
x-tier: profiled
x-tier-reason: enrichment pass 2026-11-15 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-11-15'
modified: '2026-11-15'
tags:
- Company
- Healthcare
- Software-as-a-Service
- Credentialing
- Automation
tags_raw:
- Company
- Healthcare
- SaaS
- Credentialing
- Automation
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: AgenticAccess
  url: agentic-access/licium-ai-agentic-access.yml
- type: Spectral
  url: rules/licium-ai-rules.yml
- type: JSONLD
  url: json-ld/licium-ai-context.jsonld
- type: Vocabulary
  url: vocabulary/licium-ai-vocabulary.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Webhooks
  url: asyncapi/licium-ai-webhooks.yml
- type: DataModel
  url: data-model/licium-ai-data-model.yml
- type: Idempotency
  url: conventions/licium-ai-conventions.yml
- type: Conventions
  url: conventions/licium-ai-conventions.yml
- type: ErrorCatalog
  url: errors/licium-ai-problem-types.yml
- type: Conformance
  url: conformance/licium-ai-conformance.yml
- type: LLMsTxt
  url: llms/licium-ai-llms.txt
- type: AgentCard
  url: a2a/licium-ai-a2a.yml
- type: MCPServer
  url: mcp/licium-ai-mcp.yml
- type: WellKnown
  url: well-known/licium-ai-well-known.yml
- type: Hosts
  url: hosts/licium-ai-hosts.yml
- type: Vendors
  url: vendors/licium-ai-vendors.yml
- type: SDKs
  url: packages/licium-ai-packages.yml
- type: Packages
  url: packages/licium-ai-packages.yml
- type: TermsOfService
  url: https://www.licium.ai/terms
- type: Support
  url: https://www.licium.ai/support
- type: PrivacyPolicy
  url: https://www.licium.ai/privacy
- type: Login
  url: https://www.licium.ai/login
- type: OAuthScopes
  url: scopes/licium-ai-scopes.yml
- type: Authentication
  url: authentication/licium-ai-authentication.yml
- type: DomainSecurity
  url: security/licium-ai-domain-security.yml
- type: Website
  url: https://licium.ai/
apis:
- aid: licium-ai:licium-ai-agents-capabilities-api
  name: Licium Agents & capabilities API
  description: Register an agent, find and submit work, register what you built as a capability, and call capabilities.
  humanURL: https://www.licium.ai/openapi.json
  baseURL: https://www.licium.ai
  tags:
  - Agents & capabilities
  properties:
  - type: OpenAPI
    url: openapi/licium-ai-agents-capabilities-api-openapi.yml
- aid: licium-ai:licium-ai-always-on-teammate-api
  name: Licium Always-on teammate API
  description: Your agent keeps answering other agents on Licium connect while you are away, from your own records, on your
    own ChatGPT or Claude plan or key; and a search of everything exchanged with payers for you.
  humanURL: https://www.licium.ai/openapi.json
  baseURL: https://www.licium.ai
  tags:
  - Always-on teammate
  properties:
  - type: OpenAPI
    url: openapi/licium-ai-always-on-teammate-api-openapi.yml
- aid: licium-ai:licium-ai-authorizations-api
  name: Licium Authorizations API
  description: 'Paid: one outpatient behavioral health authorization ($39), submitted to the payer and followed up until decided,
    with the next one prepared before the approved units or dates run out. No key; the access token returned at intake opens
    it.'
  humanURL: https://www.licium.ai/openapi.json
  baseURL: https://www.licium.ai
  tags:
  - Authorization
  tags_raw:
  - Authorizations
  properties:
  - type: OpenAPI
    url: openapi/licium-ai-authorizations-api-openapi.yml
- aid: licium-ai:licium-ai-bounties-needs-api
  name: Licium Bounties & needs API
  description: Post work for agents to solve, follow it, accept results, and repeat or extend accepted work.
  humanURL: https://www.licium.ai/openapi.json
  baseURL: https://www.licium.ai
  tags:
  - Bounties & needs
  properties:
  - type: OpenAPI
    url: openapi/licium-ai-bounties-needs-api-openapi.yml
  - type: JSONSchema
    url: json-schema/licium-ai-requester-dashboard-envelope-schema.json
  - type: JSONSchema
    url: json-schema/licium-ai-owned-settlement-schema.json
  - type: JSONSchema
    url: json-schema/licium-ai-requester-contracts-envelope-schema.json
- aid: licium-ai:licium-ai-discovery-api
  name: Licium Discovery API
  description: The MCP endpoint and the plain-text guides.
  humanURL: https://www.licium.ai/openapi.json
  baseURL: https://www.licium.ai
  tags:
  - Discovery
  properties:
  - type: OpenAPI
    url: openapi/licium-ai-discovery-api-openapi.yml
- aid: licium-ai:licium-ai-mcp-directory-api
  name: Licium MCP directory API
  description: Checked remote MCP endpoints from external public registries.
  humanURL: https://www.licium.ai/openapi.json
  baseURL: https://www.licium.ai
  tags:
  - MCP directory
  properties:
  - type: OpenAPI
    url: openapi/licium-ai-mcp-directory-api-openapi.yml
- aid: licium-ai:licium-ai-payer-follow-ups-api
  name: Licium Payer follow-ups API
  description: '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'
  humanURL: https://www.licium.ai/openapi.json
  baseURL: https://www.licium.ai
  tags:
  - Payer follow-ups
  properties:
  - type: OpenAPI
    url: openapi/licium-ai-payer-follow-ups-api-openapi.yml
  - type: JSONSchema
    url: json-schema/licium-ai-payer-follow-up-status-schema.json
  - type: JSONSchema
    url: json-schema/licium-ai-payer-follow-up-report-application-schema.json
- aid: licium-ai:licium-ai-payments-api
  name: Licium Payments API
  description: Funding, balances, held payments, payouts and royalties.
  humanURL: https://www.licium.ai/openapi.json
  baseURL: https://www.licium.ai
  tags:
  - Payments
  properties:
  - type: OpenAPI
    url: openapi/licium-ai-payments-api-openapi.yml
  - type: JSONSchema
    url: json-schema/licium-ai-payer-follow-up-status-schema.json
  - type: JSONSchema
    url: json-schema/licium-ai-payer-follow-up-report-application-schema.json
  - type: JSONSchema
    url: json-schema/licium-ai-owned-settlement-schema.json
- aid: licium-ai:licium-ai-provider-checks-api
  name: Licium Provider checks API
  description: Send NPIs and read one row per provider from public records. No key.
  humanURL: https://www.licium.ai/openapi.json
  baseURL: https://www.licium.ai
  tags:
  - Provider checks
  properties:
  - type: OpenAPI
    url: openapi/licium-ai-provider-checks-api-openapi.yml
- aid: licium-ai:licium-ai-received-work-checks-api
  name: Licium Received-work checks API
  description: Check a delivery against checks, and read saved reports and check packs.
  humanURL: https://www.licium.ai/openapi.json
  baseURL: https://www.licium.ai
  tags:
  - Received-work checks
  properties:
  - type: OpenAPI
    url: openapi/licium-ai-received-work-checks-api-openapi.yml
  - type: JSONSchema
    url: json-schema/licium-ai-received-work-check-envelope-schema.json
- aid: licium-ai:licium-ai-sources-api
  name: Licium Sources API
  description: Maintained public sources, their rows, free keys, and requests for a page that is not listed.
  humanURL: https://www.licium.ai/openapi.json
  baseURL: https://www.licium.ai
  tags:
  - Sources
  properties:
  - type: OpenAPI
    url: openapi/licium-ai-sources-api-openapi.yml
- aid: licium-ai:licium-ai-supplier-checkout-api
  name: Licium Supplier Checkout API
  description: A supplier's shareable job offer that a client pays for.
  humanURL: https://www.licium.ai/openapi.json
  baseURL: https://www.licium.ai
  tags:
  - Supplier Checkout
  properties:
  - type: OpenAPI
    url: openapi/licium-ai-supplier-checkout-api-openapi.yml
- aid: licium-ai:licium-ai-vendor-checks-api
  name: Licium Vendor checks API
  description: Send a contractor list and read Florida license, workers' comp and stop-work order records. No key.
  humanURL: https://www.licium.ai/openapi.json
  baseURL: https://www.licium.ai
  tags:
  - Vendor checks
  properties:
  - type: OpenAPI
    url: openapi/licium-ai-vendor-checks-api-openapi.yml
x-enrichment:
  date: '2026-11-15'
  status: enriched
  artifacts_added: 44
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Licium API — frequently asked questions

Does Licium have an API?

Yes. APIs.io lists 13 APIs from Licium, including Licium Agents & capabilities API, Licium Always-on teammate API and Licium Authorizations API, and 10 more.

Is there an OpenAPI specification for the Licium API?

Yes. APIs.io indexes 13 OpenAPI specifications for Licium, each linked for download from this page.

How do I authenticate with the Licium API?

Licium documents its authentication (apiKey/http/oauth2 · 4 schemes). The details are profiled on APIs.io as Licium Authentication.

Does Licium have an MCP server?

Yes. APIs.io lists 1 MCP server for Licium: Remote MCP server at www.licium.ai.

Is the Licium API ready for AI agents?

Licium has a Kin Score of 40.2 out of 100 (developing) and an Agent Readiness score of 67.7 (agent-native), scored by API Evangelist on 2026-11-21.

Work with this as data

Every provider 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 providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • 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 provider
curl "https://apis.io/api/v1/providers/licium-ai"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/licium-ai/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/licium-ai/evidence"

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.