RSL Collective · Authentication Profile

Rslcollective Org Authentication

Authentication

RSL Collective declares 3 security scheme(s) across its OpenAPI definitions.

CompanyAI LicensingContent LicensingCollective RightsPublishersRoyaltiesNonprofitRSL Standard
Methods: Schemes: 3 OAuth flows: API key in:

Security Schemes

olpClientBasic http
scheme: basic
olpClientCredentials oauth2
· flows:
capLicense http
scheme: License

Source

Authentication Profile

rslcollective-org-authentication.yml Raw ↑
generated: '2026-10-27'
method: searched
source: https://rslstandard.org/rsl
docs: https://rslstandard.org/rsl
related_docs:
- https://rslstandard.org/guide/license-servers
- https://rslcollective.org/developers
summary: >-
  The RSL Collective license server (https://api.rslcollective.org, named as the server in the
  collective's own RSL license examples and listed as an RSL License Server in the RSL Standard guide)
  is governed by the RSL 1.0 Open License Protocol (OLP), which the collective's editors publish at
  rslstandard.org. OLP is an OAuth 2.0 extension: clients authenticate to every OLP endpoint with HTTP
  Basic client credentials and receive an opaque License Token, which they then present to resource
  servers using the CAP `License` HTTP authentication scheme. Credentials are obtained by joining via the
  RSL Collective dashboard ("Join for free to request access to the RSL Collective licensing APIs and
  tools"). Not verified against the live server: no endpoint was called (auth endpoints are out of scope
  for probing).
schemes:
- name: olpClientBasic
  type: http
  scheme: basic
  applies_to: [POST /token, POST /introspect, POST /key]
  description: >-
    "Clients MUST authenticate to all OLP endpoints using the HTTP Basic scheme as defined in [ RFC 7617 ].
    The Authorization header MUST contain a Base64-encoded string of the form client_id:client_secret."
  credentials_issuance: >-
    "Each client application that interacts with a License Server is assigned a unique client_id and
    client_secret by the server operator during registration"
  failure: HTTP 401 with an invalid_client JSON error object
- name: olpClientCredentials
  type: oauth2
  flows:
    clientCredentials:
      tokenUrl: https://api.rslcollective.org/token
      scopes: {}
  description: >-
    "This endpoint uses the OAuth 2.0 Token Endpoint defined in [ RFC 6749 ] with the client_credentials
    grant type." Requests carry grant_type, license (URL-encoded RSL <license> XML), optional license_type
    and resource. The response returns access_token, token_type "License" and expires_in (0 = non-expiring).
  token_url_note: tokenUrl is the documented /token path joined to the server attribute https://api.rslcollective.org.
- name: capLicense
  type: http
  scheme: License
  description: >-
    Crawler Authorization Protocol: "It introduces a new authentication scheme, License , which uses the
    standard Authorization and WWW-Authenticate headers to transmit and validate License Tokens over HTTPS
    connections." Used by crawlers toward publisher resource servers; failures return 401 Unauthorized or
    402 Payment Required with a Link header to the governing RSL license.

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact 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 security artifact
curl "https://apis.io/api/v1/security/rslcollective-org-authentication"
All security posture
curl "https://apis.io/api/v1/security?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.

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