V.E.R.I.F.Y.™ · PATENT PENDING · PAT-118 THROUGH PAT-121

VERIFY Global™

AI identity verification for globals. Zero document storage. Confidence scoring. ARCEB immutable audit logging. One API call.

GDPR consent is assumed for international users. Continuity hashing (PAT-119) stores only a SHA-256 hash of credentials — the original passport or credential number is never stored.

How VERIFY Global™ Works

Submit

POST document data (base64) to the verification endpoint. Data exists only in memory.

Analyze

Patent-pending AI analyzes global credentials using claude-sonnet-4-6. Nothing is stored.

Score

A confidence score (0.0–1.0) is computed. Threshold varies by population type.

Token

A VerificationToken with ARCEB trace ID is returned. Store only the token_id.

API Integration

POST api.verify.25alpha.ai/v1/verify/global
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": "global",
  "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"global"Always "global" 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

Zero Document Retention

All documents are processed in volatile memory and never written to any persistent storage. Enforced at the code level (PAT-118).

ARCEB Audit Logging

Every verification event is permanently logged with a SHA-256 hashed user ID. Logs are immutable by database trigger — UPDATE and DELETE are blocked.

No PII in Audit Log

The audit log contains only hashed identifiers, confidence scores, and compliance flags. No names, document numbers, or personal data.

7-Year Retention

ARCEB audit records are retained for 7 years as required by federal regulations. Records cannot be modified or deleted.

Frequently Asked Questions

How does VERIFY Global™ verification work?

VERIFY Global™ verification uses patent-pending AI analysis to confirm global 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 global 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 Global™ verification?

POST to https://api.verify.25alpha.ai/v1/verify/global 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 Global™?

Get your API key and start verifying globals in minutes.

View Pricing API Documentation