Public Beta API

Understand the product first, then plug into a structured Web3 intelligence feed.

Web3 Tools Intel packages risk events, structured signals, entity intelligence, history snapshots, and source freshness into stable JSON endpoints. It is built for watchlists, research flows, light monitoring, and agent-driven workflows that would otherwise require scraping or manual page checks. You can also attach an optional beta key through x-api-key to make usage attributable without waiting for a full paid plan layer.

Open API catalog Open OpenAPI spec Request beta access

Version v1 Snapshot 2026-03-12 8 signals 3 risk events

Start Here

What this product does today

Surface risk-sensitive events that matter for wallets, security tools, and analytics products.
Turn raw observations into structured signals with affected entities and priority context.
Persist dated snapshots so you can reason about continuity instead of only reading the latest page state.
Expose source-health metadata so users can judge freshness before trusting the feed.

Support

What is supported and what is not

Supported now

Public JSON endpoints, optional beta API keys, request-beta intake, entities, signals, risk feed, full intel bundle, history snapshots, source-health visibility, and OpenAPI discovery.

Not fully shipped yet

Self-serve API key issuance, enforced plan limits, webhook delivery, and team workflow surfaces are still next-stage capabilities.

Beta Request Form

Request a beta key without leaving the page.

Choose Your Path

How you should use the beta depends on what you need

Just trying it

Start with the catalog, then look at one payload endpoint and one quality endpoint.

/api/v1/catalog.json → /api/v1/signals.json → /api/v1/source-health.json

Evaluating product quality

Check coverage, freshness, and continuity before judging the payload.

/api/v1/summary.json → /api/v1/source-health.json → /api/v1/history.json

Building monitoring

Use risk events for direct alerts and signals for prioritization logic.

/api/v1/risk-feed.json + /api/v1/signals.json

Doing structured research

Use entities for tracked tools and intel bundle for a full local sync.

/api/v1/entities.json + /api/v1/intel.json

Quickstart

1. Inspect the catalog

curl https://web3-tools-intel.pages.dev/api/v1/catalog.json

Quickstart

2. Read live signals

curl https://web3-tools-intel.pages.dev/api/v1/signals.json

Quickstart

3. Check continuity

curl https://web3-tools-intel.pages.dev/api/v1/history.json

Beta Key

Tag requests with an optional key

curl https://web3-tools-intel.pages.dev/api/v1/signals.json \
  -H 'x-api-key: YOUR_BETA_KEY'

Current behavior

The API is still public beta, so the key is optional. Right now it is used to attribute usage and support beta cohorts, not to hard-block anonymous reads.

Beta Access

Request a tracked beta workflow

curl https://web3-tools-intel.pages.dev/api/v1/request-beta \
  -X POST \
  -H 'content-type: application/json' \
  -d '{"email":"you@example.com","useCase":"Need signal and history access for monitoring"}'

Codex Skill

Want guided onboarding instead of raw docs?

If you are using Codex, ask it to use the web3-tools-intel-api skill. The skill introduces the product, identifies your scenario, tells you what the beta supports today, and then recommends the smallest useful endpoint flow.

Use the web3-tools-intel-api skill and help me evaluate whether this API fits a monitoring workflow.

Endpoints

Current public beta surfaces

Summary /api/v1/summary.json

Snapshot counts and high-level coverage metadata.

Entities /api/v1/entities.json

Tracked entities enriched with signal counts.

Signals /api/v1/signals.json

Structured signal feed with scorecards and affected entities.

Risk Feed /api/v1/risk-feed.json

Risk-event stream for trust-sensitive monitoring and alerts.

Intel Bundle /api/v1/intel.json

Full bundle of signals, distribution plans, and monetization decisions.

OpenAPI /api/v1/openapi.json

Machine-readable API specification for the public beta.

History /api/v1/history.json

Historical snapshot timeline for counts, changes, and top signals.

Source Health /api/v1/source-health.json

Observed source freshness and evidence coverage for the current collection layer.

Request Beta /api/v1/request-beta

Submit your email and use case to request a beta key or higher limits.

Schema

Signal object example

{
  "id": "b8a5ca0ec260b2dbff6fa9eab94497bab3a23c36c8bd55e0d9977a9881072b97",
  "lane": "risk",
  "title": "MetaMask: Official support guidance continues to emphasize spoofing scams and support impersonation risk.",
  "thesis": "The largest EVM wallet still needs explicit user education around fake support and spoofed brand flows, which keeps trust and anti-phishing content highly valuable.",
  "affectedEntities": [
    "metamask",
    "phantom",
    "pocket-universe"
  ],
  "evidenceIds": [
    "https://support.metamask.io/stay-safe/protect-yourself/social-engineering/spoofing-scams/"
  ],
  "scores": {
    "actionability": 4,
    "novelty": 4,
    "monetizability": 4,
    "credibility": 5,
    "freshness": 5,
    "composite": 4.2
  },
  "status": "validated",
  "recommendedActions": [
    "refresh entity page for metamask",
    "refresh compare surfaces for metamask"
  ],
  "contentHooks": [
    "Official support guidance continues to emphasize spoofing scams and support impersonation risk."
  ],
  "seoHooks": [
    "MetaMask update",
    "MetaMask alternatives"
  ],
  "productHooks": [
    "update trust note for metamask"
  ]
}

Schema

Risk event example

{
  "slug": "metamask-spoofing-scams-guidance",
  "entitySlug": "metamask",
  "title": "Spoofing scams guidance remains active",
  "severity": "high",
  "eventDate": "2026-03-12",
  "summary": "Fraudsters can impersonate MetaMask to get your SRP or password. Don't fall for it!",
  "sourceName": "MetaMask Help Center",
  "sourceUrl": "https://support.metamask.io/stay-safe/protect-yourself/social-engineering/spoofing-scams/",
  "evidence": [
    {
      "sourceName": "MetaMask Help Center",
      "sourceUrl": "https://support.metamask.io/stay-safe/protect-yourself/social-engineering/spoofing-scams/",
      "confidence": 0.9,
      "observedAt": "2026-03-12"
    }
  ]
}

Roadmap

What moves this from beta to paid product

Now

Public beta feed, versioned paths, schema visibility, and developer docs.

Next

Historical snapshots, API key auth, higher rate limits, and webhook-style alert delivery.

Later

Saved watchlists, filtering by segment, and team-oriented usage layers.

Release tracking

Follow beta changes at /developers/changelog/.