Read AI · Authentication Profile
Read Ai Authentication
Authentication
Read AI's REST API and MCP server share one OAuth 2.1 authorization server (authn.read.ai) and one bearer-token contract. There are no static API keys: the provider explicitly documents this as a known limitation of the open beta, with personal access tokens planned for GA. Client credentials are obtained by RFC 7591 dynamic client registration; the user then completes a browser authorization-code flow with PKCE. Access tokens live 10 minutes and refresh tokens rotate on every use.
Read AI 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, refreshToken, clientCredentials, deviceCode, and implicit flow(s).
CompanyMeeting IntelligenceArtificial IntelligenceTranscriptionProductivityCollaborationModel Context ProtocolAgentsWebhooksSaaS
Methods: oauth2, openIdConnect
Schemes: 2
OAuth flows: authorizationCode, refreshToken, clientCredentials, deviceCode, implicit
API key in:
Security Schemes
OAuth2 oauth2
BearerToken http