Realtime Robotics OAuth Scopes

OAuth 2.0 probed

Realtime Robotics 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.

CompanyRoboticsMotion PlanningIndustrial AutomationManufacturingSimulationCollision AvoidanceRobot ProgrammingMachine VisionDigital Twin

Scopes: 0 Flows: Method: probed

Scopes (0)

Realtime Robotics 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: https://resolver.rtr.ai/docs/user_guide/resolver/log_in/

Source

OAuth Scopes

generated: '2026-08-26'
method: probed
source: https://clerk.rtr.ai/.well-known/openid-configuration
docs: https://resolver.rtr.ai/docs/user_guide/resolver/log_in/
name: Realtime Robotics OAuth scopes
description: >-
  Realtime Robotics declares no oauth2 securitySchemes anywhere - it publishes no
  OpenAPI at all - so this scope list is read directly from the OpenID Connect
  discovery document its identity service publishes at clerk.rtr.ai. These are the
  scopes the Resolver Cloud identity layer advertises; they are identity and
  organisation scopes, not resource scopes over a Resolver API, and no scope-to-endpoint
  mapping is published because the Resolver REST API itself is documented as not yet
  publicly available.
issuer: https://clerk.rtr.ai
applies_to: realtime-robotics:resolver-cloud
scopes:
- name: openid
  description: OpenID Connect - request an ID token for the authenticated subject.
- name: profile
  description: Profile claims (name, given_name, family_name, preferred_username, picture).
- name: email
  description: Email address and email_verified claim.
- name: offline_access
  description: Issue a refresh token so the client can renew access without re-prompting.
- name: user:org:read
  description: Read the organisation membership of the authenticated user (org_id claim).
- name: public_metadata
  description: Read the user's public metadata.
- name: private_metadata
  description: Read the user's private metadata.
claims_supported:
- sub
- iss
- aud
- exp
- iat
- email
- email_verified
- name
- given_name
- family_name
- preferred_username
- picture
- org_id
x-evidence:
  fetched: '2026-08-26'
  url: https://clerk.rtr.ai/.well-known/openid-configuration
  http_status: 200
  content_type: application/json

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/realtime-robotics-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.