RunBuggy · OAuth Scopes

RunBuggy OAuth Scopes

OAuth 2.0 searched

RunBuggy 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.

CompanyAutomotiveLogisticsTransportationVehicle ShippingMarketplaceSupply ChainFleetTMSFreight

Scopes: 0 Flows: Method: searched

Scopes (0)

RunBuggy 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

generated: '2026-08-05'
method: searched
source: well-known/runbuggy-oauth-authorization-server.json, https://docs.runbuggy.com/docs/shipping/d483faef38c3b-embedding-i-frame-order-status
summary: 'RunBuggy has almost no scope surface. The REST Shippers API is bearer-token
  authenticated with no scopes at all — permission is a property of the token holder''s
  company, not of the request. Exactly one scope value is published anywhere in the
  estate, and the OAuth authorization server that fronts the MCP layer publishes none.'
model: opaque-bearer-token-no-scopes
rest_api:
  scopes_supported: []
  detail: 'securityDefinitions on all three Swagger 2.0 documents is a single
    `apiKey in header` named Authorization. No oauth2 flow, no scopes object, and no
    per-operation security requirement differentiation — every operation carries the
    same blanket requirement.'
  authorization_model: 'Authority is company-scoped and relationship-granted. A company
    can act for another company only after RunBuggy establishes that authorization
    out-of-band ("Your Runbuggy support contact can work with you to establish this
    authorization"), and the caller then discovers it via the Companies API.'
  docs: https://docs.runbuggy.com/docs/shipping/94fced2e96c5f-placing-an-order-for-another-company
scopes:
- name: openid
  used_by: embeddable order-status iframe token exchange
  description: The only scope value published by RunBuggy. Requested in the body of the
    platform oauth2/token call to mint the short-lived JWT that authorizes an
    unauthenticated buyer or seller to view a single order's status in an iframe.
  grants: read access to one order's status for the token lifetime (documented as 60
    seconds)
  source: https://docs.runbuggy.com/docs/shipping/d483faef38c3b-embedding-i-frame-order-status
mcp_authorization_server:
  issuer: https://apps.runbuggy.com/runbuggy/mcp-datascience
  metadata: well-known/runbuggy-oauth-authorization-server.json
  scopes_supported: null
  detail: The RFC 8414 metadata document omits `scopes_supported` entirely. An MCP
    client performing dynamic client registration has no published vocabulary to request
    against, and the protected-resource metadata that would normally carry it is not
    served.
gaps:
- No scope or permission reference page exists on docs.runbuggy.com.
- The REST API has no scopes, so a bearer token is all-or-nothing across all 28
  operations — including order creation and cancellation.
- The MCP authorization server advertises no scopes_supported.
x-evidence:
  fetched: '2026-08-05'
  probes:
  - url: https://apps.runbuggy.com/.well-known/oauth-authorization-server
    http_status: 200
  - url: https://docs.runbuggy.com/docs/shipping/d483faef38c3b-embedding-i-frame-order-status
    http_status: 200

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/runbuggy-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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