Record entry · Crypto DEFI

Polymarket

Added 17 Aug 2026Mentions 27Sources 14Days of coverage 10

Why this name is on the record

Polymarket was added automatically on 17 Aug 2026 after 27 mentions across 14 sources over 10 days. 56% of that coverage came from a single subject area.

Who Polymarket moves with

Names most often reported alongside it; bigger circles and heavier lines mean more shared documents. A dashed circle has no page of its own yet.

KalshiCryptoBitcoinCFTCAISenateEthereumFederal ReserveDeFi
  • Kalshi · 187 shared documents
  • Crypto · 182 shared documents
  • Bitcoin · 118 shared documents
  • CFTC · 118 shared documents
  • AI · 85 shared documents
  • Senate · 68 shared documents
  • Ethereum · 65 shared documents
  • Federal Reserve · 65 shared documents
  • DeFi · 57 shared documents
  • Trading Volume · 57 shared documents · no page of its own yet

For developers

GET https://sigb.ai/api/registry?slug=polymarket

{
  "slug": "polymarket",
  "state": "active",
  "detail": {
    "state": "active",
    "source": "ontology",
    "label": "polymarket",
    "promotedAt": "2026-08-17",
    "category": "crypto_defi",
    "evidence": {
      "mentions": 27,
      "sources": 14,
      "days": 10,
      "concentration": 0.556
    }
  }
}

The record behind this page, as data. The live response also carries the registry date and version.

Walk the record from Polymarket

Open where it comes from, follow a claim or a related name, and use the trail to come back. Every step says what it is, how it stands and when. Machines read the same record.

Polymarket

Entity.

Evidence
364 documents · 56 separate publishers · a mention shows the name is in use, not that any claim about it is true
Standing
A name from our starting list; its record is kept up to date automatically from coverage
Time
first seen 3 Sept 2026, last seen 6 Oct 2026
Measured
34% of mentions say something specific about it; the rest only name it
As of
6 Oct 2026
11 links from here

Who it moves with: the 10 names are in the map above.

What is claimed about it (1)

  • Reported by two: Reported by two sources that did not copy each other.

Situations it is named in (0)

none on file at this cutoff

For machines: this record as JSON

Watch this