Install Jentic One Beta

Connect the Decidento API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Decidento API, 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi.decidento.com%2Fdecidento" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi.decidento.com%2Fdecidento" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Decidento API.

Search French companies by sector, region, headcount, and revenue via /companies

Resolve a company by CCCID via /companies/{companyCccid}/v2 or by collection of SIRENs

Stream business signals such as fundraising and hiring via /signals

Pull curated articles from the French business press via /articles

Fetch a collection of articles, companies, or signals by ID list in one call

GET STARTED

Start building with Decidento API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Decidento API for, with concrete tasks.

★ Prospect List Building for French B2B

Build a targeted prospect list of French companies that match a sector, headcount band, and region. /companies and /companies/v2 accept structured filters and return paginated results that can feed directly into a CRM or outbound sequencer. Useful for SDR teams targeting the French market who need richer firmographics than open Sirene data alone provides.

Search /companies/v2 for French SaaS companies between 50 and 200 employees in Île-de-France and return the first 100 results with SIREN, name, and revenue band

Trigger-Event Sales Intelligence

Monitor accounts for buying signals - fundraising rounds, executive moves, hiring surges, M&A - so reps can reach out at the right moment. /signals returns recent business events with the company id, signal type, and source link. Pair it with /signals/collection to refresh signals for a watchlist of target accounts in one call. This is the canonical use case Decidento was built for.

Pull /signals filtered to type=fundraising and date>=2025-01-01 for a watchlist of 50 SIRENs and surface any new events to the sales channel

Article-Based Account Briefings

Generate an account briefing before a sales call by pulling the latest curated articles about the company. /articles supports search by company id and date, and /articles/collection accepts an array of article ids for batch retrieval. Reps walk into meetings with a one-page summary of recent press coverage rather than skimming Google News.

Search /articles for company id 12345 in the last 30 days and produce a 5-bullet pre-meeting briefing

AI Agent CRM Enrichment

An AI agent uses Decidento via Jentic to enrich newly-created CRM contacts with company firmographics and recent signals. The agent searches Jentic by intent, loads the schema, and executes the call with the SIREN supplied at runtime. Jentic injects the X-AUTH-TOKEN and X-AUTH-ID headers so the agent never holds the credentials.

Search Jentic for 'look up French company by SIREN', load the schema, and resolve a list of 25 SIRENs into Decidento company records

Key Endpoints

13 endpoints — jentic publishes the only available openapi specification for decidento api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/companies

Search French companies with parameters

GET

/companies/{companyCccid}/v2

Look up a company by CCCID

GET

/companies/collection/v2

Resolve a collection of companies by SIREN

GET

/signals

Get recent business signals

GET

/articles

Search recent articles

GET

/articles/collection

Fetch a collection of articles by ID

GET

/companies

Search French companies with parameters

GET

/companies/{companyCccid}/v2

Look up a company by CCCID

GET

/companies/collection/v2

Resolve a collection of companies by SIREN

GET

/signals

Get recent business signals

GET

/articles

Search recent articles

GET

/articles/collection

Fetch a collection of articles by ID

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Decidento API by hand means handling its paired X-AUTH-TOKEN and X-AUTH-ID headers and mapping the company, signal, and article routes yourself. Through Jentic you install once, import Decidento from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Decidento puts the company id in the URL path (/companies/{companyCccid}/v2), so a rule can pin your agent to one company: it can read that company's firmographics and nothing else. You choose the operations it may call, so broad signal and article searches are only included if you add them.

Credential isolation

Your Decidento X-AUTH-TOKEN and X-AUTH-ID are stored once, encrypted, by your own Jentic One instance and injected as headers at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find French companies by SIREN' or 'list recent fundraising signals', and Jentic returns the matching Decidento operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Decidento API through Jentic.

Why is there no official OpenAPI spec for Decidento API?

Decidento does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Decidento API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Decidento API use?

Decidento uses paired API-key headers: X-AUTH-TOKEN and X-AUTH-ID, both issued by Decidento to your account. Both headers must be present on every request. Jentic stores the pair in the encrypted vault and injects them automatically so agents call the API without ever seeing the raw values.

Can I look up a company by SIREN through the Decidento API?

Yes - /companies/collection/v2 accepts a list of SIREN identifiers and returns matching company records, while /companies/{companyCccid}/v2 resolves a single company by Decidento's CCCID. Use the collection endpoint when batch-enriching CRM records to minimise the number of round trips.

What are the rate limits for the Decidento API?

Decidento applies plan-based rate limits that are not declared in the spec. Treat the API as moderate-throughput: batch IDs into /collection endpoints rather than calling per-record loops. If you receive a 429 response, back off and retry - Decidento returns a Retry-After header on throttled responses.

How do I monitor companies for fundraising signals through Jentic?

Run `pip install jentic`, search for 'monitor French company signals', load the GET /signals schema, and pass the company ids and signal type. Schedule the agent to run daily and pipe new signals into Slack or your CRM. Jentic handles the X-AUTH-TOKEN and X-AUTH-ID injection on every call.

Does the Decidento API cover companies outside France?

No. Decidento focuses on French firmographics, French press coverage, and business signals tied to French entities identified by SIREN or CCCID. For pan-European or US firmographic data, use a different provider - Decidento will return empty results for non-French queries.

Can I limit what my agent is allowed to do with the Decidento API?

Yes. Because you run Jentic One yourself, your own rules decide which Decidento operations and credentials the agent may use, so you can allow just company lookups like /companies/{companyCccid}/v2 while excluding broad /signals and /articles searches. Since the company id sits in the URL path, a rule can pin the agent to a single company so it reads that company's firmographics and nothing else. Your X-AUTH-TOKEN and X-AUTH-ID stay under your control and are only applied to the calls you permit.

Decidento API

Name: Decidento API
Brand: Decidento API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticData EnrichmentCompany DataapiKey13 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Pull French B2B company profiles, business signals, and sector news from Decidento. Authenticated via paired X-AUTH-TOKEN and X-AUTH-ID headers.

Use for: Search for French companies in a given sector and region, Look up a company by SIREN or CCCID, Find recent fundraising signals in fintech this month, Pull the latest articles about a target account

Not supported: Does not handle non-French companies, contact-level person data, or financial-statement filings - use for French B2B firmographics, business signals, and press articles only.

Jentic publishes the only available OpenAPI specification for Decidento API, keeping it validated and agent-ready. The Decidento API delivers French B2B sales-intelligence data: company firmographics, business signals (executive moves, fundraising, hiring spikes, M&A), and curated articles from the French business press. Sales and marketing teams use it to build prospect lists, monitor accounts for trigger events, and enrich CRM records with verified company data keyed on SIREN/CCCID identifiers. Authentication uses paired X-AUTH-TOKEN and X-AUTH-ID headers issued by Decidento.

Jentic One on Github View OpenAPI Document