Sirenic · OAuth Scopes

Sirenic OAuth Scopes

OAuth 2.0 probed

Sirenic publishes 1 OAuth 2.0 scope. Scopes are the fine-grained permissions an application requests at authorization time to act against the Sirenic API on a user’s behalf.

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: 1 Flows: Method: probed

Scopes (1)

Scope	Description	Flows
mcp	Call the data routes on behalf of the account holder, against the account's free monthly quota then its prepaid credit balance. Does NOT grant the e-mail address, invoices, or the right to top up or close the account (privacy policy, MCP connector section). The only scope the authorization server advertises.

📄 Provider scope reference: https://api.sirenic.eu/confidentialite (section "Le connecteur MCP et l'autorisation OAuth")

Source

OAuth Scopes

generated: '2026-09-19'
method: probed
source: https://api.sirenic.eu/.well-known/oauth-authorization-server (RFC 8414) and /.well-known/oauth-protected-resource
  (RFC 9728)
docs: https://api.sirenic.eu/confidentialite (section "Le connecteur MCP et l'autorisation OAuth")
note: '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.'
authorization_server:
  issuer: https://api.sirenic.eu
  authorization_endpoint: https://api.sirenic.eu/compte/connecteur
  token_endpoint: https://api.sirenic.eu/oauth/jeton
  registration_endpoint: https://api.sirenic.eu/oauth/enregistrement
  revocation_endpoint: https://api.sirenic.eu/oauth/revoquer
  grant_types_supported:
  - authorization_code
  - refresh_token
  response_types_supported:
  - code
  code_challenge_methods_supported:
  - S256
  token_endpoint_auth_methods_supported:
  - private_key_jwt
  - none
  - client_secret_post
  - client_secret_basic
  client_id_metadata_document_supported: true
  dynamic_client_registration: true
protected_resource:
  resource: https://api.sirenic.eu
  resource_name: Sirenic MCP
  authorization_servers:
  - https://api.sirenic.eu
  bearer_methods_supported:
  - header
token_lifetimes:
  access_token: 1 hour
  refresh_token: expires after 90 days without use
  source: https://api.sirenic.eu/confidentialite
scopes:
- name: mcp
  description: Call the data routes on behalf of the account holder, against the account's free monthly quota then
    its prepaid credit balance. Does NOT grant the e-mail address, invoices, or the right to top up or close the
    account (privacy policy, MCP connector section). The only scope the authorization server advertises.
  source: scopes_supported in both discovery documents
scope_count: 1

Work with this as data

Every scope set 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 oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set 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 scope set

curl "https://apis.io/api/v1/scopes/sirenic-eu-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?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.

GitHub Google LinkedIn

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