Integrations

The reusable verification primitive

3 live integration surfaces today. External protocols integrate Abraxas Passport in ~4 lines — no re-KYC for users.

Relying party program

The network-effect milestone: an unaffiliated lender, marketplace, or protocol checks Abraxas credentials in production. Partners configure eligibility rules — Abraxas returns approved / denied / manual review with consent receipts and audit references.

Relying party onboarding →Outreach templates

Policy Engine

Partners define required claims (identity, screening, wallet binding, accreditation) with assurance levels and max age. The engine evaluates live claim status — not a static profile — and logs every decision.

  • Seeded policies: abraxas-core-v1, abraxas-booking-v1, abraxas-rwa-us-v1
  • POST /api/v1/policies/evaluate — direct evaluation
  • GET /api/v1/decisions/{id}/status — re-check before settlement

Trust Registry

A credential is only valuable if the verifier trusts the issuer. Abraxas maintains which issuers may sign which claim types, with assurance tiers, jurisdictions, and audit status.

  • GET /api/trust/registry — issuers + W3C schema identifiers
  • Veriff · Abraxas Network · Manual Review · Screening (partner-gated)
  • Issuer suspension and schema versioning
View registry JSON →

Quick integration

// 1) Check if user meets your policy before an action
const check = await fetch("https://abraxas-app.vercel.app/api/verification/check-level", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ sui_address: walletAddress, action: "book_asset" }),
});
const level = await check.json();
if (level.needsDeepVerification) {
  // Prompt ID check — user completes Veriff once
}

// 2) Partner flow: create request → user consents → get decision
const req = await fetch("https://abraxas-app.vercel.app/api/v1/verification-requests", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "X-API-Key": process.env.ABRAXAS_PARTNER_API_KEY,
  },
  body: JSON.stringify({
    policy_id: "abraxas-rwa-us-v1",
    requested_action: "subscribe_to_offering",
  }),
});
const { request_id, consent_url } = await req.json();

// 3) Re-check decision before settlement
const status = await fetch(
  `https://abraxas-app.vercel.app/api/v1/decisions/${decisionId}/status`,
  { headers: { "X-API-Key": process.env.ABRAXAS_PARTNER_API_KEY } }
);

Integration registry

Abraxas AppLiveFirst-party

Cielo booking, passport, and asset terminal — internal dogfood of the full loop.

GET /api/trust/status
AIL Public APILiveDeveloper

Trust status, credential verify, passport read, intent proofs.

GET /api/trust/status · POST /api/credentials/verify
Cielo Stablecoin CheckoutLiveHospitality RWA

Live USDC payment rail for verified short-term rental on Sui mainnet.

GET /api/cielo/config
External RWA MarketplaceRecruitingDesign partner slot

Accept Abraxas Passport for investor eligibility without re-KYC.

POST /api/credentials/verify
DeFi / Private Credit ProtocolRecruitingDesign partner slot

Collateral verification + identity tier for borrow against verified RWAs.

GET /api/sui/passport
Music Royalty PlatformPilotPipeline

Catalog ownership attestation via Abraxas music audit intake.

/music-audit

Become a design partner

Looking for one flagship operator to co-design reusable verification — starting with hospitality. Outcome-first collaboration, not a protocol pitch.

Design partner page →

Technical integrations, SDK snippets, and protocol listings continue below for developer-led partners.

  • Clear workflow where reusable identity or asset proof reduces friction
  • Willingness to pilot with real users (even small volume)
  • Defined success metric (conversion, time-to-verify, cost per check)
  • Permission to name publicly after pilot success
Pitch deck →Cielo E2E checkData room →