x402 List Submit a serviceSubmit
Menu

Orbylon

payment-readyonline

payment-ready until 2026-11-06

Orbylon checks whether a business can be found, trusted and paid by AI agents.

orbylon.com ↗

Call it x402 v2

x402 v2

Base URL
https://orbylon.com
Payment
x402 v2, header channel
$ curl -i -X POST 'https://orbylon.com/api/scan/full'

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

Endpoints 1 paid route on orbylon.com

POST/api/scan/fullBase$0.05since 09-14

Prices as captured in the 402 response: $0.05.

Example 402 response

Endpoints and prices

Current paid endpoints; minimum quoted prices in USD where available; first capture dates in UTC
MethodPathDescriptionPriceNetworkAsset402 channelCaptured
POST/api/scan/fullAgent Readiness Scan, full report: runs all 16 checks against a domain and returns the complete machine-readable results synchronously, plus a hosted report URL.$0.05BaseUSDCheadersince 09-14

Payment evidence

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

1 payload captured by the monitor.

123 lines, scroll inside

{
  "error": "Payment required",
  "accepts": [
    {
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "extra": {
        "name": "USD Coin",
        "version": "2"
      },
      "payTo": "0x7ba267B21ec77309CBbdce92D3005421329db62a",
      "amount": "50000",
      "scheme": "exact",
      "network": "eip155:8453",
      "maxTimeoutSeconds": 300
    }
  ],
  "resource": {
    "url": "https://orbylon.com/api/scan/full",
    "mimeType": "application/json",
    "description": "Agent Readiness Scan, full report: runs all 16 checks against a domain and returns the complete machine-readable results synchronously, plus a hosted report URL."
  },
  "extensions": {
    "bazaar": {
      "info": {
        "input": {
          "body": {
            "url": "example.com"
          },
          "type": "http",
          "method": "POST",
          "bodyType": "json"
        },
        "output": {
          "type": "json",
          "example": {
            "scores": {
              "grade": "D",
              "total": 34
            },
            "results": [
              {
                "id": "V4",
                "label": "Business identity key",
                "pillar": "verifiability",
                "status": "fail",
                "evidence": "No Orbylon identity key published for this domain.",
                "question": "Can anything you send be proven to be yours?"
              }
            ],
            "report_url": "https://orbylon.com/scan/example-com-ab12"
          }
        }
      },
      "schema": {
        "type": "object",
        "$schema": "https://json-schema.org/draft/2020-12/schema",
        "required": [
          "input"
        ],
        "properties": {
          "input": {
            "type": "object",
            "required": [
              "type",
              "method",
              "bodyType",
              "body"
            ],
            "properties": {
              "body": {
                "required": [
                  "url"
                ],
                "properties": {
                  "url": {
                    "type": "string",
                    "description": "Domain or URL of the business to scan."
                  }
                }
              },
              "type": {
                "type": "string",
                "const": "http"
              },
              "method": {
                "enum": [
                  "POST",
                  "PUT",
                  "PATCH"
                ],
                "type": "string"
              },
              "bodyType": {
                "enum": [
                  "json",
                  "form-data",
                  "text"
                ],
                "type": "string"
              }
            },
            "additionalProperties": false
          },
          "output": {
            "type": "object",
            "required": [
              "type"
            ],
            "properties": {
              "type": {
                "type": "string"
              },
              "example": {
                "type": "object"
              }
            }
          }
        }
      }
    }
  },
  "x402Version": 2
}

Can I trust it score from our own monitoring

score from our own monitoring

80/100 Solid

#137 of 177 in Verification. Bands: strong 93+, solid 75+, mixed 55+, weak below 55.

Reliability
100% uptime 30d
Compliance
A 14/14 checks pass
Price
$0.05 p82 in Verification
Risk
clean no risk flag
Traction
$0.20 30d 4 buyers, top buyer 25% (address, not entity)
14/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-09-14. Last up 2026-10-30.

── 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 30d, 1335ms response p95, x402 compliance 14 of 14, $0.05 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.

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 Verification, 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 177 listings, this one among them: the same 177 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.

Settled via coinbase ($0.20, 4 tx). Traction is a conservative undercount; first settlement seen 2026-09-15.

All measured facts

What it does

Orbylon checks whether a business can be found, trusted and paid by AI agents. The paid endpoint runs sixteen checks against any domain and returns the complete machine readable result, plus a hosted report URL a person can read. Settlement is USDC on Base, direct to the seller wallet. Orbylon never holds funds.

Orbylon is a listed x402 Verification 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-10-01 to 2026-10-30 UTC. Daily monitoring and settlement rollups do not expose their computation time; a bucket date is not an update timestamp. Latest settlement in the assessment: . 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 · Verification

uptime · latest daily rollup
100%
uptime 7d
100%
uptime 30d
100%
uptime 90d
100%
response p95
1335ms
avg response
856ms
total checks
3,030

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

price (min)
$0.05
category percentile (min)
p82 in Verification
endpoints / prices
1 / 1
model
flat
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.

assessment volume 30d
$0.20
exact assessment volume 30d (USD)
0.2
assessment recorded at (UTC)
2026-10-30T05:13:15.783Z
buyers 30d
4
settlements 30d
4
measured since
2026-09-15 (start of our harvest window)
last settlement
2026-10-26
top buyer share
25% of 30d volume (address, not entity)
top 3 buyers share
75% of 30d volume (addresses, not entities)
concentrated volume
no
trend 7d vs 30d
1.07x the 30d daily rate
networks
eip155:8453
volume all-time
$0.30
settlements all-time
6
median settlement 30d
$0.05
max settlement 30d
$0.05

Assessment volume uses the latest 30d assessment. Over time sums daily address snapshots, rounded to cents and refreshed separately. The two sources can differ in timing, precision and shared-address attribution. Amounts use cents for comparison; known sub-cent values keep up to 12 significant digits. The exact stored assessment value is shown above.

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

Top buyer share lowers the on-chain traction part of the ranking score behind this page's verdict and /best, by up to half when one address holds all 30d volume. The Recommended and Highest volume sorts of the services list do not use it; they use the Concentrated volume rule instead.

member since
2026-09-14
Recent checks
Latest 18 unpaid HTTP checks, newest first; response times in milliseconds, observation times in UTC
Checked at (UTC)StatusHTTPResponseEndpoints
Online402474ms1
Online4021875ms1
Online402335ms1
Online402548ms1
Online402553ms1
Online4021267ms1
Online402521ms1
Online402596ms1
Online402559ms1
Online402699ms1
Online402382ms1
Online402515ms1
Online402660ms1
Online402509ms1
Online4021379ms1
Online402714ms1
Online402809ms1
Online402644ms1

Changes0 in 30d

No changes recorded in the last 30 days.

all changes

Over time

On-chain volume daily snapshots, USD 30d: $0.20, peak $0.05 on 10-19
volume no data in the payload
Distinct buyers per dayDistinct buyers per day
Uptime 100% on all 29 completed days
Volume 30d
$0.20
Uptime
100% on all 29 completed days
Daily on-chain settlement volume in US dollars, 2026-10-01 to 2026-10-30; highest day $0.05 on 10-19; 28 days have no data in the payload; distinct buyers per day
More charts
Response time daily average, ms min 442ms, avg 796ms, max 1292ms

10-01 to 10-30* UTC

Scores over time

x402 compliance low 14/14, high 14/14

10-01 to 10-30* UTC

Price percentile in Verification own low to high; exact values below

10-01 to 10-30* UTC

Site signals present (of 6) own low to high; exact values below

10-01 to 10-30* UTC

Scores: one day per column, 10-01 to 10-30*, on the columns of Response time. Uptime held 100% every day in this window, including any partial day. Daily readings remain in the Uptime strip and Values. The checklist grew from 11 to 14 checks on 2026-07-28, before this window. Pillar lines use their own low and high. Exact dated readings are available in each readout and in Values.

Each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/orbylon/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.

Daily snapshot total, 30d: $0.10, peak $0.05 on 10-19. The visible 30d total in Traction comes from the latest assessment. These sources can differ in their window, refresh time, cent rounding and shared-address attribution.

Daily address snapshots: 2026-10-01 to 2026-10-30 UTC; * today so far, partial (UTC). Daily snapshots store cents. A recorded $0.00 with settlements cannot distinguish exact zero from volume rounded away. Lost precision is unavailable here.

Settlement volume uses the stored USD valuation of tracked payments; it is distinct from token quantities. USD-pegged assets are valued at 1 USD per token in these rollups. The measured settlement floor does not cover all payments to this service.

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-01 to 2026-10-30: address settlement volume in USD, distinct buyer and settlement counts, uptime percent, average response milliseconds, compliance passed/total, price percentile 0-100, site signals out of 6; UTC dates
DayVolumeBuyersSettlementsUptimeResponseCompliancePrice percentileSite signals
2026-10-01no datano datano data100%1291.86ms14/14p795/6
2026-10-02no datano datano data100%1196.43ms14/14p795/6
2026-10-03no datano datano data100%1058.30ms14/14p795/6
2026-10-04no datano datano data100%981.50ms14/14p795/6
2026-10-05no datano datano data100%815.71ms14/14p805/6
2026-10-06no datano datano data100%825.38ms14/14p805/6
2026-10-07no datano datano data100%1059.36ms14/14p805/6
2026-10-08no datano datano data100%1256.42ms14/14p805/6
2026-10-09no datano datano data100%1071.80ms14/14p805/6
2026-10-10no datano datano data100%1060.93ms14/14p795/6
2026-10-11no datano datano data100%1095.51ms14/14p795/6
2026-10-12no datano datano data100%879.87ms14/14p795/6
2026-10-13no datano datano data100%830.08ms14/14p795/6
2026-10-14no datano datano data100%955.68ms14/14p795/6
2026-10-15no datano datano data100%866.08ms14/14p795/6
2026-10-16no datano datano data100%630.44ms14/14p795/6
2026-10-17no datano datano data100%542.79ms14/14p795/6
2026-10-18no datano datano data100%615.86ms14/14p795/6
2026-10-19$0.0511100%626.11ms14/14p795/6
2026-10-20no datano datano data100%718.32ms14/14p795/6
2026-10-21no datano datano data100%686.57ms14/14p795/6
2026-10-22no datano datano data100%571.20ms14/14p795/6
2026-10-23no datano datano data100%581.91ms14/14p795/6
2026-10-24no datano datano data100%554.15ms14/14p795/6
2026-10-25no datano datano data100%462.12ms14/14p795/6
2026-10-26$0.0511100%472.34ms14/14p795/6
2026-10-27no datano datano data100%442.37ms14/14p815/6
2026-10-28no datano datano data100%626.19ms14/14p825/6
2026-10-29no datano datano data100%470.55ms14/14p825/6
2026-10-30*no datano datano data100%647.00ms14/14p825/6

Alternatives in Verification

agentshield.live facts strong 99/100 100% up 30d --- 30d
PaywallWatch strong 96/100 100% up 30d --- 30d
Grokbot Safe Read & x402 Preflight strong 95/100 100% up 30d --- 30d
how.is strong 95/100 100% up 30d --- 30d
Apex Pay · verified agent tools strong 95/100 100% up 30d --- 30d

5 of 176 other ranked services in Verification, ordered by the same measured score.

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/orbylon?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/orbylon.svg" alt="Orbylon listed on x402-list" height="28">
</a>

Markdown

[![Orbylon on x402-list](https://x402-list.com/badge/orbylon.svg)](https://x402-list.com/services/orbylon?utm_source=badge&utm_medium=referral&utm_campaign=embed)

HTML, live uptime variant

<a href="https://x402-list.com/services/orbylon?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/orbylon.svg?data=uptime" alt="Orbylon 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.