VERIFY Edu™
AI identity verification for edus. Zero document storage. Confidence scoring. ARCEB immutable audit logging. One API call.
FERPA compliance is enforced on every educational verification. COPPA consent is required when the verified user may be under 13 years of age.
How VERIFY Edu™ Works
API Integration
POST api.verify.25alpha.ai/v1/verify/edu
X-Verify-API-Key: your_api_key
Content-Type: application/json
{
"user_id": "your_internal_user_id",
"document_data": "base64_encoded_document",
"gdpr_consent": true
}
// Response: VerificationToken
{
"token_id": "uuid-v4",
"verified": true,
"population": "edu",
"confidence": 0.92,
"timestamp": "2026-06-10T00:00:00.000Z",
"expires_at": "2026-06-10T01:00:00.000Z",
"hash_present": false,
"behavioral_trust": null,
"arceb_trace_id": "uuid-v4",
"compliance_flags": {
"ferpa_compliant": false,
"coppa_consent": false,
"gdpr_consent": true,
"fcra_access_log": false,
"glba_mfa": false,
"arceb_trace": true
}
}VerificationToken Schema
token_idstring (UUID v4)Globally unique token identifier. Store this — never the document.verifiedbooleanTrue if confidence meets the population threshold. False otherwise.population"edu"Always "edu" for this endpoint.confidencenumber (0.0–1.0)Composite confidence score from AI analysis.timestampstring (ISO 8601)UTC timestamp of verification event.expires_atstring (ISO 8601)Token TTL — 1 hour from issuance.arceb_trace_idstring (UUID)Immutable audit reference. Every event is permanently logged.hash_presentbooleanTrue if a continuity hash was stored (PAT-119). False for most pipelines.behavioral_trustnumber | nullBehavioral trust score (PAT-120). Present for citizen pipeline only.compliance_flagsComplianceFlagsFERPA, COPPA, GDPR, FCRA, GLBA, and ARCEB flags specific to this verification.Compliance & Privacy
Frequently Asked Questions
How does VERIFY Edu™ verification work?
VERIFY Edu™ verification uses patent-pending AI analysis to confirm edu identity. Documents are analyzed in volatile memory only — nothing is stored. A VerificationToken is returned with a confidence score and compliance flags.
Does V.E.R.I.F.Y.™ store edu documents?
No. V.E.R.I.F.Y.™ processes all documents in volatile memory only. No document content is written to any database, log, or storage layer. This is enforced at the code level per PAT-118.
What compliance standards does this verification meet?
V.E.R.I.F.Y.™ enforces FERPA, COPPA, GDPR, FCRA, and GLBA compliance flags on every verification token. All events are logged immutably via ARCEB audit records with 7-year retention.
What is the API endpoint for VERIFY Edu™ verification?
POST to https://api.verify.25alpha.ai/v1/verify/edu with your X-Verify-API-Key header and a JSON body containing user_id and document_data (base64 encoded). The response is a VerificationToken with verified boolean, confidence score, and compliance flags.
How is ARCEB audit logging enforced?
Every verification event writes an immutable record to the verify_arceb_log table. A database trigger prevents UPDATE and DELETE operations on this table — audit records cannot be modified or removed. Records are retained for 7 years.
Ready to integrate VERIFY Edu™?
Get your API key and start verifying edus in minutes.