x402 List Submit a serviceSubmit
Menu

MyRxWallet Paid Data API

payment-readyonline

payment-ready until 2026-11-04

Pay-per-call healthcare and on-chain data for AI agents.

Compare: all sanctions screening APIs

myrxwallet.io ↗

Call it x402 v1

x402 v1

Base URL
https://oli.myrxwallet.io/api/v1/x402
Payment
x402 v1, body (v1 style)
$ curl -i 'https://oli.myrxwallet.io/api/v1/x402/crypto/rates/ETH-USD'

An unpaid request returns HTTP 402 with the payment terms. Sign a payment authorization, then retry with the X-PAYMENT header.

Endpoints 4 paid routes on oli.myrxwallet.io

POST/compliance/aml-checkBase$0.25since 10-28
GET/crypto/rates/ETH-USDBase$0.02since 10-28
GET/drug/price/00093-7146-01Base$0.10since 10-28
GET/provider/verify/1003000126Base$0.05since 10-28

Prices as captured in the 402 response: median $0.075 across the 4 endpoints, unchanged since first capture.

Example 402 response

Endpoints and prices

Current paid endpoints; minimum quoted prices in USD where available; first capture dates in UTC
MethodPathDescriptionPriceNetworkAsset402 channelCaptured
POST/compliance/aml-checkAML/sanctions screening$0.25BaseUSDCbodysince 10-28
GET/crypto/rates/ETH-USDLive crypto exchange rate$0.02BaseUSDCbodysince 10-28
GET/drug/price/00093-7146-01Drug pricing by NDC code$0.10BaseUSDCbodysince 10-28
GET/provider/verify/1003000126NPI provider verification$0.05BaseUSDCbodysince 10-28

Payment evidence

402 payload captured at . Check evidence JSON · Measurement methodology.

First of 4 payloads captured by the monitor.

17 lines, scroll inside

{
  "error": "Payment required: $0.05 USDC on Base L2",
  "accepts": [
    {
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "payTo": "0x121F4aD1E1CFbb685606B7a89FdDfdf2fceeF9D2",
      "scheme": "exact",
      "network": "base",
      "mimeType": "application/json",
      "resource": "/api/v1/x402/provider/verify/1003000126",
      "description": "NPI provider verification",
      "maxAmountRequired": "50000"
    }
  ],
  "howToPay": "Send USDC on Base network to payTo address, then re-request with X-Payment: <txHash> header",
  "x402Version": 1
}
Other captured 402 responses (3)

Captured payload 2 of 4

{
  "error": "Payment required: $0.02 USDC on Base L2",
  "accepts": [
    {
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "payTo": "0x121F4aD1E1CFbb685606B7a89FdDfdf2fceeF9D2",
      "scheme": "exact",
      "network": "base",
      "mimeType": "application/json",
      "resource": "/api/v1/x402/crypto/rates/ETH-USD",
      "description": "Live crypto exchange rate",
      "maxAmountRequired": "20000"
    }
  ],
  "howToPay": "Send USDC on Base network to payTo address, then re-request with X-Payment: <txHash> header",
  "x402Version": 1
}

Captured payload 3 of 4

{
  "error": "Payment required: $0.25 USDC on Base L2",
  "accepts": [
    {
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "payTo": "0x121F4aD1E1CFbb685606B7a89FdDfdf2fceeF9D2",
      "scheme": "exact",
      "network": "base",
      "mimeType": "application/json",
      "resource": "/api/v1/x402/compliance/aml-check",
      "description": "AML/sanctions screening",
      "maxAmountRequired": "250000"
    }
  ],
  "howToPay": "Send USDC on Base network to payTo address, then re-request with X-Payment: <txHash> header",
  "x402Version": 1
}

Captured payload 4 of 4

{
  "error": "Payment required: $0.10 USDC on Base L2",
  "accepts": [
    {
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "payTo": "0x121F4aD1E1CFbb685606B7a89FdDfdf2fceeF9D2",
      "scheme": "exact",
      "network": "base",
      "mimeType": "application/json",
      "resource": "/api/v1/x402/drug/price/00093-7146-01",
      "description": "Drug pricing by NDC code",
      "maxAmountRequired": "100000"
    }
  ],
  "howToPay": "Send USDC on Base network to payTo address, then re-request with X-Payment: <txHash> header",
  "x402Version": 1
}

Can I trust it score from our own monitoring

score from our own monitoring

83/100 Solid

#231 of 440 in Data. Bands: strong 93+, solid 75+, mixed 55+, weak below 55.

Reliability
100% uptime since 10-28
Compliance
C 12/14 checks pass, failing: declares the current x402 version (2), EIP-712 domain parameters present on every EVM entry
Signability
route not signable
Price
$0.02 to $0.25 p78 in Data
Risk
clean no risk flag
Traction
---
12/14 compliance checks
  • 402 payload captured
  • accepts[] array present
  • payTo address recoverable
  • payTo at accepts[0].payTo (conformant shape)
  • payTo is a valid on-chain address
  • atomic price declared
  • atomic price in a sane range
  • asset (token) address declared
  • network resolves to CAIP-2
  • payment scheme declared
  • served over HTTPS
  • declares the current x402 version (2)
  • EIP-712 domain parameters present on every EVM entry
  • x402 v2 envelope delivered in the payment-required header

402 terms unchanged since 2026-10-28. Last up 2026-10-28.

── Site signals

  • homepage reachable
  • openapi doc
  • pricing page
  • llms.txt
  • robots.txt
  • terms page
How the score works

What the score read on this service: status online, 100% uptime, latest daily rollup (no 30d window yet), 203ms response p95, x402 compliance 12 of 14, $0.02 price against the category. Each of those is measured, and each is published in full below.

The score comes from our own monitoring, never from reviews, operator claims, or a language model: reliability, x402 compliance, price against the category, a deterministic risk flag, and a small on-chain traction term, weighted by ranking generation 3. It is not placement anyone can buy: the paid verify tier is reported beside it and is not one of its inputs. Every component below stays published and read-only.

Bands on the 0 to 100 measured score: strong at 93 and above, solid from 75, mixed from 55, weak below 55. Price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, so the score places a service in its own field.

It is a score inside Data, and only there: price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, which here means 440 listings, this one among them: the same 440 the position above is counted against. When the two differ, the field is the wider one, because a listing we have measured too little of to rank still sits in the field the price and the speed are normalized over. The same service in a different field would read differently. The same engine answers GET /api/v1/best, and asked for a different pool (the whole directory, or another filter) it returns a different number for this service under this same ranking generation. Neither is more correct: they answer different questions, and the methodology states which is which.

All measured facts

What it does

Pay-per-call healthcare and on-chain data for AI agents. Drug pricing by NDC, drug interaction checks, NPI provider verification, crypto spot rates and AML/compliance screening. No API keys and no signup: every endpoint answers HTTP 402 with USDC on Base under x402 v1, then returns JSON once the transaction hash is sent back in the X-Payment header. A machine-readable catalogue is served at /catalog and an agent card at https://oli.myrxwallet.io/.well-known/agent-card.json.

MyRxWallet Paid Data API is a listed x402 Data API. Captured payment terms name Base. Monitoring and settlement figures below describe the observations available to this directory; an unpaid HTTP 402 check does not prove that a paid call will deliver.

Assessment computed at . Latest service check observed at . Service data JSON · Measurement methodology.

Page rendered at . This response time is separate from the observation and computation times attached to each measurement.

Latest endpoint observation: . Latest price capture: . Prices are recorded quotes, not a promise of availability. Token assets and payment terms are listed separately. Endpoint data JSON · Price history JSON · Measurement methodology.

Assessment computed at . Uptime uses the stated daily-rollup window; response times are in milliseconds, compliance is passed/evaluated checks, and traction is a measured settlement floor. The comparison score is out of 100 within this category. Assessment JSON · Measurement methodology.

Observed daily coverage: 2026-09-29 to 2026-10-28 UTC. Daily monitoring and settlement rollups do not expose their computation time; a bucket date is not an update timestamp. Uptime and response JSON · Volume JSON · Buyers JSON · Measurement methodology.

Ranked from the measured category pool, refreshed at most once a minute. The comparison has no persisted computation timestamp; the assessment time above belongs to this service only. Ranking API documentation · Ranking methodology.

x402 List home · Services · Data

uptime · latest daily rollup
-
uptime 7d
-
uptime 30d
-
uptime 90d
-
response p95
203ms
avg response
203ms
total checks
1

Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.

At least one EVM route on this service returns its 402 without the EIP-712 domain parameters (extra.name and extra.version), so a standard x402 client cannot build the signature for that route.

Measured on the last 402 envelope captured from this service. It is a fact about the envelope, not a judgement on the service or its operator.

This is the only conformance check that caps the compliance grade, at C.

price (min)
$0.02
price (max)
$0.25
category percentile (min)
p78 in Data
category percentile (max)
p81 in Data
endpoints / prices
4 / 4
model
tiered
stability
100%

No deterministic risk flag. Risk fires only on an exact blocklist match, or a reserved-brand name with a mismatched verified payTo. Never from low uptime, a high price, or a model guess.

domain age
-
registrar
-
hosting
custom
domain created
---

Identity facts, not a risk score.

On-chain traction has not been assessed for this service yet.

member since
2026-10-28
Recent checks
Latest 8 unpaid HTTP checks, newest first; response times in milliseconds, observation times in UTC
Checked at (UTC)StatusHTTPResponseEndpoints
Online402509ms4
Online402446ms4
Online402195ms4
Online4025428ms2
Online402812ms4
Online402179ms4
Online402441ms4
Online402203ms4

Changes0 in 30d

No changes recorded in the last 30 days.

all changes

Over time

On-chain volume

On-chain traction has not been assessed for this service yet.

Uptime no completed-day data
Uptime
no completed-day data

On-chain traction has not been assessed for this service yet.

More charts
Response time daily average, ms min 1027ms, avg 1027ms, max 1027ms

09-29 to 10-28* UTC

Each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/myrxwallet-paid-data-api/price, /scores, /volume and /buyers.

Values

* today so far, partial (UTC).

The uptime summary counts completed UTC days only. The strip, readouts and table retain today's partial reading.

Assessment history last recorded at . Each UTC day uses its last recorded run; missing readings stay unmeasured. Assessment history JSON · Measurement methodology.

Daily values, 2026-10-28 to 2026-10-28: uptime percent, average response milliseconds, compliance passed/total, price percentile 0-100, site signals out of 6; UTC dates
DayUptimeResponseCompliancePrice percentileSite signals
2026-10-28*100%1026.63ms12/14p782/6

Alternatives in Data

Money Reactor strong 99/100 --- up 30d --- 30d
SniperX•x402 strong 97/100 99.9% up 30d $689.69 30d
claw402 strong 97/100 100% up 30d $1.2k 30d
Quant Agent Shop strong 96/100 --- up 30d --- 30d
glim.sh strong 95/100 100% up 30d $34.59 30d

5 of 439 other ranked services in Data, ordered by the same measured score.

see the whole category

Own this service?

Keep this listing accurate. Ownership is proven with a domain check and every change is reviewed by hand.

Update this listing

Earn the verified tier: x402list pays a real call to this endpoint and, if it delivers, the service is delivery-verified. The fee covers the cost of the probe, not the badge; there is no refund if the call does not deliver. Agent and API only, no in-browser signing. See /api.

Verify this service ($0.25)
Embed a badge

HTML

<a href="https://x402-list.com/services/myrxwallet-paid-data-api?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/myrxwallet-paid-data-api.svg" alt="MyRxWallet Paid Data API listed on x402-list" height="28">
</a>

Markdown

[![MyRxWallet Paid Data API on x402-list](https://x402-list.com/badge/myrxwallet-paid-data-api.svg)](https://x402-list.com/services/myrxwallet-paid-data-api?utm_source=badge&utm_medium=referral&utm_campaign=embed)

HTML, live uptime variant

<a href="https://x402-list.com/services/myrxwallet-paid-data-api?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/myrxwallet-paid-data-api.svg?data=uptime" alt="MyRxWallet Paid Data API uptime on x402-list" height="28">
</a>
Delisting

To request delisting, email info@x402-list.com with the service name, slug, or URL. Removal is free and does not require proof of ownership. See all free email requests.