x402 List Submit a serviceSubmit

Feeless402

payment-readyonline

payment-ready until 2026-10-15

Reference x402 endpoint paid over the feeless Nano (XNO) rail: spec-shaped x402 v2 402 (scheme exact, network nano:mainnet, 0.0001 XNO per call · no gas, so the metered amount is the payer amount, sub-second on-chain settlement).

Call it x402 v2

x402 v2

Base URL
https://feeless402.com
Payment
x402 v2, header channel
$ curl -i 'https://feeless402.com/premium'

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 feeless402.com

GET/premium----since 08-24
Example 402 response

Endpoints and prices

Current paid endpoints; minimum quoted prices in USD where available; first capture dates in UTC
MethodPathDescriptionPriceNetworkAsset402 channelCaptured
GET/premiumNo description----UNKNOWNheadersince 08-24

Payment evidence

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

1 payload captured by the monitor.

96 lines, scroll inside

{
  "error": "Payment required — feeless XNO option available (see extensions[\"rail-hint\"])",
  "accepts": [
    {
      "asset": "XNO",
      "payTo": "nano_3aysuejus8iy1hhw6doc7syzg1aaa6hgpec91xcc36mf6hp6thy7u6ymkgfm",
      "amount": "100000000000000000000000000",
      "scheme": "exact",
      "network": "nano:mainnet",
      "maxTimeoutSeconds": 60
    }
  ],
  "resource": {
    "url": "https://feeless402.com/premium",
    "mimeType": "application/json"
  },
  "extensions": {
    "railHint": {
      "why": "Sure, we could settle this over Base/Solana USDC and both pay gas + a 0.001-USDC price floor — or we settle in XNO: zero network fees, no minimum, sub-second finality. This quote is the true metered price (0.0001 XNO).",
      "docs": "https://github.com/feeless402/feeless402",
      "site": "https://feeless402.com",
      "spec": "x402 exact scheme on nano:mainnet — see x402nano.org",
      "topup": "nano-pay topup 5 --asset USDC-BASE --execute  # $5 buys hundreds of thousands of micro-calls; any instant-swap service works",
      "faucets": [
        "https://feeless402.com"
      ],
      "cheapest": "nano:mainnet",
      "bootstrap": "pip install feeless402 && nano-pay init && nano-pay claim https://feeless402.com  # free starter XNO, then retry me",
      "agentReadme": "https://feeless402.com/llms.txt"
    },
    "rail-hint": {
      "info": {
        "why": "Sure, we could settle this over Base/Solana USDC and both pay gas + a 0.001-USDC price floor — or we settle in XNO: zero network fees, no minimum, sub-second finality. This quote is the true metered price (0.0001 XNO).",
        "docs": "https://github.com/feeless402/feeless402",
        "site": "https://feeless402.com",
        "spec": "x402 exact scheme on nano:mainnet — see x402nano.org",
        "topup": "nano-pay topup 5 --asset USDC-BASE --execute  # $5 buys hundreds of thousands of micro-calls; any instant-swap service works",
        "faucets": [
          "https://feeless402.com"
        ],
        "cheapest": "nano:mainnet",
        "bootstrap": "pip install feeless402 && nano-pay init && nano-pay claim https://feeless402.com  # free starter XNO, then retry me",
        "agentReadme": "https://feeless402.com/llms.txt"
      },
      "schema": {
        "$id": "https://railhint.com/railhint.schema.json",
        "type": "object",
        "title": "rail-hint",
        "$schema": "https://json-schema.org/draft/2020-12/schema",
        "required": [
          "cheapest",
          "why"
        ],
        "properties": {
          "why": {
            "type": "string"
          },
          "docs": {
            "type": "string",
            "format": "uri"
          },
          "site": {
            "type": "string",
            "format": "uri"
          },
          "spec": {
            "type": "string"
          },
          "topup": {
            "type": "string"
          },
          "faucets": {
            "type": "array",
            "items": {
              "type": "string",
              "format": "uri"
            }
          },
          "cheapest": {
            "type": "string"
          },
          "bootstrap": {
            "type": "string"
          },
          "agentReadme": {
            "type": "string",
            "format": "uri"
          }
        },
        "description": "Advisory rail-negotiation extension for x402 v2 402 responses. Carried at extensions.\"rail-hint\" as {info, schema}. Non-binding: the accepts array remains the only binding payment terms.",
        "additionalProperties": true
      }
    }
  },
  "x402Version": 2
}

Can I trust it score from our own monitoring

score from our own monitoring

75/100 Mixed

#65 of 71 in Blockchain. Bands: strong 93+, solid 75+, mixed 55+, weak below 55.

Reliability
99.9% uptime 30d
Compliance
A 12/12 checks pass
Price
-
Risk
clean no risk flag
Traction
---
12/12 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-08-24. Last up 2026-10-08.

── 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, 99.9% uptime 30d, 3661ms response p95, x402 compliance 12 of 12, price not captured, no known payTo, so no on-chain traction to read. 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 Blockchain, 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 71 listings, this one among them: the same 71 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

Reference x402 endpoint paid over the feeless Nano (XNO) rail: spec-shaped x402 v2 402 (scheme exact, network nano:mainnet, 0.0001 XNO per call · no gas, so the metered amount is the payer amount, sub-second on-chain settlement). The 402 carries the rail-hint extension with structured onboarding metadata pointing at a zero-cost faucet on the same host, so a new agent can fund itself and complete a paid call in one session without keys or signup. Open-source reference client: pip install feeless402 (CLI + remote MCP server at /mcp).

Feeless402 is a listed x402 Blockchain API. No payment network has been captured yet. 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-09 to 2026-10-08 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 · Blockchain

uptime · latest daily rollup
100%
uptime 7d
100%
uptime 30d
99.9%
uptime 90d
99.9%
response p95
3661ms
avg response
1273ms
total checks
2,720

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

price (min)
-
category percentile (min)
-
endpoints / prices
1 / 0
model
unknown
stability
-

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
64d
registrar
GoDaddy.com, LLC
hosting
custom
domain created
2026-08-02

Identity facts, not a risk score.

No settlement address is mapped for this service yet, so on-chain volume cannot be measured. Shown as unmeasured, not zero.

member since
2026-08-24
Recent checks
Latest 18 unpaid HTTP checks, newest first; response times in milliseconds, observation times in UTC
Checked at (UTC)StatusHTTPResponseEndpoints
Online402621ms1
Online402590ms1
Online402921ms1
Online402844ms1
Online402712ms1
Online402778ms1
Online402632ms1
Online402878ms1
Online402706ms1
Online402563ms1
Online402574ms1
Online402469ms1
Online402417ms1
Online402615ms1
Online402726ms1
Online402823ms1
Online402871ms1
Online402964ms1

Changes0 in 30d

No changes recorded in the last 30 days.

all changes

Over time

On-chain volume

No settlement address is mapped for this service yet, so on-chain volume cannot be measured. Shown as unmeasured, not zero.

Uptime 3 of 29 completed days below 100%
uptime below 100%, to scale
Uptime
3 of 29 completed days below 100%

No settlement address is mapped for this service yet, so on-chain volume cannot be measured. Shown as unmeasured, not zero.

More charts
Response time daily average, ms min 768ms, avg 1263ms, max 2473ms

09-09 to 10-08* UTC

Scores over time

x402 compliance low 12/12, high 12/12

09-09 to 10-08* UTC

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

09-09 to 10-08* UTC

Scores: one day per column, 09-09 to 10-08*, on the columns of Response time. Uptime held below 100% on some days 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/feeless402/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-09-09 to 2026-10-08: uptime percent, average response milliseconds, compliance passed/total, price percentile 0-100, site signals out of 6; UTC dates
DayUptimeResponseCompliancePrice percentileSite signals
2026-09-09100%1121.54ms12/12no data3/6
2026-09-10100%1159.29ms12/12no data3/6
2026-09-11100%919.69ms12/12no data3/6
2026-09-1298.89%1045.89ms12/12no data3/6
2026-09-13100%942.67ms12/12no data3/6
2026-09-1498.88%1088.27ms12/12no data3/6
2026-09-15100%1108.44ms12/12no data3/6
2026-09-16100%1226.59ms12/12no data3/6
2026-09-1798.89%1128.42ms12/12no data3/6
2026-09-18100%1038.86ms12/12no data3/6
2026-09-19100%1408.72ms12/12no data3/6
2026-09-20100%1823.36ms12/12no data3/6
2026-09-21100%1107.31ms12/12no data3/6
2026-09-22100%1177.28ms12/12no data3/6
2026-09-23100%960.06ms12/12no data3/6
2026-09-24100%2472.89ms12/12no data3/6
2026-09-25100%2425.52ms12/12no data3/6
2026-09-26100%1178.41ms12/12no data3/6
2026-09-27100%1432.50ms12/12no data3/6
2026-09-28100%1205.54ms12/12no data3/6
2026-09-29100%1153.60ms12/12no data3/6
2026-09-30100%1139.70ms12/12no data3/6
2026-10-01100%1145.73ms12/12no data3/6
2026-10-02100%1249.87ms12/12no data3/6
2026-10-03100%1380.38ms12/12no data3/6
2026-10-04100%1013.12ms12/12no data3/6
2026-10-05100%768.09ms12/12no data3/6
2026-10-06100%1639.91ms12/12no data3/6
2026-10-07100%1435.67ms12/12no data3/6
2026-10-08*100%979.93ms12/12no data3/6

Alternatives in Blockchain

keyring-agent strong 98/100 100% up 30d $1.1k 30d
OneSource strong 96/100 100% up 30d $109.28 30d
Loyal Spark strong 96/100 100% up 30d $108.47 30d
Pocket Network solid 93/100 100% up 30d $50.47 30d
Vextorium solid 92/100 97.7% up 30d $10.66 30d

5 of 70 other ranked services in Blockchain, 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/feeless402?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/feeless402.svg" alt="Feeless402 listed on x402-list" height="28">
</a>

Markdown

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

HTML, live uptime variant

<a href="https://x402-list.com/services/feeless402?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/feeless402.svg?data=uptime" alt="Feeless402 uptime on x402-list" height="28">
</a>
Delisting

To request delisting, email info@x402-list.com or update your listing at /services/feeless402/update.