Integritas Is Now First-Class in RelAI SDK - Here’s How to Use It

Integritas is now built directly into RelAI SDK.

No separate integration project. No custom request plumbing. Just enable it and keep using the same client.fetch(...) flow you already have.

This post is intentionally simple and focused on outcomes: what users get, what to turn on, and how to ship fast.

What Integritas adds

Integritas adds a verification layer to paid API usage.

For product teams, that usually means:

• clearer trust story for buyers,
• better proof/receipt data after payment,
• easier audit and support conversations.

1) Enable Integritas in 30 seconds

npm install @relai-fi/x402

import { createX402Client } from '@relai-fi/x402';
const client = createX402Client({
  wallets,
  integritas: { enabled: true, flow: 'single' },
});

That is enough for most teams to get started.

2) Keep the same fetch API

You do not need a new request model.

const response = await client.fetch('https://api.relai.fi/relay/1765103787374/projects?page=1');
const data = await response.json();

3) Choose your flow (simple rule)

• single: best default for most apps, one cleaner buyer experience.
• dual: use when your backend policy needs a separated mode.

4) Per-request control (optional)

Need a specific request without Integritas? Override once:

await client.fetch(url, {
  x402: { integritas: false },
});

5) Works with WebSocket relay too

Integritas is not limited to HTTP relay. It works with Relay WS transport as well, so you can keep low-latency flows and still keep Integritas enabled.

6) Where to see the result

After payment, settlement metadata can be propagated through:

• PAYMENT-RESPONSE
• X-PAYMENT-RESPONSE

Quick launch checklist

1. Turn Integritas on globally.
2. Start with single flow.
3. Validate one HTTP relay call and one WS relay call.
4. Confirm payment metadata appears in your app/dashboard.