generated: '2026-08-13'
method: searched
source: https://pagespeedonline.googleapis.com/$discovery/rest?version=v5
docs: https://developers.google.com/speed/docs/insights/v5/get-started#APIKey
note: >-
  The refined OpenAPI in this repo declares only apiKey security, so the mechanical
  derivation (derive-oauth-scopes.py) found zero oauth2 schemes. Google's own Discovery
  document — revision 20260811, probed 2026-08-13 — does declare an oauth2 block, with a
  single scope, and attaches that scope to the one method. The documented and recommended
  path is still the API key; OAuth here only carries an identity assertion, not a
  resource permission.
schemes:
  - name: oauth2
    source: https://pagespeedonline.googleapis.com/$discovery/rest?version=v5
    declared_in: auth.oauth2.scopes
    flows: []
    flow_note: >-
      Google Discovery documents list scopes without flow definitions; the flows are
      Google's standard OAuth 2.0 endpoints at accounts.google.com, not published in this
      document.
scopes:
  - scope: openid
    description: Associate you with your personal info on Google
    applies_to: [pagespeedonline.pagespeedapi.runpagespeed]
    sources:
      - https://pagespeedonline.googleapis.com/$discovery/rest?version=v5
    note: >-
      This is the OIDC identity scope, not a PageSpeed resource permission. The API grants
      no read/write scope surface — analysis is performed on public URLs and there is no
      user-owned data to authorize against.
summary:
  scope_count: 1
  resource_scopes: 0
  identity_scopes: 1
  primary_auth: api-key
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com