Cerenovus · Authentication Profile

Cerenovus Authentication

Authentication

Cerenovus secures its APIs with oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

CompanyArtificial IntelligenceAI AgentsEnterprise SoftwareDecision IntelligenceKnowledge ManagementPrivate EquityDue DiligenceModel Context ProtocolY Combinator
Methods: oauth2 Schemes: 1 OAuth flows: authorizationCode API key in:

Security Schemes

CerenovusOAuth oauth2
· flows: authorizationCode

Source

Authentication Profile

cerenovus-authentication.yml Raw ↑ 
generated: '2026-08-14'
method: probed
source: https://api.cerenovus.ai/.well-known/oauth-authorization-server
note: >-
  Derived entirely from the provider's own anonymous OAuth discovery documents on
  api.cerenovus.ai, not from documentation — Cerenovus publishes no developer docs or
  auth page. There is no OpenAPI to derive securitySchemes from; this profile
  describes the only authenticated surface found, the OAuth 2.1 authorization server
  guarding the MCP endpoint at https://api.cerenovus.ai/mcp.
summary:
  types:
  - oauth2
  api_key_in: []
  oauth2_flows:
  - authorizationCode
  pkce: true
  dynamic_client_registration: true
schemes:
- name: CerenovusOAuth
  type: oauth2
  source: https://api.cerenovus.ai/.well-known/oauth-authorization-server
  issuer: https://api.cerenovus.ai/
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api.cerenovus.ai/authorize
    tokenUrl: https://api.cerenovus.ai/token
    refreshUrl: https://api.cerenovus.ai/token
    scope_count: 9
  revocation_endpoint: https://api.cerenovus.ai/revoke
  registration_endpoint: https://api.cerenovus.ai/register
  response_types_supported:
  - code
  grant_types_supported:
  - authorization_code
  - refresh_token
  code_challenge_methods_supported:
  - S256
  token_endpoint_auth_methods_supported:
  - client_secret_post
  - none
protected_resources:
- resource: https://api.cerenovus.ai/
  resource_name: Compendium vault
  authorization_servers:
  - https://api.cerenovus.ai/
  metadata: https://api.cerenovus.ai/.well-known/oauth-protected-resource
challenge:
  status: 401
  header: WWW-Authenticate
  scheme: Bearer
  carries_resource_metadata: true
  example: >-
    Bearer error="invalid_token", error_description="Missing Authorization header",
    resource_metadata="https://api.cerenovus.ai/.well-known/oauth-protected-resource"
x-evidence:
  fetched: '2026-08-14'
  probes:
  - url: https://api.cerenovus.ai/.well-known/oauth-authorization-server
    http_status: 200
  - url: https://api.cerenovus.ai/.well-known/oauth-protected-resource
    http_status: 200
  - url: https://api.cerenovus.ai/authorize
    http_status: 400
    note: rejects a request with no client_id, confirming a live authorization endpoint
  - url: https://api.cerenovus.ai/token
    http_status: 405
    note: GET rejected; POST-only token endpoint
  - url: https://api.cerenovus.ai/register
    http_status: 405
    note: GET rejected; POST-only dynamic client registration endpoint