LibertAI · Authentication Profile

Libertai Authentication

Authentication

LibertAI declares 2 security scheme(s) across its OpenAPI definitions.

CompanyArtificial IntelligenceInferenceModel RoutingOpenAI-CompatibleDecentralizedConfidential Computingx402
Methods: Schemes: 2 OAuth flows: API key in:

Security Schemes

bearerApiKey http
scheme: bearer
x402 payment

Source

Authentication Profile

Raw ↑ 
generated: '2026-10-13'
method: searched
source: https://docs.libertai.io/quickstart.html
docs: https://docs.libertai.io/quickstart.html
note: The served OpenAPI declares no securitySchemes; the docs document Bearer API keys created in the Developer console, and x402 per-request payment as a keyless alternative.
schemes:
- name: bearerApiKey
  type: http
  scheme: bearer
  description: 'Authorization: Bearer $LIBERTAI_API_KEY; keys are created and topped up at https://console.libertai.io'
- name: x402
  type: payment
  description: Keyless pay-per-request; the API answers 402 Payment Required, the client retries with an EIP-712-signed USDC (Base) payment in the X-PAYMENT header.
  docs: https://docs.libertai.io/apis/x402.html

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/libertai-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. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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