Apply to integrate Abraxas verification
A relying party is any lender, marketplace, registry, or protocol that accepts an Abraxas credential or Passport state to clear a downstream action. without re-running KYC on the user.
Integration guide (start here)
One API call returns a decision plus cryptographic proof that any relying party can verify independently. Copy-paste examples, curl commands, and JSON schemas cover what you need before you apply.
Onboarding path
Identity-only (POST /api/credentials/verify), wallet trust (GET /api/trust/status), or asset registry (GET /api/verify/registry).
Use /verify/ABX-RE-HOSP-001 or POST with your abx_live_ key. Confirm decision: approved before wiring production gates.
Call our API server-side. Never trust client-side JWT parsing alone. verify signature via our endpoint or published Ed25519 public key.
Run a 30-day pilot with a defined metric: time-to-verify, conversion lift, or cost per manual review eliminated.
Production checklist
- 1. Read /docs/relying-party-verify. one verify call → proof → independent check
- 2. Issue abx_live_ key with verify:credential scope
- 3. Implement server-side POST /api/credentials/verify at your transaction gate
- 4. Confirm GET /api/proof/{proof_id} returns signature_valid: true
- 5. First approved production verify logs toward the external RP mainnet gate
Submit integration intent. We review within 48h and issue an abx_test_ sandbox key on approval.
Verify against ABX-RE-HOSP-001 or Passport Tier 3 demo before production wiring.
Public verifierPaste your issued API key to view usage, onboarding progress, and integration status.
Open portal