CAIS runs two distinct identity surfaces. (1) The MCP server at mcp.caisgroup.com is its own OAuth 2.1 authorization server: authorization-code + PKCE S256, refresh tokens, RFC 7591 dynamic client registration, RFC 7009 revocation, RFC 9728 protected-resource metadata, and bearer tokens in the Authorization header only. It supports client_id metadata documents. (2) The member platform behind members.caisgroup.com authenticates through an Auth0 tenant on the custom domain login.caisgroup.com, which publishes full OpenID Connect Discovery 1.0 metadata including MFA challenge and device-authorization endpoints. No API key, HTTP basic, or mutualTLS scheme is advertised on any public CAIS surface.
CAIS secures its APIs with oauth2 and openIdConnect across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).
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.