canonical: https://jentic.com/apis/particulier.api.gouv.fr/particulier

# Particulier Api API Particulier

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.

## For AI 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.

## Scope

Does not handle benefit payments, document storage, or identity enrollment. Use for verifying French citizens' administrative and benefit status only.

## Capabilities

- 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

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Call GET `/api/v2/etudiants` to confirm an applicant's student status

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v2/revenu-solidarite-active` | RSA benefit status |
| GET | `/api/v2/prime-activite` | Activity bonus status |
| GET | `/api/v2/allocation-adulte-handicape` | Disabled adult allowance (AAH) status |
| GET | `/api/v2/complementaire-sante-solidaire` | Solidarity health cover (C2S) status |
| GET | `/api/v2/composition-familiale` | Family quotient from CAF records |
| GET | `/api/v2/etudiants` | Student status |
| GET | `/api/v2/scolarites` | Pupil enrollment and scholarship status |
| GET | `/api/v2/paiements-pole-emploi` | France Travail payments |

## Key resources

- **Benefit status** — Status checks for RSA, activity bonus, AAH, ASF, and solidarity health cover
- **Household** — Family quotient from CAF and MSA records
- **Employment** — France Travail payments and job-seeker status
- **Education** — Student and pupil enrollment and scholarship status
- **Service** — Server status pings and token introspection

## AI readiness

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.

- **Score:** 53 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 70 / 100
  - Developer Experience & Jentic Compatibility: 77 / 100
  - AI-Readiness & Agent Experience: 29 / 100
  - Agent Usability: 94 / 100
  - Security: 55 / 100
  - AI Discoverability: 71 / 100
- **View full report:** https://jentic.com/apis/particulier.api.gouv.fr/particulier/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Truora** — Identity verification and background checks
- **USA.gov** — US government information and services directory

## FAQ

### 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.