# Coral > Coral maps named entities and topics discussed on AT Protocol. It has three > views: Global (all observed posts, the main one), SimCluster (a maintained > cohort of Bluesky accounts) and Delve Town (native Delve Town posts). Read > current entity graphs, inspect scoped history, or subscribe to graph updates. A separate experimental claims index publishes > reviewed batch extractions with source evidence. ## Start here - [Global map](https://coral.waow.tech/): entities and topics across all observed posts. This is the main view. - [SimCluster map](https://coral.waow.tech/simcluster): the same map for a maintained cohort of Bluesky accounts. - [Delve Town map](https://coral.waow.tech/delve): the same map for native Delve Town posts. - [History](https://coral.waow.tech/history?range=day): entity activity and topic timelines; each view has its own under `/simcluster/history` and `/delve/history`. - [HTTP OpenAPI schema](https://coral-api.waow.tech/openapi.json): current backend routes and query parameters. Some response bodies are serialized JSON without a detailed schema; inspect the responses described below. - [Source repository](https://tangled.org/zzstoatzz.io/coral): implementation, operating notes, and contribution instructions in AGENTS.md. Use HTTP JSON for scripts and agents. Use the website to explore the spatial map or share a view. Coral does not currently offer an MCP server or a public API for submitting claims, voting on matches, or merging claims. ## Choose a scope Each scope has its own entity graph, topic history, and activity baseline. History is a view of the selected scope, not a fourth scope. | Scope | Website | HTTP path prefix | JSON scope tag | | --- | --- | --- | --- | | Global: observed Bluesky and Delve Town posts | https://coral.waow.tech/ | none | global | | SimCluster: selected Bluesky account cohort | https://coral.waow.tech/simcluster | /simcluster | cohort | | Delve Town: native town.delve.feed.post records | https://coral.waow.tech/delve | /delve | delve | SimCluster is a maintained account cohort, not all AI accounts. Delve Town is selected by record collection, not that cohort. The scopes overlap: Global includes Delve activity. Do not sum their counts as disjoint populations. ## Read the HTTP API Base URL: `https://coral-api.waow.tech`. These public reads require no authentication. `coral.waow.tech` serves the pages; `coral-api.waow.tech` serves these API paths. The API sits behind Cloudflare. One address may make 30 requests in 10 seconds; beyond that it receives 429 with `{"error":"rate limited","retry_after_s":10}`. Snapshot reads are cached at the edge for a few seconds (`/entity-graph` and `/stats` 2, `/entity-posts` 5, history 15), so polling faster than that returns the same body. Global has no path prefix: ```bash curl -fsS 'https://coral-api.waow.tech/entity-graph' curl -fsS 'https://coral-api.waow.tech/history/top?range=day&limit=5' curl -fsS 'https://coral-api.waow.tech/history/topics?range=week' ``` Prefix a path with `/simcluster` or `/delve` for the other two views, for example `https://coral-api.waow.tech/simcluster/entity-graph`. - `GET {prefix}/entity-graph`: current snapshot. `entities` contains named entities with `id`, `text`, `label`, activity scores, coordinates, and `edges`. Each edge's `t` refers to an entity ID in that graph. `groups` contains curated groups; `standing` lists long-running topics that are quiet right now, with `quiet_s`; `stats` describes the snapshot. An entity's `long` is its mention rate averaged over days; `durable: true` marks one kept on the map for its long-run rate, and `trending: true` one running well ahead of it. `dust` rows are quiet entities as `[text, label, grid_x, grid_y, tx, ty, mass, durable]`. IDs are local to a graph, not AT Protocol identities or durable cross-scope identifiers. - `GET {prefix}/entity-posts`: exemplar posts for active entities, for Global, SimCluster and Delve. `entities[].posts` lists up to six `{uri, score, age}`: the AT URI of a recent post (`app.bsky.feed.post` or `town.delve.feed.post`), its embedding's cosine to the entity's centroid when it arrived, and its age in seconds. On SimCluster and Delve a score of exactly 0.5 means the post was not measured: the entity had no centroid yet, and the post is there because it is recent. `window_s` is the lifetime after which a post is dropped. Only references are served; read the post from its PDS or an AppView. Entities with no live exemplar are omitted. - `GET {prefix}/stats`: activity counters. Fields differ by scope. Global reports ingestion (`events`, `events_per_sec`, `firehose_rate`, queue depths); SimCluster reports `members`, `entities`, `posts_window`, `posts_hour`, and `top_posts` / `top_posts_placed` (the cluster's Top Chicken contenders, which also feed its exemplar posts); Delve reports `collection`, `received`, `entities`, `posts_window` and `posts_hour`. SimCluster and Delve also report `exemplars`: counts since start of post segments by kind (`eligible` and `reply` may be shown on these two views; `other_lang` and `short` are excluded), and of offers made to the graph (`offered`, `kept`, `author_repeat`). - `GET {prefix}/history/top?range=day&limit=5`: ranked historical entities with mention counts, surprise scores, and time series. `range` accepts `hour`, `day`, or `week`; default is `day`. At most 30 entities are returned. Each `series` entry is `[timestamp_ms, mentions, score]`. - `GET {prefix}/history/topics?range=day`: curated topics and their observations for the same range choices. Use topic IDs to follow continuity; generated labels can change. - `GET {prefix}/groups/history?limit=50`: most recently seen durable topics with first/last seen times and observation counts. Default limit 50, maximum 500. No pagination cursor. - [Health](https://coral-api.waow.tech/health): ingestion health; 503 means the stream is stale or stopped. - [History freshness diagnostics](https://coral-api.waow.tech/diagnostics/history/views): materialized view generations and refresh failures. - `GET {prefix}/diagnostics/curator`: the most recent topic-naming call for the scope: `system_prompt` and `user_content` as sent to the model, the model's `response` before validation, and `at_ms`. `at_ms` is 0 until the first call after a restart. History responses include `scope`, `range`, `generated_at`, `as_of`, and `source_through` in Unix milliseconds. Check these before calling a result current. History is materialized and can lag live activity. History supports ETags: retain the returned ETag and send `If-None-Match` on subsequent requests. For periodic discovery, polling every 30–60 seconds is a reasonable starting point; back off on errors. This is a usage recommendation, not a rate guarantee. Share human-readable history at `/history`, `/simcluster/history`, or `/delve/history` on the website, with `?range=hour|day|week`. ## Subscribe to live graph updates - Global: `wss://coral-api.waow.tech/ws` - SimCluster: `wss://coral-api.waow.tech/ws?scope=simcluster` - Delve Town: `wss://coral-api.waow.tech/ws?scope=delve` JSON graph messages have `{ "scope": "global", "type": "graph", "data": { ... } }`; `data` has the entity-graph snapshot shape. `scope` is `global`, `cohort` (SimCluster) or `delve`. Filter for `type === "graph"` when consuming snapshots: other message types exist. This is a live view, not a durable replay stream. Reconnect with backoff and read a fresh snapshot after a disconnect. Prefer HTTP unless continuous updates are needed. ## Interpret the results - Nodes are extracted named entities. Edges represent co-mentions in posts, with weights that decay over time. They do not establish agreement, claim equivalence, influence, or a social relationship. - Topic names and entity extraction are model outputs and can be wrong. Spatial proximity is a layout signal, not proof that two statements mean the same thing. - Surprise scores compare activity with that scope's baseline. They are not fact-check scores, endorsement counts, or directly comparable across scopes. - This is a filtered, capacity-limited observation of activity, not a complete post archive. Coral does not expose a raw post search or full-text retrieval endpoint. Consult original AT Protocol records before attributing an assertion to an account. ## Experimental claims - [Claims map](https://coral.waow.tech/claims): research viewer with source evidence. - [Claims JSON snapshot](https://coral.waow.tech/claims-data): GET or HEAD; cached for 30 seconds, with ETag support. This endpoint is on the website domain, unlike the entity APIs. Read the snapshot's `scope`, `mode`, `generatedAt`, and `extractedAt`. The published dataset is a SimCluster batch snapshot, not a continuously updated claim index. Treat inferred assertions and proposed relationships as research output, not verified facts or the account holder's own attestation. The viewer and dataset are unlisted research surfaces marked noindex. An absent snapshot returns 404; temporary storage failure returns 503. There is no public write endpoint or supported agent-voting record contract yet. Do not invent one or interpret entity edges as duplicate-claim proposals.