Know of an official OpenAPI document? Contribute it →
For Agents
Verify French citizens' official benefit, household, student, and employment status from government registries, with FranceConnect consent. Authenticates with an API key and a bearer token.
Use for: Verify whether an applicant receives the RSA benefit, Check a household's family quotient for a means-tested rate, Confirm a student's enrollment and scholarship status, Look up disabled adult allowance status for eligibility
Not supported: Does not handle benefit payments, document storage, or identity enrollment. Use for verifying French citizens' administrative and benefit status only.
The API Particulier service returns official administrative and benefit status for French citizens from government data sources, with the citizen's consent through FranceConnect. It confirms whether a person receives benefits such as RSA, the activity bonus, the disabled adult allowance, or solidarity health cover, returns a household's family quotient from CAF or MSA records, and verifies student and scholarship status. Status and ping operations let a service check eligibility and the availability of the upstream registries.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Particulier, 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%2Fparticulier.api.gouv.fr%2Fparticulier" | shStep 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%2Fparticulier.api.gouv.fr%2Fparticulier" | 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.
What an agent can do with API Particulier API.
Verify a citizen's disabled adult allowance (AAH) status
Check revenu de solidarite active (RSA) and activity-bonus status
Look up a household's family quotient from CAF or MSA records
Confirm student and scholarship status for an applicant
Verify eligibility for complementary health cover solidarity (C2S)
Read France Travail payment and job-seeker status
Patterns agents use API Particulier API for, with concrete tasks.
★ AI Agent Eligibility Checks
A public-service or social-benefit agent can confirm an applicant's official status before granting a means-tested rate or aid, through Jentic. The agent searches for the right status operation, supplies the citizen's identifiers through the FranceConnect token, and reads back the authoritative status, without the developer wiring the two credentials or reading the API Particulier reference docs.
Call GET /api/v2/revenu-solidarite-active to confirm an applicant's RSA status
Means-Tested Pricing
Local services set fees by household resources. The family-quotient operations return the CAF or MSA quotient for a household, so an agent can resolve the correct tariff band for a service such as childcare or school meals from the official figure rather than a self-declared one.
Call GET /api/v2/composition-familiale to read a household's family quotient
Student and Scholarship Verification
Universities and youth-aid programs confirm who is enrolled and who holds a scholarship. The student and enrollment operations return the official status, so an agent can validate an application against the registry before issuing a benefit or discount.
Call GET /api/v2/etudiants to confirm an applicant's student status
16 endpoints — the api particulier service returns official administrative and benefit status for french citizens from government data sources, with the citizen's consent through franceconnect.
METHOD
PATH
DESCRIPTION
/api/v2/revenu-solidarite-active
RSA benefit status
/api/v2/prime-activite
Activity bonus status
/api/v2/allocation-adulte-handicape
Disabled adult allowance (AAH) status
/api/v2/complementaire-sante-solidaire
Solidarity health cover (C2S) status
/api/v2/composition-familiale
Family quotient from CAF records
/api/v2/etudiants
Student status
/api/v2/scolarites
Pupil enrollment and scholarship status
/api/v2/paiements-pole-emploi
France Travail payments
/api/v2/revenu-solidarite-active
RSA benefit status
/api/v2/prime-activite
Activity bonus status
/api/v2/allocation-adulte-handicape
Disabled adult allowance (AAH) status
/api/v2/complementaire-sante-solidaire
Solidarity health cover (C2S) status
/api/v2/composition-familiale
Family quotient from CAF records
/api/v2/etudiants
Student status
/api/v2/scolarites
Pupil enrollment and scholarship status
/api/v2/paiements-pole-emploi
France Travail payments
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
Setup
Wiring the API Particulier by hand means registering for an authorization, passing your API key on every call, and attaching a FranceConnect token for each citizen whose data you read. Through Jentic you install once, import API Particulier from the API Directory, store the API key once, and your agent calls it.
Permission scoping
The API Particulier is read-only, so a rule can bound your agent to the specific status checks it needs, such as the RSA and family-quotient operations, and exclude the rest. You choose the operation set, so the agent verifies only the statuses you grant.
Credential isolation
Your API Particulier key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'check RSA benefit status' or 'look up a family quotient', and Jentic returns the matching API Particulier operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using API Particulier API through Jentic.
What authentication does the API Particulier use?
The API Particulier authenticates with an API key in the `X-Api-Key` header, and the citizen-data operations also require a FranceConnect bearer token that identifies the person, per its OpenAPI spec. The ping endpoints need no credential. Through Jentic the API key is stored encrypted by your own Jentic One instance and injected at call time, while the FranceConnect token is supplied per request.
Can I verify a citizen's RSA status with the API Particulier?
Yes. The RSA operation returns the official benefit status for the person identified by the FranceConnect token, and companion operations cover the activity bonus, disabled adult allowance, and solidarity health cover. Each returns the authoritative status rather than a self-declared value.
What are the rate limits for the API Particulier?
The OpenAPI spec does not specify rate limits; access is governed by your authorization agreement. Current limits and usage terms are documented in the vendor documentation at https://particulier.api.gouv.fr.
How do I check benefit status with the API Particulier through Jentic?
Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import API Particulier from the API Directory, and store your API key once. Your agent then searches for an intent such as 'check RSA benefit status', and Jentic returns the matching operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there an API Particulier MCP server?
You do not need an MCP server to give your agent the API Particulier. Jentic connects it directly from the API Directory: import the API, store your key once, and your agent calls the status-check operations on demand, which keeps your agent's context free of an extra server's tool definitions.
Can I limit what my agent is allowed to do with the API Particulier?
Yes. Every operation here is a read status check, so you can allow your agent only the ones a workflow needs, such as the RSA or student-status checks, while leaving out the others. Because you run Jentic One yourself, the agent verifies just the statuses you grant, and every call is logged against your audit trail.
GET STARTED