Generixgroup8 AFNOR Directory Service
Browse all Swaggerhub Generixgroup8 APIs★ Only Publicly Available OpenAPI DocumentProductivityNote Takingbearer, oauth29 EndpointsREST
For Agents
Programmatically siren search (or legal unit), consult a siren (legal unit) by siren number. Covers 9 operations with bearer, oauth2 authentication.
Use for: I need to siren search (or legal unit), I want to consult a siren (legal unit) by siren number, Search for for a siret (facility), Find all gets a siret (facility) by siret number
Not supported: Does not handle payments, communications, or crm — use for productivity only.
The __Directory Service__ API allows you to: - View and search for companies (SIREN) - View and search for establishments (SIRET) - View, and search for routing codes - View, and search for directory entries **Authentication :** Each endpoint must be called with an access token (Bearer). This token is retrieved by a call to a token URL. --- Siren Company by Siren number - `POST /siren/search` => S. The API exposes 9 endpoints secured with bearer, oauth2 authentication.
Install Jentic One Beta
Connect the AFNOR Directory Service to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AFNOR Directory Service, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AFNOR Directory Service API.
SIREN search (or legal unit)
Consult a siren (legal unit) by SIREN number
Search for a SIRET (facility)
Gets a siret (facility) by SIRET number
Get a routing code by SIRET and routing identifier
Use Cases
Patterns agents use AFNOR Directory Service API for, with concrete tasks.
★ Productivity Operations
Use the AFNOR Directory Service to perform productivity operations programmatically. The API provides 9 endpoints covering core functionality including siren search (or legal unit), consult a siren (legal unit) by siren number, search for a siret (facility).
Call POST /v1/siren/search to siren search (or legal unit)
Automated Siren Management
Automate siren operations by combining multiple AFNOR Directory Service endpoints. Agents can consult a siren (legal unit) by siren number and then search for a siret (facility) in a single workflow.
Call GET /v1/siren/code-insee:{siren} to consult a siren (legal unit) by siren number, then verify the result
AI Agent Integration via Jentic
AI agents discover and call AFNOR Directory Service endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer, oauth2 tokens manually.
Search Jentic for 'siren search (or legal unit)', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
9 endpoints — the __directory service__ api allows you to: - view and search for companies (siren) - view and search for establishments (siret) - view, and search for routing codes - view, and search for directory entries **authentication :** each endpoint must be called with an access token (bearer).
METHOD
PATH
DESCRIPTION
POST
/v1/siren/search
SIREN search (or legal unit)
GET
/v1/siren/code-insee:{siren}
Consult a siren (legal unit) by SIREN number
POST
/v1/siret/search
Search for a SIRET (facility)
GET
/v1/siret/code-insee:{siret}
Gets a siret (facility) by SIRET number
POST
/v1/routing-code/search
Search for a routing code
GET
/v1/routing-code/siret:{siret}/code:{routing-identifier}
Get a routing code by SIRET and routing identifier
POST
/v1/directory-line/search
Search for a directory line
GET
/v1/directory-line/code:{addressing-identifier}
Get a directory line.
POST
/v1/siren/search
SIREN search (or legal unit)
GET
/v1/siren/code-insee:{siren}
Consult a siren (legal unit) by SIREN number
POST
/v1/siret/search
Search for a SIRET (facility)
GET
/v1/siret/code-insee:{siret}
Gets a siret (facility) by SIRET number
POST
/v1/routing-code/search
Search for a routing code
GET
/v1/routing-code/siret:{siret}/code:{routing-identifier}
Get a routing code by SIRET and routing identifier
POST
/v1/directory-line/search
Search for a directory line
GET
/v1/directory-line/code:{addressing-identifier}
Get a directory line.
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AFNOR Directory Service bearer, oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'siren search (or legal unit)') and Jentic returns the matching AFNOR Directory Service operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct AFNOR Directory Service integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AFNOR Directory Service API through Jentic.
What authentication does the AFNOR Directory Service use?
The AFNOR Directory Service uses bearer, oauth2 authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I siren search (or legal unit) with the AFNOR Directory Service?
Yes. Use the POST /v1/siren/search endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the AFNOR Directory Service?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I siren search (or legal unit) through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'siren search (or legal unit)'. Jentic returns the matching AFNOR Directory Service operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the AFNOR Directory Service have?
The AFNOR Directory Service exposes 9 endpoints covering siren, siret, routing code operations.
GET STARTED