Parea AI · OAuth Scopes

Parea AI OAuth Scopes

OAuth 2.0 derived

Parea AI uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

Tokens are issued from token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

LLMEvaluationObservabilityTestingPrompt ManagementAI EngineeringMachine LearningTracingExperimentationHuman Feedback
Scopes: 0 Flows: password Method: derived

OAuth endpoints

Token URL
token
Flows
password

Scopes (0)

Parea AI implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

Parea authenticates with a per-organization API key passed in the x-api-key header (or SDK constructor); no OAuth scopes are used or documented (https://docs.parea.ai/api-reference/authentication).

📄 Provider scope reference: https://docs.parea.ai/api-reference/authentication

Source

OAuth Scopes

parea-scopes.yml Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/parea-rest-api-openapi.yml
docs: https://docs.parea.ai/api-reference/authentication
note: Parea authenticates with a per-organization API key passed in the x-api-key
  header (or SDK constructor); no OAuth scopes are used or documented
  (https://docs.parea.ai/api-reference/authentication).
schemes:
- name: OAuth2PasswordBearer
  source: openapi/parea-rest-api-openapi.yml
  flows:
  - flow: password
    tokenUrl: token
scopes: []