13trust / 100

Scan

by vault.xrpl-utilities.io in Other

x402 APIFailing, checked 6 h ago

XR-Vault per-issuer RWA deep dive

POST
https://vault.xrpl-utilities.io/scan
Price
$0.1
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
6 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 6 h ago: Amount "0.10" is not in atomic token units

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://vault.xrpl-utilities.io/scan

Each call costs $0.1 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://vault.xrpl-utilities.io/scan
content-type: application/json

{
  "issuer": "Ondo OUSG"
}

Example response

The provider's example. We can't check it without paying.

Example response, 27 lines
{
  "amm_exposure": {
    "pools": [],
    "pools_containing": 0
  },
  "caveat": "Native units; no fabricated USD valuation.",
  "current": {
    "net_circulating_raw": "95000000",
    "obligations_raw": "100000000",
    "trustline_count": 312
  },
  "flow_24h": {
    "burned_amount": "1200000",
    "burns_count": 1,
    "minted_amount": "5000000",
    "mints_count": 3,
    "net_amount": "3800000"
  },
  "issuer": {
    "asset_class": "treasuries",
    "currency": "OUSG",
    "logical_label": "Ondo OUSG",
    "wallets_aggregated": 2
  },
  "schema_version": "1.16.0",
  "service": "XR-Vault"
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.1.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://vault.xrpl-utilities.io/scan' \
  -H 'content-type: application/json' \
  --data-raw '{"issuer":"Ondo OUSG"}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://vault.xrpl-utilities.io/scan' \
  -H 'content-type: application/json' \
  --data-raw '{"issuer":"Ondo OUSG"}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.1 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.1" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.1 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fvault.xrpl-utilities.io%2Fscan&method=POST
const res = await pay("https://vault.xrpl-utilities.io/scan", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "issuer": "Ondo OUSG"
  }),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.1 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.1"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://vault.xrpl-utilities.io/scan",
        json={
            "issuer": "Ondo OUSG",
        },
    )
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
6 h agoAmount "0.10" is not in atomic token units402920 ms$0.1
14 h agoAmount "0.10" is not in atomic token units402897 ms$0.1
22 h agoAmount "0.10" is not in atomic token units402865 ms$0.1
31 h agoAmount "0.10" is not in atomic token units402885 ms$0.1
38 h agoAmount "0.10" is not in atomic token units402882 ms$0.1
Show 1 older checks
45 h agoAmount "0.10" is not in atomic token units4021.3 s$0.1