Sirenic · OAuth Scopes
Sirenic OAuth Scopes
OAuth 2.0
probed
Sirenic 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.
Company DataBusiness RegistryKYBSanctions ScreeningFinancial DataCredit RiskVAT ValidationIBAN ValidationE-InvoicingPublic ProcurementOpen DataFranceEuropex402Agentic CommerceMCPA2ACompany
Scopes: 0
Flows:
Method: probed
Scopes (0)
Sirenic 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 2.0 exists for ONE surface: the MCP connector at https://api.sirenic.eu/mcp/connecteur used by Gemini CLI / Claude / ChatGPT style assistants. The REST API itself is not OAuth — it is x402 pay-per-call or an X-Api-Key. The OpenAPI declares no oauth2 securityScheme, so derive-oauth-scopes.py produced nothing; this file is read from the live discovery documents.
OAuth 2.0 exists for ONE surface: the MCP connector at https://api.sirenic.eu/mcp/connecteur used by Gemini CLI / Claude / ChatGPT style assistants. The REST API itself is not OAuth — it is x402 pay-per-call or an X-Api-Key. The OpenAPI declares no oauth2 securityScheme, so derive-oauth-scopes.py produced nothing; this file is read from the live discovery documents.
📄 Provider scope reference: https://api.sirenic.eu/confidentialite (section "Le connecteur MCP et l'autorisation OAuth")
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.