Loa Healthcare Pricing API · OAuth Scopes

Loa Healthcare Pricing API OAuth Scopes

OAuth 2.0 searched

Loa Healthcare Pricing API 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.

HealthcarePrice Transparencymedical pricingHospitalsProvidersProvider Directoryhospital pricesCPTHCPCSMCPagent-nativeOpenAPIllms-txt
Scopes: 0 Flows: Method: searched

Scopes (0)

Loa Healthcare Pricing API 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.

OAuth applies to the MCP surface only; the REST OpenAPI declares a single optional apiKey scheme with no oauth2 flows (derive-oauth-scopes found no spec-declared scopes). Scopes below are the identity scopes the protected-resource metadata advertises — there are no resource-permission scopes; access tiers (authenticated / suggestions / linked provider) are enforced per-account, not per-scope.

📄 Provider scope reference: https://www.loacare.com/mcp

Source

OAuth Scopes

Raw ↑ 
generated: '2026-09-03'
method: searched
source: https://www.loacare.com/.well-known/oauth-protected-resource
docs: https://www.loacare.com/mcp
note: >-
  OAuth applies to the MCP surface only; the REST OpenAPI declares a single optional apiKey scheme with
  no oauth2 flows (derive-oauth-scopes found no spec-declared scopes). Scopes below are the identity
  scopes the protected-resource metadata advertises — there are no resource-permission scopes; access
  tiers (authenticated / suggestions / linked provider) are enforced per-account, not per-scope.
authorization_server: https://eknkfyyjqxuvgdzocccu.supabase.co/auth/v1
scopes:
  - name: openid
    description: OpenID Connect authentication for MCP tool calls.
  - name: email
    description: Submitter email identity, used by reviewed update submissions.
  - name: profile
    description: Basic profile identity for linked-provider affiliation signals.

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/loa-healthcare-pricing-api-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.