Licium · Authentication Profile

Licium Authentication

Authentication

Licium secures its APIs with apiKey, http, and oauth2 across 4 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

CompanyHealthcareSoftware-as-a-ServiceCredentialingAutomation
Methods: apiKey, http, oauth2 Schemes: 4 OAuth flows: authorizationCode API key in: header

Security Schemes

BearerAuth http
scheme: bearer
McpOAuth oauth2
· flows: authorizationCode
PayerFollowUpToken apiKey
· in: header (X-Payer-Follow-Up-Token)
ReportDeleteCredential apiKey
· in: header (X-Licium-Report-Delete-Key)

Source

Authentication Profile

Raw ↑
generated: '2026-11-15'
method: derived
source: openapi/licium-ai-openapi.json
summary:
  types:
  - apiKey
  - http
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - authorizationCode
schemes:
- name: BearerAuth
  type: http
  scheme: bearer
  description: API key issued by Licium. Request one at hello@licium.ai. Never put keys in URLs.
  sources:
  - openapi/licium-ai-openapi.json
- name: McpOAuth
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://www.licium.ai/oauth/authorize
    tokenUrl: https://www.licium.ai/oauth/token
    scopes: 2
  description: Sign-in for the hosted MCP (/mcp, /mcp/claude, /mcp/chatgpt). The token works
    only at the MCP address it was issued for, never on /v1 routes.
  sources:
  - openapi/licium-ai-openapi.json
- name: PayerFollowUpToken
  type: apiKey
  in: header
  parameter: X-Payer-Follow-Up-Token
  description: The follow-up's access_token, returned once by POST /v1/payer-follow-ups. It
    opens that follow-up only. GET calls also take it as ?token= (the links in our emails carry
    one). A session signed in on licium.ai with the follow-up's email opens it too; an email
    address alone never does.
  sources:
  - openapi/licium-ai-openapi.json
- name: ReportDeleteCredential
  type: apiKey
  in: header
  parameter: X-Licium-Report-Delete-Key
  description: Anonymous report delete credential returned once by POST /v1/check when save=true.
    Never put it in a URL.
  sources:
  - openapi/licium-ai-openapi.json

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • 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 security artifact
curl "https://apis.io/api/v1/security/licium-ai-authentication"
All security posture
curl "https://apis.io/api/v1/security?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.