Terabase Energy · OAuth Scopes

Terabase Energy OAuth Scopes

OAuth 2.0 searched

Terabase Energy publishes 2 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Terabase Energy API on a user’s behalf.

Tokens are issued from https://terabase-prd.auth.us-west-2.amazoncognito.com/oauth2/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.

solarrenewable-energyenergy-modelingutility-scale-solarsimulationphotovoltaicsconstruction-technologygeospatialterrain-analysisclimate-techmcpenergy-storage

Scopes: 2 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://terabase-prd.auth.us-west-2.amazoncognito.com/oauth2/token

Flows
clientCredentials

Scopes (2)

Scope	Description	Flows
transactions/get	Read access to the PlantPredict API surface.	clientCredentials
transactions/post	Write access to the PlantPredict API surface.	clientCredentials

📄 Provider scope reference: https://docs.plantpredict.com/api-docs/api_quick_start_guide

Source

OAuth Scopes

generated: '2026-08-05'
method: searched
source: https://docs.plantpredict.com/api-docs/intro
docs: https://docs.plantpredict.com/api-docs/api_quick_start_guide
note: >-
  The OpenAPI declares only a `bearerAuth` HTTP bearer scheme, so a purely spec-derived pass finds no OAuth surface.
  The scopes below are taken from the provider's own written authentication section and the published Agent Skill,
  which both name the Cognito token endpoint and the two scopes explicitly.
schemes:
- name: PlantPredict OAuth 2.0
  provider: AWS Cognito (terabase-prd)
  source: https://docs.plantpredict.com/api-docs/intro
  flows:
  - flow: clientCredentials
    tokenUrl: https://terabase-prd.auth.us-west-2.amazoncognito.com/oauth2/token
    client_auth: basic
scopes:
- scope: transactions/get
  description: Read access to the PlantPredict API surface.
  flows: [clientCredentials]
  sources: [https://docs.plantpredict.com/api-docs/intro]
- scope: transactions/post
  description: Write access to the PlantPredict API surface.
  flows: [clientCredentials]
  sources: [https://docs.plantpredict.com/api-docs/intro]
guidance: >-
  Terabase instructs callers to request both scopes to access the entire surface. Scopes are coarse — read vs write
  across the whole API — with no per-resource granularity. Role, not scope, gates the elevated operations: the spec's
  403 Forbidden description notes that status-change endpoints "require elevated privileges that not every API client
  is granted".
mcp_scopes:
  server: https://mcp.plantpredict.terabase.energy
  scopes_supported: []
  source: well-known/terabase-energy-mcp-oauth-protected-resource.json
  note: The MCP protected-resource metadata advertises an empty scopes_supported array.