Daily transfers, volume and coverage →
bess-x402.onrender.com · bess-x402.onrender.com · Security
Passive audit of a website in one call: 0-100 score and grade across security headers, TLS certificate, email authentication (SPF, DKIM, DMARC) and SEO basics (title, description, canonical, og:image, robots.txt, sitemap), with a list of concrete fixes, plus registrar, domain age, tech stack and AI
| Network | Scheme | Amount | Asset |
|---|---|---|---|
| Arbitrum | exact | 0.02 | USDC |
| Base | exact | 0.02 | USDC |
| Polygon | exact | 0.02 | USDC |
“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 20000 = 0.02 USDC per call on Base. 3 payment options published.
endpoint
https://bess-x402.onrender.com/v1/reports/website
{
"method": "GET",
"queryParams": {
"domain": "stripe.com"
},
"type": "http"
}
{
"example": {
"domain": "stripe.com",
"fixes": [
{
"area": "security",
"fix": "add the permissions-policy header"
},
{
"area": "dns",
"fix": "consider enabling DNSSEC"
}
],
"generated": "2026-10-29T06:46:05+00:00",
"grade": "A",
"note": "passive checks only (public DNS, RDAP, one HTTPS page load); no scanning",
"score": 97,
"scores": {
"email": 100,
"security_headers": 90,
"seo": 100,
"tls": 100
},
"summary": {
"ai_crawlers": {
"Applebot-Extended": "default",
"Bytespider": "default",
"CCBot": "default",
"ChatGPT-User": "default",
"ClaudeBot": "default",
"GPTBot": "default",
"Google-Extended": "default",
"PerplexityBot": "default",
"anthropic-ai": "default"
},
"certificate_days_left": 29,
"description": "Stripe is a financial services platform that helps all types of businesses accept payments, build flexible billing models, and manage money movement.",
"dmarc_policy": "reject",
"email_grade": "A",
"expires": "2027-09-11T04:00:00Z",
"final_url": "https://stripe.com",
"https_status": 200,
"registered": "1995-09-12T04:00:00Z",
"registrar": "SafeNames Ltd.",
"security_header_grade": "A",
"technologies": [
"WooCommerce",
"Next.js"
],
"title": "Stripe | Financial Infrastructure to Grow Your Revenue"
}
},
"type": "json"
}
Examples are the provider's own, not a call we made.
The payout address is also published by 182 other service(s); the volume cannot be attributed to one of them.
| Window | Observed | Transfers |
|---|---|---|
| Last complete day (2026-10-28) | — | — |
| Last 7 days | — | — |
| Last 30 days | — | — |
| Growth, 7d against the 7 before | not comparable | |
The payout address is shared with 182 other service(s). That is normal for facilitator and platform addresses, and it is why this profile shows no inflow figure. The volume exists — it just cannot be split without inventing a rule.
How attribution works →26 of 13,801 services (0.2%) in Security have attributable inflows; 11,599 have a source-measured call count. Median measured calls: 2.
Rank this category by observed inflows →Passive audit of a website in one call: 0-100 score and grade across security headers, TLS certificate, email authentication (SPF, DKIM, DMARC) and SEO basics (title, description, canonical, og:image, robots.txt, sitemap), with a list of concrete fixes, plus registrar, domain age, tech stack and AI crawler rules. Use for lead qualification, vendor checks or SEO and security reviews.
Quoted from x402 Bazaar · source record · read 2026-10-29
Attribution blocked
· confidence low
The payout address is also published by 182 other service(s); the volume cannot be attributed to one of them.
Why revenue is “unknown”. A revenue figure needs a receipt: an amount a buyer actually paid for this service. We hold none for this entry, and we hold no funds at all. What we have instead is an activity value of $0.02 — the source's call count multiplied by the published price. That is what the list price implies, not what anyone paid. The payout address is also published by 182 other service(s); the volume cannot be attributed to one of them.
No daily history has been archived for this service yet. Open the full daily history →
A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it. See evidence levels.
One row per statement. “Verified” means we checked it ourselves and the finding is quoted. “Provider claim” means we read it in the provider's own record. “Not found” is a statement about our search, not proof of absence.
| Statement | Status | What we found | Source | Checked |
|---|---|---|---|---|
| Endpoint | Provider claim |
https://bess-x402.onrender.com/v1/reports/website
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
api.cdp.coinbase.com | 2026-10-29 |
| Input output | Provider claim |
Request/response examples published with the listing
EvidenceBeispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters. |
api.cdp.coinbase.com | 2026-10-29 |
| Payment | Provider claim |
3 rails: Base, Polygon, Arbitrum · payee 0x1129A6BB9C6165FF07fdC509c107B522CA0e1871
EvidenceAus den `accepts`-Einträgen: Netzwerk, Asset, Empfängeradresse und Betrag. Die Adresse ist die Grundlage der späteren On-Chain-Zuordnung; sie ist noch nicht durch eine eigene 402-Antwort bestätigt. |
api.cdp.coinbase.com | 2026-10-29 |
| Pricing | Provider claim |
0.02 USDC per call
EvidenceAtomic amount 20000 = 0.02 USDC per call on Base. 3 payment options published. Netzwerk: Base, Polygon, Arbitrum. |
api.cdp.coinbase.com | 2026-10-29 |
| Protocol | Provider claim |
x402 (HTTP 402 payment challenge)
EvidenceIm x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http). |
api.cdp.coinbase.com | 2026-10-29 |
| Provider | Provider claim |
bess-x402.onrender.com
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
api.cdp.coinbase.com | 2026-10-29 |
| Usage | Verified |
1 calls / 1 unique payers in the last 30 days
EvidenceSource-reported usage from Coinbase x402 Bazaar, read on 2026-10-29. Letzter Aufruf laut Quelle: 2026-10-29T06:50:04.213Z. Aufrufe sind kein Umsatz. |
api.cdp.coinbase.com | 2026-10-29 |
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.
Sorted by source-measured calls, not by our opinion. The right-hand figure is observed inflow, which stays empty for peers whose address is shared.
| With a measured call count | 11,599 (84.0 %) |
|---|---|
| With a published price | 11,873 (86.0 %) |
| With attributable inflows | 26 (0.2 %) |
| Observed inflows · 30d | $192.52 |
| Median measured calls | 2 |
| Median price per call | $0.01 |
Email deliverability & domain security check — validates SPF, DKIM (multi-selector), and DMARC, detects spoofing and misconfigurations, and returns an A–F email security grade with transparent deductions. Anti-spam / ant...
Full website audit in one call: accessibility (WCAG 2.1 A/AA via axe-core), on-page SEO, HTTP security headers and page speed / page weight, from a single browser load of one URL. Cheaper than four separate calls; if any...
CVE vulnerability lookup. Returns security vulnerability records by CVE id or keyword from the NIST National Vulnerability Database and GitHub Security Advisories, each with CVSS score, severity, CWE weakness class, affe...
Resolve DNS records using DNS-over-HTTPS and return structured JSON for infrastructure, security, and agent workflows.
Chosen by category and by whether we have measured them, not by who pays us. A sponsored placement in this list is labelled as such.