payment-ready until 2026-10-06
Deterministic pre-execution audit of a prediction-market trade thesis. Submit the reasoning behind a trade as free text; receive PASS, WAIT, or FAIL with the taxonomy codes that fired, a risk score, and a reproducible verdict_hash. Audits the reasoning, not the transaction. Out-of-scope requests are refused free. Payable over HTTP x402 or MCP.
Pay from $2.00 in USDC on Base, settled onchain via the x402 protocol, no signup, no API key needed.
measured since 2026-07-14 (start of our harvest window) · $34.75 all-time · settled via coinbase
VERDICT
ranking generation 3solid 77/100 #46 of 54 in Blockchain by measured score
What the score read on this service: status online, 99.9% uptime 30d, 2153ms response p95, x402 compliance 14 of 14, $2 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 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 54 listings, this one among them. That set is wider than the 54 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 BLOCKCHAIN
Other Blockchain 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).
| SERVICE | BAND | SCORE | UPTIME 30D | VOL 30D |
|---|---|---|---|---|
| Loyal Spark | strong | 96 | 100% | $121.88 |
| OneSource | strong | 95 | 100% | $101.46 |
| true402 | solid | 90 | 100% | $0.26 |
| SolSigs | solid | 89 | 100% | $0 |
| GPUOps Blockchain Data MCP | solid | 88 | 100% | $0 |
ASSESSMENT
updated 4h agoThe 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 99.9%
- uptime · latest daily rollup
- 100%
- uptime 7d
- 100%
- uptime 30d
- 99.9%
- uptime 90d
- 99.9%
- response p95
- 2153ms
- avg response
- 1591ms
- total checks
- 2,776
Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.
compliance A (14/14)
14 of 14 x402 conformance checks pass. Full checklist below.
price $2.00 (p97 in Blockchain)
- price (min)
- $2.00
- category percentile (min)
- p97 in Blockchain
- endpoints / prices
- 1 / 1
- model
- flat
- 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
- 221d
- registrar
- Cloudflare, Inc
- hosting
- custom
- domain created
- 2026-02-16
Identity facts, not a risk score.
traction $8.00 30d · 1 buyers · top buyer 100% (address, not entity)
- volume 30d
- $8.00
- buyers 30d
- 1
- settlements 30d
- 4
- measured since
- 2026-07-14 (start of our harvest window)
- last settlement
- 2026-09-01
- 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
- $34.75
- settlements all-time
- 20
- median settlement 30d
- $2.00
- max settlement 30d
- $2.00
- settled via
- coinbase ($8.00, 4 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.
WHAT IT DOES
ai-derivedNo AI synthesis has been produced for this service yet.
ENDPOINTS
| METHOD | PATH | DESCRIPTION | PRICE | NETWORK | ASSET | 402 CHANNEL |
|---|---|---|---|---|---|---|
| POST | /x402/verify | $2.00 | Base | USDC | header |
REQUEST / RESPONSE EXAMPLE
An unpaid request to POST /x402/verify returns HTTP 402 with the payment terms. Settle onchain via your facilitator, then retry with the X-Payment header.
curl -i -X POST 'https://mcp.djzs.ai/x402/verify'
// 402 response (captured by monitor) · 1 payload · click to expand
[
{
"error": "PAYMENT_REQUIRED",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xc1923748669dFC3a79497d0403A90a275161eCCA",
"amount": "2000000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
],
"resource": {
"url": "https://mcp.djzs.ai/x402/verify",
"mimeType": "application/json",
"description": "Deterministic pre-execution audit of a prediction-market trade thesis. 2 USDC per audit."
},
"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/djzs-protocol/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.
checklist grew 11->14 on 2026-07-28; a step here is a metric change, not a regression
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.
COMPLIANCE
14/14 checks pass · grade Alast 402 captured 2026-08-20 · last up 2026-09-29
- 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
EMBED THIS BADGE
<a href="https://x402-list.com/services/djzs-protocol?utm_source=badge&utm_medium=referral&utm_campaign=embed"> <img src="https://x402-list.com/badge/djzs-protocol.svg" alt="DJZS Protocol listed on x402-list" height="28"> </a>
[](https://x402-list.com/services/djzs-protocol?utm_source=badge&utm_medium=referral&utm_campaign=embed)
<a href="https://x402-list.com/services/djzs-protocol?utm_source=badge&utm_medium=referral&utm_campaign=embed"> <img src="https://x402-list.com/badge/djzs-protocol.svg?data=uptime" alt="DJZS Protocol uptime on x402-list" height="28"> </a>