generated: '2026-07-25'
method: searched
source: openapi/moodys-rms-data-bridge-openapi.json, openapi/moodys-rms-location-intelligence-openapi.yaml,
  openapi/moodys-rms-risk-modeler-openapi.yml
docs: https://developer.rms.com/platform/docs/authentication-and-authorization
summary:
  types:
  - apiKey
  - accessToken
  api_key_in:
  - header
  self_serve: false
  recommended: apiKey
schemes:
- name: RMS_Auth
  type: apiKey
  in: header
  parameter: Authorization
  description: An API key is a token that enables a client application to make requests to tenant
    applications running on Intelligent Risk Platform.
  sources:
  - openapi/moodys-rms-data-bridge-openapi.json
  - openapi/moodys-rms-location-intelligence-openapi.yaml
  - openapi/moodys-rms-risk-modeler-openapi.yml
methods:
- method: api-key
  header: Authorization
  prefix: none
  lifetime: long-lived
  bound_to: A project or client application, not a user account.
  issuance: >-
    Created and managed by tenant administrators in Admin Center. Developers must contact their tenant
    administrator to acquire an API key. There is no self-serve signup, free tier or sandbox.
  recommended_for: production
  example: |-
    curl --location --request GET 'https://{host}/riskmodelerv1/datasources' \
      --header 'Authorization: {api_key}'
  admin_docs: https://support.rms.com/o/html-doc/OLH_ContentRLRB_Online_Library/Content/IRP_Admin/GeneratingAPIKeys.htm
- method: access-token
  header: Authorization
  style: bearer
  lifetime: session
  bound_to: A user account, accessed on that user's behalf.
  recommended_for: evaluation and testing
  note: >-
    The provider explicitly recommends API keys over tokens for production because keys are long-lived
    and require no refresh. No authorization endpoint, token endpoint, flow or scope list is published,
    so this is not a discoverable OAuth 2.0 profile — hence no scopes/ artifact.
authorization:
  model: role-based access control with group-based access rights
  description: >-
    The API key or access token encodes the access rights and permissions granted to the client. A key is
    mapped to one or more groups and inherits the roles assigned to those groups. Entitlements gate which
    products (Risk Modeler, UnderwriteIQ, ExposureIQ, TreatyIQ) the caller can reach.
  notable_roles:
  - name: IRP Agentic Tools User
    grants:
    - {action: Access Platform MCP Server, level: read}
    - {action: Execute APIs with Platform MCP Server, level: write}
    note: Required for any MCP client connecting to the Platform MCP Server.
  docs: https://developer.rms.com/platform/docs/access-control
oauth2: false
openid_connect: false
mutual_tls: false
scopes_published: false
discovery:
  openid_configuration: not-served
  oauth_authorization_server: not-served
  note: See well-known/moodys-rms-well-known.yml for the full probe record.
hosts:
- https://api-use1.rms.com
- https://api-euw1.rms.com
transport_security: >-
  All calls to and from the Intelligent Risk Platform are encrypted. TLS 1.3 was negotiated on
  api-use1.rms.com and developer.rms.com on 2026-07-25.