Narrative Check
by OnchainPulse in Onchain & crypto
Narrative-vs-chain consistency check — the missing layer of token due diligence: fetches the project's own website, extracts its checkable public claims (supply, locks, team holdings, taxes, ownership) and marks each one consistent / inconsistent / unverifiable against independently observed on-chain data, with the exact numbers. Pre-launch-imposter screen included (site live? trading while site dead?). Solana + 8 EVM chains incl. Base & Robinhood Chain. Facts only — no scores, no advice.
https://onchainpulse.theaslangroupllc.com/api/narrative-check- Price
- $0.15
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 6 h ago, next any minute now
Reliability
Latest check failed 6 h ago: Amount "0.15" is not in atomic token units
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://onchainpulse.theaslangroupllc.com/api/narrative-check
Each call costs $0.15 in USDC on Polygon, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://onchainpulse.theaslangroupllc.com/api/narrative-check?address=0x532f27101965dd16442E59d40670FaF5eBB142E4&chain=base&url=brett.xyzParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
address | string | Yes | Token contract address (0x… EVM) or mint (base58 Solana) |
chain | string | No | solana or one of: base, ethereum, bsc, arbitrum, polygon, optimism, avalanche, robinhood (default base) |
url | string | Yes | Project's public website URL or domain |
Example response
The provider's example. We can't check it without paying.
Example response, 48 lines
{
"address": "0x…",
"chain": "base",
"claims": [
{
"claim": "Liquidity locked for 12 months",
"on_chain_observation": "LP lock/burn share observed at 4.2% — locked share does not match a full-lock claim",
"status": "inconsistent",
"topic": "liquidity"
},
{
"claim": "1,000,000,000 total supply",
"on_chain_observation": "On-chain total supply reads 1,000,000,000",
"status": "consistent",
"topic": "supply"
},
{
"claim": "Team tokens vested for 2 years",
"on_chain_observation": "Provided data cannot identify team wallets or vesting contracts",
"status": "unverifiable_on_chain",
"topic": "team_holdings"
}
],
"counts": {
"checked": 9,
"consistent": 5,
"inconsistent": 1,
"unverifiable_on_chain": 3
},
"disclaimer": "Point-in-time consistency observations between a project's public statements and observable on-chain data. \"Not supported by on-chain data\" describes a data mismatch at the time of the check — it is not an accusation of wrongdoing or intent. Not financial, legal or investment advice; never a recommendation to buy, sell or avoid any asset.",
"explorer": "https://basescan.org/token/0x…",
"imposter_screen": {
"site_live": true,
"socials_on_site": [
"https://x.com/example"
],
"token_trading": true,
"trading_while_site_dead": false
},
"notable_absences": [
"No contract address listed on the site"
],
"site": {
"live": true,
"title": "Example Protocol",
"url": "https://example.xyz"
}
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.15.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://onchainpulse.theaslangroupllc.com/api/narrative-check?address=0x532f27101965dd16442E59d40670FaF5eBB142E4&chain=base&url=brett.xyz'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://onchainpulse.theaslangroupllc.com/api/narrative-check?address=0x532f27101965dd16442E59d40670FaF5eBB142E4&chain=base&url=brett.xyz' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.15 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.15" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.15 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fonchainpulse.theaslangroupllc.com%2Fapi%2Fnarrative-check
const res = await pay("https://onchainpulse.theaslangroupllc.com/api/narrative-check?address=0x532f27101965dd16442E59d40670FaF5eBB142E4&chain=base&url=brett.xyz");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.15 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.15"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://onchainpulse.theaslangroupllc.com/api/narrative-check?address=0x532f27101965dd16442E59d40670FaF5eBB142E4&chain=base&url=brett.xyz")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 6 h ago | Amount "0.15" is not in atomic token units | 402 | 207 ms | $0.15 |
| 11 h ago | Amount "0.15" is not in atomic token units | 402 | 323 ms | $0.15 |
| 17 h ago | Amount "0.15" is not in atomic token units | 402 | 304 ms | $0.15 |
| 23 h ago | Amount "0.15" is not in atomic token units | 402 | 307 ms | $0.15 |
| 28 h ago | Amount "0.15" is not in atomic token units | 402 | 188 ms | $0.15 |
Show 5 older checks
| 33 h ago | Amount "0.15" is not in atomic token units | 402 | 279 ms | $0.15 |
| 39 h ago | Amount "0.15" is not in atomic token units | 402 | 376 ms | $0.15 |
| 44 h ago | Amount "0.15" is not in atomic token units | 402 | 206 ms | $0.15 |
| 2 days ago | Amount "0.15" is not in atomic token units | 402 | 171 ms | $0.15 |
| 2 days ago | Amount "0.15" is not in atomic token units | 402 | 189 ms | $0.15 |