Ex-Human · Authentication Profile

Ex Human Authentication

Authentication

Ex-Human secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyArtificial IntelligenceConversational AIAI CompanionsGenerative AIText to SpeechImage GenerationVideo GenerationAvatarsMultimodal
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

HTTPBearer http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-19'
method: searched
source: openapi/ex-human-openapi.yml
docs: https://docs.exh.ai/reference/getting-started-with-your-api
summary:
  types:
  - http
  http_schemes:
  - bearer
  notes: >-
    All Ex-Human API operations require an HTTP Bearer token. Create a Bearer token in the admin
    console at https://admin.exh.ai/ and send it as `Authorization: Bearer <your-token>` on every
    request. There is a single provider-wide security scheme (HTTPBearer); no OAuth 2.0, no OAuth
    scopes, and no API-key query/header alternative are documented.
schemes:
- name: HTTPBearer
  type: http
  scheme: bearer
  admin_url: https://admin.exh.ai/
  applied_to: all operations
  sources:
  - openapi/ex-human-openapi.yml