Entire · Authentication Profile

Entire Authentication

Authentication

Entire secures its APIs with oauth2-device and bearer-token across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the deviceAuthorization flow(s).

CompanyDeveloper ToolsDeveloper PlatformGitGit HostingVersion ControlSource ControlAI AgentsAgent InfrastructureCLI
Methods: oauth2-device, bearer-token Schemes: 2 OAuth flows: deviceAuthorization API key in:

Security Schemes

EntireDeviceAuth oauth2
EntireToken http
scheme: bearer

Source

Authentication Profile

entire-authentication.yml Raw ↑ 
generated: '2026-07-19'
method: searched
source: https://github.com/entireio/cli + https://docs.entire.io/ (Security and privacy)
note: >-
  Entire exposes no public REST API, so this profile is derived from the platform's
  documented CLI/client authentication rather than from an OpenAPI securityScheme.
summary:
  types: [oauth2-device, bearer-token]
  api_key_in: []
  oauth2_flows: [deviceAuthorization]
schemes:
- name: EntireDeviceAuth
  type: oauth2
  flow: deviceAuthorization
  command: entire login
  description: >-
    The Entire CLI authenticates with the platform via a device authorization flow
    (`entire login`), which mints a token used for subsequent Checkpoint/session sync.
  sources: [https://github.com/entireio/cli]
- name: EntireToken
  type: http
  scheme: bearer
  token_env: ENTIRE_TOKEN
  token_storage: [os-keyring, file-backed store, environment variable]
  description: >-
    Access token issued by device auth. Stored in the OS keyring by default, with
    file-backed and ENTIRE_TOKEN environment-variable fallbacks for CI/headless use.
  sources: [https://github.com/entireio/cli]