AzurSafe x402

Overview

AzurSafe x402 screens wallets and other counterparties before autonomous onchain actions. It returns machine-readable risk results that software can use immediately.

Why teams use it

• Block unsafe actions before execution
• Return structured outputs an agent can enforce
• Keep a clear policy trail for each decision

How it works

1. Agent prepares an onchain action
2. Agent screens the identifier
3. Agent sends a paid x402 request to https://ai.azursafe.com/agent/screen-id
4. AzurSafe x402 returns a risk result
5. Policy decides allow, review, or block
6. Agent continues only if permitted

API

Paid screening endpoint:
GET https://ai.azursafe.com/agent/screen-id?identifier=<value>

Health endpoint:
GET https://ai.azursafe.com/health

Description

Screen a wallet or counterparty before an autonomous onchain action.

The x402 payment request is made to the full production URL above, using https://ai.azursafe.com as the domain.

Examples

Example requests

GET https://ai.azursafe.com/agent/screen-id?identifier=0xAb5801a7D398351b8bE11C439e05C5B3259aeC9B
GET https://ai.azursafe.com/agent/screen-id?identifier=TE3mCcPULjPUE7ykX7RArDPAhyahoy3d2j
GET https://ai.azursafe.com/agent/screen-id?identifier=1PMycacnJaSqwwJqjawXBErnLsZ7RkXUAs
GET https://ai.azursafe.com/agent/screen-id?identifier=example.org
GET https://ai.azursafe.com/agent/[email protected]
GET https://ai.azursafe.com/agent/screen-id?identifier=+14155550123
GET https://ai.azursafe.com/agent/screen-id?identifier=treasury_bot
GET https://ai.azursafe.com/agent/screen-id?identifier=8fjkQpV7L6Wm2nZrYt3aBcD4EfGhJkLmNoPqRsTuVwX

Health check example

GET https://ai.azursafe.com/health

HTTP status: 200
{
  "ok": true
}

Legit example

Identifier: 0xAb5801a7D398351b8bE11C439e05C5B3259aeC9B
Request URL: https://ai.azursafe.com/agent/screen-id?identifier=0xAb5801a7D398351b8bE11C439e05C5B3259aeC9B
HTTP status: 200
{
  "ok": true,
  "endpoint": "screen-id",
  "identifier": "0xAb5801a7D398351b8bE11C439e05C5B3259aeC9B",
  "data": {
    "name": "Vb_4e62be",
    "legitimacyStatus": "legit",
    "category": "Foundation/Developer",
    "source": "Public and Online Data",
    "findings": 4
  }
}

Fraud example

Identifier: TE3mCcPULjPUE7ykX7RArDPAhyahoy3d2j
Request URL: https://ai.azursafe.com/agent/screen-id?identifier=TE3mCcPULjPUE7ykX7RArDPAhyahoy3d2j
HTTP status: 200
{
  "ok": true,
  "endpoint": "screen-id",
  "identifier": "TE3mCcPULjPUE7ykX7RArDPAhyahoy3d2j",
  "data": {
    "name": "OFAC_Sanctioned_2b477d",
    "legitimacyStatus": "fraud",
    "category": "Phishing/Fraud",
    "source": "Online and Public Data",
    "findings": 2
  }
}

Unknown example

Identifier: 1PMycacnJaSqwwJqjawXBErnLsZ7RkXUAs
Request URL: https://ai.azursafe.com/agent/screen-id?identifier=1PMycacnJaSqwwJqjawXBErnLsZ7RkXUAs
HTTP status: 200
{
  "ok": true,
  "endpoint": "screen-id",
  "identifier": "1PMycacnJaSqwwJqjawXBErnLsZ7RkXUAs",
  "data": {
    "name": null,
    "legitimacyStatus": "unknown",
    "category": null,
    "source": null,
    "findings": 0
  }
}

Networks and coverage

AzurSafe x402 supports wallet screening across 30+ major blockchains and identifier types.

Screening coverage is broader than payment settlement rails. The API is designed to screen counterparties across major ecosystems including EVM, Solana, UTXO, XRP, Tron, and more.

Company and access

AzurSafe builds blockchain compliance and investigation solutions recognized by public and private financial institutions that help teams improve security, streamline transactions, and increase trust across digital asset operations.

We are a growing multidisciplinary team based in France, we are leading the industry across compliance, data, engineering, and investigations, supported by specialized expertise in AML/CFT, sanctions, regulatory strategy, and blockchain investigations.