Infer by Flow7 · OAuth Scopes

Infer by Flow7 OAuth Scopes

OAuth 2.0 searched

Infer by Flow7 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.

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.

AI/ML inferenceLLM API gatewayResponses-compatible APICoding-agent toolingDeveloper toolsUsage-based billingPrepaid billingAgent-nativeAgent SkillsModel routing
Scopes: 0 Flows: Method: searched

Scopes (0)

Infer by Flow7 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.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-08-11'
method: searched
source: >-
  https://infer.flow7.org/openapi-public.json (listModels description) and https://infer.flow7.org/docs
description: >-
  Infer publishes a permission scope on its API keys, but it is NOT OAuth 2.0. There is no
  authorization server (both /.well-known/oauth-authorization-server and
  /.well-known/openid-configuration return 404), no token endpoint and no consent flow. The scope is a
  property attached to a workspace API key at creation time. This file records that honestly rather
  than leaving a documented permission model unrecorded.
oauth2: false
authorization_server: null
scheme: api-key-permission-scopes
scope_count: 1
scopes:
  - name: inference:write
    description: >-
      Required for the authenticated operations. Infer's OpenAPI states on listModels: "The key must
      carry the inference:write scope." createResponse uses the same bearerAuth scheme.
    operations:
      - listModels
      - createResponse
    granted_by: key creation inside a verified workspace
derived_from:
  - openapi/infer-by-flow7-public-api-openapi.yml
notes:
  - >-
    derive-oauth-scopes.py yields nothing for this provider by design — there is no oauth2
    securityScheme in the contract to derive from.
  - >-
    Spend ceilings (per-key daily and monthly microdollar limits) act as a second, orthogonal
    authorization axis. They are recorded in authentication/ and rate-limits/, not here, because they
    limit cost rather than capability.