Skip to content
Worlds
Any place on EarthAsk about a place. Get signed satellite facts and a picture of the ground.Streets: London267 street cameras. Each count names its clip, and your browser checks its receipt.Fields: IndiaRead a farm field for 12 months. Nine field tools for your agent.Compliance: EUDRAn area in, a deforestation verdict and a signed receipt out.Platform
How it worksLive statusMeasurement APICompany and contactAgentsVerifyPricingDocs Status
Does it work now? Check it.
Your browser runs each check on this page. We do not report our own health: you measure it. A red line means the part did not answer or did not pass, and the page says which.
Live proof
Your browser checks the signed head of our log once a minute.
IN PROGRESSfirst check
1Fetch the log head…
2SHA-256 of the canonical bytes…
3Ed25519 against the pinned key…
4The log only grew since the stamped head…
Fingerprint: the SHA-256 of the canonical bytes. A change of one byte gives a different pattern.
- signed at
- …
- rate
- shown after the second check
- after emem
- …
- Bitcoin
- no anchor read
Witnesses
Who else saw emem's log? Your browser checks the newest co-signature from a key that a domain vouches for.
IN PROGRESSemem log
1Find the newest vouched co-signature…
2Ed25519 over the BLAKE3 preimage…
3The log only grew since the witness saw it…
- keys
- …
- operator
- …
- coverage
- …
- why
- A second party that saw the same history makes a split view hard: emem cannot show one log to you and another log to someone else. Only an outside operator gives that protection; a co-signature from the same owner shows that the check works.
Checks in progress: 0 of 14
0 pass. Your browser ran every check. The page runs them again each minute.
geo.qa receipts
Verifier and log
GET /api/world-model/verify/log/sth
checking…
Receipt store (server check)
GET /api/world-model/verify/by-cid/ec8aecfebe9b…
checking…
Receipt check in this browser
?include_receipt=true, then SHA-256 + Ed25519 here
checking…
Keys and discovery
Signing key
GET /.well-known/geoqa.json
checking…
Key set (JWKS)
GET /.well-known/jwks.json
checking…
Agent card (A2A)
GET /.well-known/agent-card.json
checking…
Worlds
London World
GET /api/worlds/london
checking…
geo.qa Fields (MCP)
POST /mcp tools/list
checking…
geo.qa core (MCP)
POST /api/mcp tools/list
checking…
Map tiles
GET /api/basemap/dark/3/3/5
checking…
Open memory (emem.dev)
emem responder
GET emem.dev/v1/health
checking…
emem transparency log
GET emem.dev/v1/log/sth
checking…
emem receipt check in this browser
POST emem.dev/v1/recall, then BLAKE3 + Ed25519 here
checking…
Accounts
Account and chat service
GET /api/health
checking…
What a pass proves. The part answered, and where the check names a signature, the signature is valid against a key that this page pinned. A pass does not prove that every reading is right.
Why some checks run here. Two checks rebuild and verify a receipt in your browser, with no help from our server. If those pass, you do not need to trust this page either. Every Bitcoin anchor of the log is in /log-anchors/index.json, and the witness rules are in WITNESS.md.