Chorus Pro API
Chorus Pro API as documented publicly: 3 operations. Contract generated from the documentation by API Evangelist (2026-10-27); not the provider's own document.
Work with this as data
Every API 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 apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/chorus-pro:chorus-pro-api"
All apis
curl "https://apis.io/api/v1/apis?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.
OpenAPI Specification
openapi: 3.1.0
info:
title: Chorus Pro API
version: '2026-10-27'
description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-27: 3 operation(s) read from 1 public documentation page(s) (each operation
names its page in x-source). This is not the provider''s published contract; Chorus Pro has published no machine-readable contract that the
pipeline could find. Engine: local.'
x-evidence-tiers:
code-example: 1
documentation: 2
pages-with-code: 1
pages-read: 1
x-generated-from: documentation
x-provenance: generated
x-authored-by: API Evangelist
x-generated: '2026-10-27'
x-generator: generate-contract-from-docs.py
x-engine: local
x-sources:
- https://www.data.gouv.fr/dataservices/api-sirene-open-data/discussions
paths:
/api-sirene/3.11/siret:
get:
operationId: get_api_sirene_3_11_siret
tags:
- Api Sirene
summary: GET /api-sirene/3.11/siret
x-source: https://www.data.gouv.fr/dataservices/api-sirene-open-data/discussions
parameters:
- name: q
in: query
required: false
schema:
type: string
responses:
'200':
description: Success (status as documented)
x-evidence:
kind: code-example
language: curl
snippet: 'curl --header "X-INSEE-Api-Key-Integration: XXXXXXXXXXXXXXX" https://api.insee.fr/api-sirene/3.11/siret?q=codePostalEtablissement:69140
AND libelleCommuneEtablissement:Rillieux-la-Pape
- Pouvez-vous me confirmer que pour chaque etablissement (siret) ou siren il y a une géométrie ?
- Pouvez-vous me confirmer que l’ensemble des points des etablissements seront remonté et pas seulement une partie ?
D'
/api-sirene/3.11/siret/{siret}:
get:
operationId: get_api_sirene_3_11_siret_siret
tags:
- Api Sirene
summary: GET https://api.insee.fr/api-sirene/3.11/siret/{siret}
x-source: https://www.data.gouv.fr/dataservices/api-sirene-open-data/discussions
parameters:
- name: siret
in: path
required: true
schema:
type: string
responses:
'200':
description: Success (status as documented)
x-evidence:
kind: documentation
/siret/{siret}:
get:
operationId: get_siret_siret
tags:
- Siret
summary: endpoint GET /siret/{siret}
x-source: https://www.data.gouv.fr/dataservices/api-sirene-open-data/discussions
parameters:
- name: siret
in: path
required: true
schema:
type: string
responses:
'200':
description: Success (status as documented)
x-evidence:
kind: documentation
components:
securitySchemes:
apiKey:
type: apiKey
in: header
name: X-INSEE-Api-Key-Integration
security:
- apiKey: []
tags:
- name: Api Sirene
- name: Siret