Office of the Count
payment-ready until 2026-11-11
Deterministic counting of public agent rooms by message ids: author counts, per-author message ids, truncation and referral detection.
Call it x402 v1
x402 v1
- Base URL
- https://ai.paideuma.de/x402
- Payment
- x402 v1, body (v1 style)
$ curl -i 'https://ai.paideuma.de/x402/count' An unpaid request returns HTTP 402 with the payment terms. Sign a payment authorization, then retry with the X-PAYMENT header.
Endpoints 1 paid route on ai.paideuma.de
Prices as captured in the 402 response: $0.05, unchanged since first capture.
Example 402 response
Endpoints and prices
| Method | Path | Description | Price | Network | Asset | 402 channel | Captured |
|---|---|---|---|---|---|---|---|
| GET | / | Office of the Count · verifiable count of a public agent room (JSON). | $0.05 | Base | USDC | body | since 11-04 |
Payment evidence
402 payload captured at . Check evidence JSON · Measurement methodology.
1 payload captured by the monitor for GET /count.
20 lines, scroll inside
{
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USDC",
"version": "2"
},
"payTo": "0xdD997081d30a35ED497467e9Cf634662d08D8a01",
"scheme": "exact",
"network": "base",
"mimeType": "application/json",
"resource": "https://ai.paideuma.de/x402/count",
"description": "Office of the Count — verifiable count of a public agent room (JSON).",
"maxAmountRequired": "50000",
"maxTimeoutSeconds": 60
}
],
"x402Version": 1
} Can I trust it score from our own monitoring
score from our own monitoring
#14 of 184 in Verification. Bands: strong 93+, solid 75+, mixed 55+, weak below 55.
- Reliability
- 100% uptime since 11-04
- Compliance
- A 13/14 checks pass, failing: declares the current x402 version (2)
- Price
- $0.05 p82 in Verification
- Risk
- clean no risk flag
- Traction
- ---
13/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-11-04. Last up 2026-11-04.
── 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), 166ms response p95, x402 compliance 13 of 14, $0.05 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 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 184 listings, this one among them: the same 184 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
Deterministic counting of public agent rooms by message ids: author counts, per-author message ids, truncation and referral detection. Free tier 3 requests/day per IP+room. Paid tier 0.05 USDC on Base via x402, settled directly to the operator wallet. No custody, no accounts, no API keys.
Office of the Count 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-06 to 2026-11-04 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 · Verification
- uptime · latest daily rollup
- -
- uptime 7d
- -
- uptime 30d
- -
- uptime 90d
- -
- response p95
- 166ms
- avg response
- 166ms
- 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)
- $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.
On-chain traction has not been assessed for this service yet.
- member since
- 2026-11-04
Recent checks
| Checked at (UTC) | Status | HTTP | Response | Endpoints |
|---|---|---|---|---|
| Online | 402 | 110ms | 1 | |
| Online | 402 | 92ms | 1 | |
| Online | 402 | 81ms | 1 | |
| Online | 402 | 154ms | 1 | |
| Online | 402 | 220ms | 1 | |
| Online | 402 | 213ms | 1 | |
| Online | 402 | 140ms | 1 | |
| Online | 402 | 119ms | 1 | |
| Online | 402 | 166ms | 1 |
Changes0 in 30d
No changes recorded in the last 30 days.
Over time
On-chain traction has not been assessed for this service yet.
- Uptime
- no completed-day data
On-chain traction has not been assessed for this service yet.
More charts
10-06 to 11-04* UTC
Each series spans only the dates it has data for. Every series is also served as JSON at /api, /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.
| Day | Uptime | Response | Compliance | Price percentile | Site signals |
|---|---|---|---|---|---|
| 2026-11-04* | 100% | 168.67ms | 13/14 | p82 | 1/6 |
Alternatives in Verification
5 of 183 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 listingEarn 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/ office-of-the-count? utm_source=badge& utm_medium=referral& utm_campaign=embed"> <img src="https://x402-list.com/ badge/ office-of-the-count.svg" alt="Office of the Count listed on x402-list" height="28"> </a>
Markdown
[](https://x402-list.com/ services/ office-of-the-count? utm_source=badge& utm_medium=referral& utm_campaign=embed)
HTML, live uptime variant
<a href="https://x402-list.com/services/ office-of-the-count? utm_source=badge& utm_medium=referral& utm_campaign=embed"> <img src="https://x402-list.com/ badge/ office-of-the-count.svg? data=uptime" alt="Office of the Count 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.