Context.dev · OAuth Scopes

Context.dev OAuth Scopes

OAuth 2.0 searched

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

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.

Web ScrapingBrand IntelligenceData EnrichmentAI AgentsWeb DataClassificationWebsite MonitoringCompany DataDeveloper ToolsAPIs

Scopes: 2 Flows: Method: searched

Scopes (2)

Scope	Description	Flows
api.read	Read access to Context.dev API endpoints (brand lookup, web scrape/crawl, search, enrichment, and related read operations).
api.write	Write access for mutating API operations (e.g. creating/updating/deleting monitors). Agent credentials are issued with both api.read and api.write after the claim ceremony.

📄 Provider scope reference: https://www.context.dev/auth.md

Source

OAuth Scopes

generated: '2026-07-18'
method: searched
source: >-
  https://www.context.dev/.well-known/oauth-authorization-server and
  https://www.context.dev/auth.md
docs: https://www.context.dev/auth.md
schemes:
- name: AgentAuth
  source: well-known/contextdev-oauth-authorization-server.json
  authorization_server: https://www.context.dev
  token_endpoint: https://www.context.dev/oauth2/token
  revocation_endpoint: https://www.context.dev/oauth2/revoke
  grant_types:
  - urn:ietf:params:oauth:grant-type:jwt-bearer
  - urn:workos:agent-auth:grant-type:claim
scopes:
- scope: api.read
  description: >-
    Read access to Context.dev API endpoints (brand lookup, web scrape/crawl,
    search, enrichment, and related read operations).
  sources:
  - well-known/contextdev-oauth-authorization-server.json
- scope: api.write
  description: >-
    Write access for mutating API operations (e.g. creating/updating/deleting
    monitors). Agent credentials are issued with both api.read and api.write
    after the claim ceremony.
  sources:
  - well-known/contextdev-oauth-authorization-server.json
note: >-
  Scopes are exposed via the OAuth2 agent-auth (service_auth) flow, not via the
  static-API-key path. The OpenAPI declares only bearerAuth (http bearer); the
  scope surface is documented in the well-known metadata and auth.md.