CAPPS Developer Integration Portal

Build with CAPPS using trust scans, SafeAI labels, verification badges, instant decisions and signed receipts.

This portal gives developers a public-safe route map for integrating CAPPS without exposing child records, private identity evidence, wallet signing secrets or unsupported trust claims.

View Integration Manifest Open API Playground Transport Rails

Developer Lanes Trust Scanner SafeAI Registry Verify Badge Instant Check Receipts SDK Handoff

Integration Routes

Start with public-safe decisions and proof receipts.

Trust Scanner

Score websites, communities, AI tools and platforms with transparent factors and evidence state.

SafeAI Registry

Prepare AI tools for child-safety labels, model risk notes, audit status and public review boundaries.

Verification Badge

Show reviewed status only when manifest, policy and evidence route support the badge state.

Instant Verification

Request CAPS ID, age-band, consent, trust and platform status without collecting raw private records.

Transport Receipts

Use signed receipt references, idempotency keys, policy version and evidence hash for each decision.

SDK Handoff

Use JavaScript, Python, Go and Rust SDK lanes after public manifest and rate-limit boundaries are reviewed.

Decision Payload

Public-safe response shape for developers.

{
  "capsId": "CAPS-EXAMPLE-001",
  "route": "/caps/evaluate",
  "decision": "allow-with-restrictions",
  "trustBand": "reviewing",
  "consentState": "guardian-reviewed",
  "policyVersion": "capps-safety-2026-06",
  "receiptRef": "receipt-hash-reference",
  "evidenceHash": "sha256-public-proof"
}

Hardening Rules

Every integration must preserve the CAPPS public-data boundary.

No Private RecordsDo not send child records, private contacts, raw identity records or private conversations.

No Wallet SecretsDo not send wallet signing secrets or recovery material through CAPPS public routes.

No Unsupported LabelsVerified, safe, partner or school labels require reviewed public evidence.

Receipt FirstUse signed receipts, policy versions and evidence hashes for every decision record.

Developer Next Steps

Build one integration at a time.

1. Scan

Run a public trust scan and record the risk factors that matter for your product.

2. Verify

Map the entity to a CAPS ID, badge state, evidence route and review boundary.

3. Decide

Use instant verification to return an allow, restrict, review or block decision.

4. Prove

Publish only the route, policy version, receipt reference and evidence hash.