AFNOR Directory Service

Name: AFNOR Directory Service API
Brand: AFNOR Directory Service
Availability: InStock

★ Only Publicly Available SpecProductivityNote 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.

Quickstart

Get started with AFNOR Directory Service in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"siren search (or legal unit)"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

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

GET STARTED

Start building with AFNOR Directory Service API

Explore with Jentic

View OpenAPI Spec

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.

Jentic publishes the only available OpenAPI specification for AFNOR Directory Service, keeping it validated and agent-ready.

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.

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

Why though 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.

Alternative

Asana

Alternative productivity API

Choose Asana when you need a different approach to productivity operations

Alternative

Monday

Alternative productivity API

Choose Monday when you need a different approach to productivity operations

Complementary

Clickup

Complementary productivity API

Choose Clickup when you need a complementary approach to productivity operations

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.