Never build verification again.

The entire pitch

const eligibility = await abraxas.can(user, {
  age: 21,
  identity: true,
  jurisdiction: ["US"],
});

if (eligibility.allowed) {
  unlockExperience();
}

SDK evolution may also expose abraxas.trust(), abraxas.assert(), or abraxas.check() depending on whether the API describes permission or trust state.

const trust = await abraxas.trust(user);

if (trust.age21) { ... }
if (trust.identity) { ... }
if (trust.resident("US")) { ... }

Abraxas is in production with real assets. Cielo Sunrise and Chickasaw land diligence are live reference integrations for design partners embedding verification today. Today: POST /api/credentials/verify

• Better conversion. Every extra upload loses users. Do not ask again if verification already exists.
• Lower compliance burden. Consume trusted credentials instead of becoming an identity company.
• Lower engineering cost. One SDK instead of months building verification infrastructure.
• Better privacy. Merchants need answers (over 21? verified? resident?), not passport images.
• Network effects. More merchants means more valuable credentials and more users arrive pre verified.

First wedge

• Age restricted commerce
• Identity verification
• Reusable eligibility

Verify before agents act.

Built for humans and agents. Abraxas issues cryptographic proofs that both people and AI agents can independently verify before acting on real-world assets.

As AI agents begin executing real financial and asset actions, they need more than data. they need independently verifiable proof. Abraxas provides portable, cryptographic verification that agents can check before they act.

Abraxas is independent verification infrastructure. not a Robinhood integration. We build alongside the same agentic stack so builders can compose verify → act without rebuilding trust per app.

• Agent receives a task that touches a verified person or RWA (allocation, custody handoff, gated product access).
• POST /api/credentials/verify with record_id or credential. read response.agent.proceed.
• GET response.verify_url. require proof.agent.valid === true (fail closed).
• Only then invoke act-layer tools (e.g. Robinhood MCP order placement) per your policy.

agentic_finance_stack in GET /api/docs/agents · abraxas.agentic_finance.v1

Live proof

The category

Every RWA app and asset tokenization platform rebuilds trust from scratch. Abraxas is the verification infrastructure that makes proof portable.

Not another issuer. Not another marketplace. Abraxas is the trust check every token app plugs into.

Where Abraxas sits

What you integrate

Already issuing tokenized assets? Embed Abraxas Passport so verified assets move across applications without repeating due diligence.

• Universal Asset Passport
• Verification API
• Reusable compliance
• Due diligence layer
• Cross-platform trust

Design partner program

Design partners get sandbox credentials, documented verify paths, and hands-on support while wiring production flows. External production keys ship when your integration passes the same verification gates we hold ourselves to.

• 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