API DemoFELCASimulated dataMarch 14, 2026Live demo

FELCA API Demo — See `is_adult: true/false` live

Q: Does this demo make real API calls?

No. All data is 100% simulated locally in your browser — no request is sent to the server and no credits are consumed. The behavior and JSON response are identical to the real production API.

Q: What is is_adult: true / false?

It's the main field in the FELCA API response. true means the CPF holder is 18 or older — access granted. false means under 18 — your platform must block access to restricted content as required by Brazil's FELCA Law (Lei 15.211/2025).

Q: Does the API store the CPF sent?

No. FlagCheck processes the CPF in real time and immediately discards it. For your ANPD audit log, store only the SHA-256 of the CPF + the meta.request_id + meta.timestamp fields — this proves compliance without exposing personal data.

Q: How long does a real integration take?

The /api/felca/age-check endpoint is a simple POST with a CPF in the body and a JSON response. A developer can integrate in under 1 hour. We have examples in JavaScript, Python, PHP, and cURL.

Q: When should I use /api/felca/liveness beyond age-check?

Liveness (CPF + selfie) is recommended for high-risk platforms: sports betting, adult content, alcohol delivery, and fintech. It confirms that the person using the platform is actually the CPF holder — preventing a minor from using an adult's document. Returns face_match.matched (true/false) and face_match.confidence (0–100). If the CPF belongs to a minor, biometrics are skipped and credits_liveness is 0.

Q: What does face_match.confidence mean?

It is the similarity score between the submitted selfie and the official photo linked to the CPF in the Receita Federal database, from 0 to 100. Values ≥ 70 indicate a reliable match. A score of 96 means near-perfect correspondence. A score of 31 means the selfie likely belongs to a different person.

Two interactive demos: Age Check (CPF → is_adult) and Liveness (CPF + selfie → is_adult + face_match). See the full JSON and integration code. No real API calls are made, no credits spent.

POST /api/felca/age-checkDEMO — simulated data

CPF

How it works in a real integration

1📝

Form collects CPF

Your registration or checkout form collects the user's Brazilian CPF (tax ID).

2🔒

Backend calls the API

Your server makes a server-side POST with the CPF. The API key stays secure.

3⚡

Response in < 2s

The API returns is_adult: true or false. You grant or block access accordingly.

Lei FELCA (Lei 15.211/2025): Brazil's FELCA Law (Lei 15.211/2025) in effect from 17/03/2026: self-declaration of age is prohibited. Every digital platform accessible to minors needs reliable verification. Read the full guide →

What each response field means

Campo / Field	Tipo / Type	Descrição / Description
data.is_adult	boolean	true = 18+, grant access. false = minor, block. This is the main field for FELCA compliance logic.
data.age	integer	Calculated age of the CPF holder. Omitted if minor (LGPD data protection).
data.date_of_birth	string	Date of birth (YYYY-MM-DD). Omitted if minor.
data.document.valid	boolean	Whether the CPF exists and is active in the Brazilian Tax Authority database.
data.face_match.matched	boolean	(Liveness) true = face matches the CPF holder. false = different person.
data.face_match.confidence	float 0–100	(Liveness) Facial similarity score. ≥ 70 = reliable match.
meta.credits_liveness	integer	(Liveness) Credits consumed by biometrics. 0 if minor (biometrics skipped).
meta.request_id	string	Unique request ID — store this for your ANPD compliance audit log.
meta.timestamp	string ISO 8601	Exact verification timestamp — required for audit trail.

🤳

When to use Liveness (CPF + Selfie)?

The /api/felca/liveness endpoint is recommended for high-risk platforms: sports betting, adult content, alcohol delivery, and fintech. It confirms not just the age, but that the person using the platform is actually the CPF holder — preventing a minor from using an adult's document.

✅ face_match.matched: true — face matches the CPF registered at Receita Federal
⚠️ face_match.matched: false — adult, but face does not match the holder
🔴 is_adult: false — minor detected, biometrics skipped (no liveness cost)

Test it now in the "2 — Liveness Check" tab above.

FELCA Law in effect — March 17, 2026

Ready to integrate for real?

Get your API key and integrate in under 1 hour. FELCA compliant, LGPD-safe, no CPF stored.

Talk to an expert →View integration guide →

Frequently Asked Questions

Does this demo make real API calls?▼

No. All data is 100% simulated locally in your browser — no request is sent to the server and no credits are consumed. The behavior and JSON response are identical to the real production API.

What is is_adult: true / false?▼

It's the main field in the FELCA API response. true means the CPF holder is 18 or older — access granted. false means under 18 — your platform must block access to restricted content as required by Brazil's FELCA Law (Lei 15.211/2025).

Does the API store the CPF sent?▼

No. FlagCheck processes the CPF in real time and immediately discards it. For your ANPD audit log, store only the SHA-256 of the CPF + the meta.request_id + meta.timestamp fields — this proves compliance without exposing personal data.

How long does a real integration take?▼