x402 List Submit a serviceSubmit
Menu

Pico

payment-readyonline

payment-ready until 2026-11-15

Creator content monetization on Celo.

celopico.nl ↗

Call it

Base URL
https://celopico.nl
Payment
body (v1 style)
$ curl -i 'https://celopico.nl/api/content/e8d5e951-8fa2-4f29-83a3-62bad86d9095'

An unpaid request returns HTTP 402 with the payment terms. Sign a payment authorization, then retry with the payment header named in the 402 response.

Endpoints 1 paid route on celopico.nl

GET/api/content/e8d5e951-8fa2-4f29-83a3-62bad86d9095----since 11-07
Example 402 response

Endpoints and prices

Current paid endpoints; minimum quoted prices in USD where available; first capture dates in UTC
MethodPathDescriptionPriceNetworkAsset402 channelCaptured
GET/api/content/e8d5e951-8fa2-4f29-83a3-62bad86d9095USDm payment via Celo MiniPay----USDmbodysince 11-07

Payment evidence

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

1 payload captured by the monitor.

20 lines, scroll inside

{
  "accepts": [
    {
      "asset": "0x765DE816845861e75A25fCA122bb6898B8B1282a",
      "extra": {
        "name": "USDm",
        "version": "1"
      },
      "payTo": "0x413F08Dc5C387d3ceb2E60508c85bB4416067339",
      "scheme": "exact",
      "network": "eip155:42220",
      "mimeType": "application/json",
      "resource": "/api/content/e8d5e951-8fa2-4f29-83a3-62bad86d9095",
      "description": "USDm payment via Celo MiniPay",
      "maxAmountRequired": "2000000000000000000",
      "maxTimeoutSeconds": 300
    }
  ],
  "version": "0.2"
}

Can I trust it score from our own monitoring

score from our own monitoring

85/100 Solid

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

Reliability
100% uptime since 11-07
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-11-07. Last up 2026-11-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, 100% uptime, latest daily rollup (no 30d window yet), 2532ms response p95, x402 compliance 12 of 12, price not captured. 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 Content, 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 65 listings, this one among them: the same 65 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

Creator content monetization on Celo. Creators set prices for gated content, fans pay with cUSD via MiniPay. Returns x402 payment requirements for each content endpoint. Also supports free unlocking via GoodDollar G$ UBI tips.

Pico is a listed x402 Content 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-10-10 to 2026-11-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 · Content

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

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
118d
registrar
Key-Systems GmbH
hosting
custom
domain created
2026-07-12

Identity facts, not a risk score.

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

member since
2026-11-07
Recent checks
Latest 11 unpaid HTTP checks, newest first; response times in milliseconds, observation times in UTC
Checked at (UTC)StatusHTTPResponseEndpoints
Online4022596ms1
Online4022432ms1
Online4022193ms1
Online4022582ms1
Online4022504ms1
Online4023524ms1
Online4022694ms1
Online4022384ms1
Online4021273ms1
Online4021934ms1
Online4022532ms1

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 100% on all 1 completed day
Uptime
100% on all 1 completed day

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

More charts
Response time daily average, ms min 2390ms, avg 2409ms, max 2428ms

10-10 to 11-08* UTC

Each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/pico-mw6zj25d-0/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-11-07 to 2026-11-08: uptime percent, average response milliseconds, compliance passed/total, price percentile 0-100, site signals out of 6; UTC dates
DayUptimeResponseCompliancePrice percentileSite signals
2026-11-07100%2390.17ms12/12no data2/6
2026-11-08*100%2427.75msno datano datano data

Alternatives in Content

DevX Voice strong 99/100 --- up 30d --- 30d
Tollkit Web strong 99/100 100% up 30d --- 30d
SCRIPTMASTERLABS URL to Markdown API solid 90/100 98.7% up 30d $15.74 30d
Pinata solid 90/100 100% up 30d $13.68 30d
YouTube transcript API for AI agents solid 89/100 100% up 30d $0 30d

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

Markdown

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

HTML, live uptime variant

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