cryptopulse.saascloud.ai
Composite 0-100 buy-safety score for any token: combines contract security analysis (honeypot, taxes, ownership risks) with live market depth (liquidity, volume, activity) into a single verdict: avoid | high-risk | caution | ok | strong. One call answers 'should my agent touch this token?'
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Live 402 challenge
Captured by the enrichment pass, not read just now. Prices can change — always read the 402 the endpoint answers with.
{
"error": "X-PAYMENT header is required",
"accepts": [
{
"scheme": "exact",
"network": "base",
"mimeType": "application/json",
"resource": "https://cryptopulse.saascloud.ai/api/token-score",
"description": "Composite 0-100 buy-safety score for any token: combines contract security analysis (honeypot, taxes, ownership risks) with live market depth (liquidity, volume, activity) into a single verdict: avoid | high-risk | caution | ok | strong. One call answers 'should my agent touch this token?'",
"outputSchema": {
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"chain": "base",
"address": "0x0000000000000000000000000000000000000000"
}
},
"output": {
"type": "json",
"example": {
"score": 72,
"reasons": [
"thin liquidity"
],
"verdict": "ok",
"components": {
"market": 27,
"security": 45
}
}
}
}
}
],
"x402Version": 1
}Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
Pay 0.05 USDC on Base to 0x9331…8C409. The signed payment is good for 5 minutes.
- Paid to
- 0x9331…8C409
- USD Coin contract
- 0x8335…02913
- Payment window
- 5 minutes
- As published
- 50000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x9331bf848992A61f184654c1c0E931c66398C409",
"amount": "50000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
]Provenance
- Seen in the source catalog
- 2026-08-03 16:20Z
- Last indexed by Roundhouse
- 2026-09-24 02:15Z
- Last enriched (probe, favicon, geo)
- 2026-09-15 16:15Z
- x402 version
- 2
- Max timeout
- 300s
- Liveness probe
- HTTP 402
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
Nothing indexed for this service or its provider yet. Not a claim that it is unused — only that we hold no record. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service cryptopulse.saascloud.ai and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=cryptopulse.saascloud.ai' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://cryptopulse.saascloud.ai/api/token-score, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.