# OnchainPulse Narrative-vs-Chain Consistency Check

> OnchainPulse Narrative-vs-Chain Consistency Check is a paid API for AI agents from onchainpulse.theaslangroupllc.com, paid per call via x402, $0.15/call, status unknown (last checked 2026-09-14).

Fetches a token project's website, extracts its public claims about supply, locks, team holdings, taxes, and ownership, and cross-checks each claim against live on-chain data, labeling each as consistent, inconsistent, or unverifiable with exact numbers.

## Facts

- Endpoint: GET https://onchainpulse.theaslangroupllc.com/api/narrative-check
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/onchainpulse-narrative-vs-chain-consistency-check-6a855ea0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hFTLGp5SzWHvbMpS4Uxrq

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability onchainpulse-narrative-vs-chain-consistency-check-6a855ea0
```

Example prompt: Can you check whether the claims on the website for this token contract match what's actually on-chain — I want to see if their stated supply, team holdings, and lock claims are consistent or inconsistent with real blockchain data?

## When to prefer this

Choose this endpoint when you need to fact-check a specific token project's stated narrative against independently observed on-chain data — especially before investing, listing, or publishing research. It is uniquely suited for catching discrepancies between marketing claims and blockchain reality (supply, locks, team holdings, taxes, ownership). Prefer it over general contract-safety scanners when the goal is narrative consistency rather than bytecode vulnerability analysis, and over generic blockchain explorers when you need automated claim extraction from the project's own website rather than manual lookup.

## Known failure modes

- Project website unreachable or returns no extractable claims — claims list empty
- Token contract address not found on specified chain — chain or address error returned
- Chain not supported — must be Solana or one of the 8 supported EVM chains including Base and Robinhood Chain
- On-chain data temporarily unavailable for a specific field — claim marked unverifiable
- Malformed contract address — request validation error
- Website content too ambiguous to extract specific numeric claims — fields marked unverifiable

## How this service works

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.

## Output

A structured list of each checkable public claim extracted from the project's website (e.g. 'max supply: 1,000,000,000'), each labeled as consistent, inconsistent, or unverifiable, alongside the exact on-chain figure observed. Also includes a pre-launch imposter signal indicating whether the site is live and whether trading activity exists on-chain despite a dead or absent site. No scores or investment advice are returned — only factual comparisons.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "url",
  "address"
 ],
 "properties": {
  "url": {
   "type": "string",
   "description": "Project's public website URL or domain"
  },
  "chain": {
   "type": "string",
   "description": "solana or one of: base, ethereum, bsc, arbitrum, polygon, optimism, avalanche, robinhood (default base)"
  },
  "address": {
   "type": "string",
   "description": "Token contract address (0x… EVM) or mint (base58 Solana)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "site": {
   "url": "https://example.xyz",
   "live": true,
   "title": "Example Protocol"
  },
  "chain": "base",
  "claims": [
   {
    "claim": "Liquidity locked for 12 months",
    "topic": "liquidity",
    "status": "inconsistent",
    "on_chain_observation": "LP lock/burn share observed at 4.2% — locked share does not match a full-lock claim"
   },
   {
    "claim": "1,000,000,000 total supply",
    "topic": "supply",
    "status": "consistent",
    "on_chain_observation": "On-chain total supply reads 1,000,000,000"
   },
   {
    "claim": "Team tokens vested for 2 years",
    "topic": "team_holdings",
    "status": "unverifiable_on_chain",
    "on_chain_observation": "Provided data cannot identify team wallets or vesting contracts"
   }
  ],
  "counts": {
   "checked": 9,
   "consistent": 5,
   "inconsistent": 1,
   "unverifiable_on_chain": 3
  },
  "address": "0x…",
  "explorer": "https://basescan.org/token/0x…",
  "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.",
  "imposter_screen": {
   "site_live": true,
   "token_trading": true,
   "socials_on_site": [
    "https://x.com/example"
   ],
   "trading_while_site_dead": false
  },
  "notable_absences": [
   "No contract address listed on the site"
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onchainpulse-narrative-vs-chain-consistency-check-6a855ea0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from onchainpulse.theaslangroupllc.com](https://www.zero.xyz/host/onchainpulse.theaslangroupllc.com/llms.txt)