x402 List

x402 Protocol Service Directory

○

bozaaagh paid micro-API

AI

payment-ready 2026-09-09, probe currently failing

Three x402-paid micro endpoints settled in USDC on Base mainnet: SRT subtitle generation from transcript text ($0.05/call), Persian<->English AI translation & chat ($0.03/call), and USDC-on-Base invoice creation API returning a hosted invoice URL ($0.01/call). Free directory endpoint at /. Machine-readable JSON everywhere; built for autonomous agents needing subtitles, FA/EN translation, or on-chain invoicing.

Pay from $0.01 to $0.05 per request in USDC on Base, settled onchain via the x402 protocol, no signup, no API key needed.

measured since 2026-09-07 (start of our harvest window) · $0.05 all-time · settled via ultravioletadao

BASE URL http://107.189.20.242:3131 │ WEBSITE http://107.189.20.242:3131 │ ENDPOINTS 3 │ NETWORK Base │ ASSET USDC │ MEMBER SINCE 2026-09-08 │ MONITORED SINCE 2026-09-08

VERDICT

ranking generation 3

mixed 66/100 #154 of 162 in AI by measured score

What the score read on this service: status offline, 51.6% uptime 30d, 33ms response p95, x402 compliance 13 of 14, $0.01 price against the category, on-chain traction measured. 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.

It is a score inside AI, 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 162 listings, this one among them. That set is wider than the 162 the position above is counted against, 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.

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.

ALTERNATIVES IN AI

Other AI services in this directory, ordered by the same measured score. The figures are ours: 30-day uptime from our own probes, 30-day settlement volume read on-chain (a conservative undercount, and null where we cannot measure it, never a zero).

Ranked alternative x402 services in the same category, with band, measured score, 30-day uptime and 30-day on-chain settlement volume
SERVICE BAND SCORE UPTIME 30D VOL 30D
Otto AI strong 95 100% $56.13
NetIntel strong 94 100% $16.76
x402engine strong 93 100% $28.00
GlianaAI solid 93 100% $68.10
Agent402.tools solid 92 99.7% $138.77
5 of 161 other ranked services in AI · see the whole category

ASSESSMENT

updated 1h ago

The parts the verdict above is computed from, each with its proof. Click any chip. Measured values stay read-only; unknown is honest, and an unknown is never counted as a zero.

reliability 51.6%
uptime · latest daily rollup
0%
uptime 7d
0%
uptime 30d
51.6%
uptime 90d
51.6%
response p95
33ms
avg response
18ms
total checks
182

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

compliance A (13/14): served over HTTPS, stale (probe failing)

13 of 14 x402 conformance checks pass; failing: served over HTTPS. Full checklist below.

jump to compliance checklist

price $0.01 to $0.05 (p49 in AI)
price (min)
$0.01
price (max)
$0.05
category percentile (min)
p49 in AI
category percentile (max)
p44 in AI
endpoints / prices
3 / 3
model
tiered
stability
100%
risk clean

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.

traction $0.05 30d · 1 buyers · top buyer 100% (address, not entity)
volume 30d
$0.05
buyers 30d
1
settlements 30d
3
measured since
2026-09-07 (start of our harvest window)
last settlement
2026-09-08
top buyer share
100% of 30d volume (address, not entity)
trend 7d vs 30d
0.00x the 30d daily rate
networks
eip155:8453
volume all-time
$0.05
settlements all-time
3
median settlement 30d
$0.01
max settlement 30d
$0.03
settled via
ultravioletadao ($0.05, 3 tx)

Conservative undercount: only USDC settlements via facilitators we measure are counted. A measured floor, not an estimate.

Top buyer share is part of the ranking score: a higher share lowers the traction part of the score, by up to half when one address holds all 30d volume.

CHANGES

1 in 30d

Payout, price, and schema changes detected on this service's x402 wire. A payout rotation at an unchanged price shows up here even when nothing else moves. Full feed at /changes.

changes schema changed 21d ago (1 in 30d)

schema changed · 21d ago

schema removed GET /x402/fa exact eip155:8453 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 USDC 1 application/json 60 http://107.189.20.242:3131/x402/fa {"name":"USD Coin","version":"2"}

schema removed GET /x402/invoice exact eip155:8453 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 USDC 1 application/json 60 http://107.189.20.242:3131/x402/invoice {"name":"USD Coin","version":"2"}

schema removed GET /x402/srt exact eip155:8453 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 USDC 1 application/json 60 http://107.189.20.242:3131/x402/srt {"name":"USD Coin","version":"2"}

schema added GET /x402/fa exact eip155:8453 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 USDC 2 300 {"name":"USD Coin","version":"2"}

schema added GET /x402/invoice exact eip155:8453 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 USDC 2 300 {"name":"USD Coin","version":"2"}

schema added GET /x402/srt exact eip155:8453 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 USDC 2 300 {"name":"USD Coin","version":"2"}

see all changes for this service

WHAT IT DOES

ai-derived

No AI synthesis has been produced for this service yet.

ENDPOINTS

Service endpoints with HTTP method, path, description, pricing, and network
METHOD PATH DESCRIPTION PRICE NETWORK ASSET 402 CHANNEL
GET /x402/fa Persian<->English AI translation/chat $0.03 Base USDC header
GET /x402/invoice Create a USDC-on-Base invoice, returns JSON + invoice URL $0.01 Base USDC header
GET /x402/srt Generate timed SRT subtitles from transcript text $0.05 Base USDC header
3 endpoints

REQUEST / RESPONSE EXAMPLE

An unpaid request to GET /x402/fa returns HTTP 402 with the payment terms. Settle onchain via your facilitator, then retry with the X-Payment header.

// request
curl -i 'http://107.189.20.242:3131/x402/fa'
// 402 response (captured by monitor) · 3 payloads · click to expand
[
  {
    "error": "Payment required",
    "accepts": [
      {
        "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
        "extra": {
          "name": "USD Coin",
          "version": "2"
        },
        "payTo": "0x3e2493fc3c3bB539ef4a4B24Ba9af383AB2ECCF9",
        "amount": "50000",
        "scheme": "exact",
        "network": "eip155:8453",
        "maxTimeoutSeconds": 300
      }
    ],
    "resource": {
      "url": "http://107.189.20.242:3131/x402/srt",
      "mimeType": "application/json",
      "description": "Generate timed SRT subtitles from transcript text"
    },
    "x402Version": 2
  },
  {
    "error": "Payment required",
    "accepts": [
      {
        "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
        "extra": {
          "name": "USD Coin",
          "version": "2"
        },
        "payTo": "0x3e2493fc3c3bB539ef4a4B24Ba9af383AB2ECCF9",
        "amount": "30000",
        "scheme": "exact",
        "network": "eip155:8453",
        "maxTimeoutSeconds": 300
      }
    ],
    "resource": {
      "url": "http://107.189.20.242:3131/x402/fa",
      "mimeType": "application/json",
      "description": "Persian<->English AI translation/chat"
    },
    "x402Version": 2
  },
  {
    "error": "Payment required",
    "accepts": [
      {
        "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
        "extra": {
          "name": "USD Coin",
          "version": "2"
        },
        "payTo": "0x3e2493fc3c3bB539ef4a4B24Ba9af383AB2ECCF9",
        "amount": "10000",
        "scheme": "exact",
        "network": "eip155:8453",
        "maxTimeoutSeconds": 300
      }
    ],
    "resource": {
      "url": "http://107.189.20.242:3131/x402/invoice",
      "mimeType": "application/json",
      "description": "Create a USDC-on-Base invoice, returns JSON + invoice URL"
    },
    "x402Version": 2
  }
]

OVER TIME

All charts use the 90d selector; each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/bozaaagh-paid-micro-api/price, /scores, /volume and /buyers. On-chain volume and distinct buyers are measured over the service's settlement address and are a conservative undercount (only settlements that reach a measured facilitator are counted). The on-chain series roll up hourly, so the latest day can be up to about an hour behind; distinct buyers are counted per payout address, so a service that settles to more than one address is an upper bound.

UPTIME
09-09 · uptime 72.1% · 15ms avg09-10 · uptime 0.0%09-11 · uptime 0.0%09-12 · uptime 0.0%09-13 · uptime 0.0%09-14 · uptime 0.0%09-15 · uptime 0.0%09-16 · uptime 0.0%09-17 · uptime 0.0%09-18 · uptime 0.0%09-19 · uptime 0.0%09-20 · uptime 0.0%09-21 · uptime 0.0%09-22 · uptime 0.0%09-23 · uptime 0.0%09-24 · uptime 0.0%09-25 · uptime 0.0%09-26 · uptime 0.0%09-27 · uptime 0.0%09-28 · uptime 0.0%09-29 · uptime 0.0%09-08 · uptime 100.0% · 19ms avg09-09 · uptime 72.1% · 15ms avg09-10 · uptime 0.0%09-11 · uptime 0.0%09-12 · uptime 0.0%09-13 · uptime 0.0%09-14 · uptime 0.0%09-15 · uptime 0.0%09-16 · uptime 0.0%09-17 · uptime 0.0%09-18 · uptime 0.0%09-19 · uptime 0.0%09-20 · uptime 0.0%09-21 · uptime 0.0%09-22 · uptime 0.0%09-23 · uptime 0.0%09-24 · uptime 0.0%09-25 · uptime 0.0%09-26 · uptime 0.0%09-27 · uptime 0.0%09-28 · uptime 0.0%09-29 · uptime 0.0%09-0809-29
90D UPTIME 51.6%
RESPONSE TIME
09-08 · 19ms avg09-08 · 19ms avg09-09 · 15ms avg09-09 · 15ms avg09-10 · 0ms avg09-10 · 0ms avg09-11 · 0ms avg09-11 · 0ms avg09-12 · 0ms avg09-12 · 0ms avg09-13 · 0ms avg09-13 · 0ms avg09-14 · 0ms avg09-14 · 0ms avg09-15 · 0ms avg09-15 · 0ms avg09-16 · 0ms avg09-16 · 0ms avg09-17 · 0ms avg09-17 · 0ms avg09-18 · 0ms avg09-18 · 0ms avg09-19 · 0ms avg09-19 · 0ms avg09-20 · 0ms avg09-20 · 0ms avg09-21 · 0ms avg09-21 · 0ms avg09-22 · 0ms avg09-22 · 0ms avg09-23 · 0ms avg09-23 · 0ms avg09-24 · 0ms avg09-24 · 0ms avg09-25 · 0ms avg09-25 · 0ms avg09-26 · 0ms avg09-26 · 0ms avg09-27 · 0ms avg09-27 · 0ms avg09-28 · 0ms avg09-28 · 0ms avg09-29 · 0ms avg09-29 · 0ms avg09-0809-29
AVG RESP 18ms
PRICE (captured 402, USD)
09-08 · $0.0309-29 · $0.03$0.0309-0809-29

Median across 3 endpoints. Use the selector to isolate one.

SUB-SCORES (uptime + x402 compliance)
09-08 uptime: 100.0% compliance: 93% checks09-09 uptime: 89.5% compliance: 93% checks09-10 uptime: 86.2% compliance: 93% checks09-11 uptime: 83.2% compliance: 93% checks09-12 uptime: 80.3% compliance: 93% checks09-13 uptime: 77.7% compliance: 93% checks09-14 uptime: 75.2% compliance: 93% checks09-15 uptime: 72.9% compliance: 93% checks09-16 uptime: 71.2% compliance: 93% checks09-17 uptime: 68.6% compliance: 93% checks09-18 uptime: 66.7% compliance: 93% checks09-19 uptime: 64.8% compliance: 93% checks09-20 uptime: 63.1% compliance: 93% checks09-21 uptime: 61.4% compliance: 93% checks09-22 uptime: 59.9% compliance: 93% checks09-23 uptime: 58.4% compliance: 93% checks09-24 uptime: 57.3% compliance: 93% checks09-25 uptime: 56.0% compliance: 93% checks09-26 uptime: 54.3% compliance: 93% checks09-27 uptime: 53.1% compliance: 93% checks09-28 uptime: 51.9% compliance: 93% checks09-29 uptime: 51.6% compliance: 93% checksuptimecompliance09-0809-29

checklist grew 11->14 on 2026-07-28; a step here is a metric change, not a regression

PILLARS OVER TIME (measured)

Measured site and economics pillars from the assessment history, so the latest value shown elsewhere on this page reads as a point on a trend rather than a permanent state.

VOLUME (on-chain settlement, USD)
09-07 · $0.0409-08 · $0.01peak $0.0409-0709-08
DISTINCT BUYERS
09-07 · 1 buyer09-08 · 1 buyerpeak 1 buyer09-0709-08

COMPLIANCE

13/14 checks pass · grade A · failing: served over HTTPS · stale (probe failing)

last 402 captured 2026-09-08 · last up 2026-09-09

  • 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

SITE PILLARS

  • homepage reachable
  • openapi doc
  • pricing page
  • llms.txt
  • robots.txt
  • terms page
recent checks (18) live · click to expand
TIME STATUS RESP CAUSE
○ DOWN 5ms network: fetch failed
○ DOWN 5ms network: fetch failed
○ DOWN 5ms network: fetch failed
○ DOWN 5ms network: fetch failed
○ DOWN 5ms network: fetch failed
○ DOWN 5ms network: fetch failed
○ DOWN 5ms network: fetch failed
○ DOWN 4ms network: fetch failed
○ DOWN 5ms network: fetch failed
○ DOWN 5ms network: fetch failed
○ DOWN 5ms network: fetch failed
○ DOWN 8ms network: fetch failed
○ DOWN 5ms network: fetch failed
○ DOWN 6ms network: fetch failed
○ DOWN 5ms network: fetch failed
○ DOWN 5ms network: fetch failed
○ DOWN 5ms network: fetch failed
○ DOWN 6ms network: fetch failed

EMBED THIS BADGE

Show that bozaaagh paid micro-API is monitored on x402-list. Paste this on your site or README, it links back to this live listing.

bozaaagh paid micro-API listed on x402-list
status
bozaaagh paid micro-API uptime on x402-list
live uptime
// HTML
<a href="https://x402-list.com/services/bozaaagh-paid-micro-api?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/bozaaagh-paid-micro-api.svg" alt="bozaaagh paid micro-API listed on x402-list" height="28">
</a>
// Markdown
[![bozaaagh paid micro-API on x402-list](https://x402-list.com/badge/bozaaagh-paid-micro-api.svg)](https://x402-list.com/services/bozaaagh-paid-micro-api?utm_source=badge&utm_medium=referral&utm_campaign=embed)
// HTML · live uptime variant
<a href="https://x402-list.com/services/bozaaagh-paid-micro-api?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/bozaaagh-paid-micro-api.svg?data=uptime" alt="bozaaagh paid micro-API uptime on x402-list" height="28">
</a>

RUN THIS SERVICE?

Keep this listing accurate: propose changes to the name, description, website, category or add new endpoints to monitor. Ownership is verified with a domain proof and every change is reviewed manually; measured data stays read-only.

[ 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) ]

To request delisting, email info@x402-list.com or update your listing at /services/bozaaagh-paid-micro-api/update.