A live view of the world-data store behind the Asbente API: its sources, the data they bring in, the knowledge graph built from it, and the ontology that shapes it all.
Checking…
Needs attention: our code or settings failing a source three runs in a row, translations, a late or failed graph run, a stale runner, a disk near its guard, a stuck backlog, or rows looser than their source's rights. Publisher side: sites that are down, unreachable or empty; known, and not counted in the verdict. Runs cut off by a runner restart are not failures.
Sources working through a backlog over several runs, the sites that answered HTTP 429 (too many requests) in the last 7 days, and keys another system also uses. A source with a backlog is polled more often until it is done; we keep to each site's limits.
Requests a site turned away as too many, by source and host.
Sources whose key another system also uses, so the two split one quota. Only the key's name is shown, never its value.
Every request serves a row at the stricter of its own rights and its source's current rights, so a source made stricter is served at its new rights at once. Listed here: current rows still carrying looser rights, until they are re-versioned.
Every source in the registry and how its last fetch went. Refused means the site declined us (robots.txt, 403 or a challenge page); we record that and leave it alone.
| Source | Kind | Cadence | Status | Last run | Last ok | Translation | Note |
|---|
Sources we have decided not to use, or can't use yet, and why: each note quotes the clause when terms are the reason, says what would change it and links the publisher's terms.
Loading the notes…
Rows are Postgres estimates and count every version (the store is append-only). Daily figures cover the last 14 days.
The compute behind the store: the world database on Supabase and the two Fly machines. The database's size is worked out from its settings; Supabase does not report it.
Where the store's things are, what sources reported in the last 7 days, and how many sources cover each country. Drag to turn the globe; hover or tap a mark for its details.
Every kind of thing in the knowledge graph and how the kinds link up, then one real company's neighbourhood. Hover or tap a circle, an arrow or a name.
Loading the graph…
Scroll the diagram sideways to see all of it.
Scroll sideways for the regulators and places.
Source entities are resolved into canonical ones, and rules derive relationships between them. Pairs the resolver is unsure of wait in the review queue.
Relationships a rule could not derive yet, mostly for want of an entity to point at.
Identifiers the last resolve run set aside because they failed a format or check.
For each pair a person decided on the private review page: had the resolver's tier, the tier policy and each agent pass judged it the same way? Counts only.
The kinds of things the store knows about, and the identifiers that tie them together.
Loading the Phase 1 page…