For developers and agents

Your agent can search the web. It can’t yet know the world.

Search returns pages. Globodex returns state: entities, events, and relationships — structured, deduplicated, bound to time and place, with citations your agent can verify and your users can audit.

Search is not state

Five pages about the same thing are not five facts.

Feed an agent raw search results and it re-reads the same event five times, weighs a low-credibility blog like a primary source, and still has to guess what is affected. The layer does that work once, upstream.

What search gives your agent

“oakland port crane maintenance”5 results · 0.4s
C

Port of Oakland announces two-week crane maintenance…

coastal-trade-news.com/story/8842
H

BREAKING: Oakland port cranes going offline for weeks

headline-aggregator.net/feed
B

Crane maintenance window set for August, port says

bayarea-logistics-daily.com/ports
F

Ports face TOTAL disruption this summer, insiders warn

freight-rumors.blog/hot-takes
S

Oakland crane maintenance: what shippers should know

supply-chain-wire.com/west-coast
5 pages · 4 overlapping · 1 low-credibility

What Globodex gives it

Two-week crane maintenance window at Port of Oakland, from Aug 3.

gx-9c04 place:port · port-of-oakland 03 Jul 14:02Z

Three sources corroborate

CBS

One rejected below threshold

freight-rumors.blog

Record complete to L2

Affectsroute:transpacific-westcommodity:arabica

GET /v1/events/gx-9c04

{
  "id": "gx-9c04",
  "what": "Two-week crane maintenance window…",
  "entity": { "id": "port-of-oakland", "type": "place:port" },
  "when": "2026-07-03T14:02Z",
  "sources": [
    { "host": "coastal-trade-news.com", "tier": "primary" },
    { "host": "bayarea-logistics-daily.com", "tier": "primary" },
    { "host": "supply-chain-wire.com", "tier": "secondary" }
  ],
  "rejected": ["freight-rumors.blog"],
  "conformance": "L2",
  "confidence": "high",
  "affects": ["route:transpacific-west", "commodity:arabica"]
}

The shape

The questions your agent will actually ask.

Recent events on an entity, its current resolved state, and the same layer exposed as MCP tools. This is the shape we are converging on with design partners.

01 · Recent events

What just changed at a place you’re watching?

Everything asserted about one resolved entity, with sources and edges already attached.

GET /v1/entities/port-of-oakland/events?since=24h

{
  "entity": { "id": "port-of-oakland", "type": "place:port" },
  "events": [{
    "what": "Two-week crane maintenance window from Aug 3",
    "when": "2026-07-03T14:02Z",
    "sources": [{ "url": "…", "tier": "primary" }],
    "affects": ["route:transpacific-west",
                "commodity:container-freight"],
    "conformance": "L2", "confidence": "high"
  }]
}
02 · Current state

What’s going on with a supplier you depend on?

The current resolved state of one entity — standing guidance, open events, and what it touches.

GET /v1/entities/growers-coop/state

{
  "entity": { "id": "growers-coop", "type": "org:cooperative" },
  "state": {
    "as_of": "2026-07-03T14:02Z",
    "standing": "Revised 2026 harvest guidance down 8%",
    "open_events": 2,
    "affects": ["commodity:arabica", "route:santos-antwerp"],
    "last_changed": "2026-07-02T09:14Z"
  },
  "conformance": "L2", "confidence": "high"
}
03 · MCP tool call

Or the same questions, over MCP.

The layer speaks MCP to any compatible agent. Same structured object back.

tools/call globodex_entity_events

{
  "method": "tools/call",
  "params": {
    "name": "globodex_entity_events",
    "arguments": { "entity": "port-of-oakland", "since": "24h" }
  }
}

# Tools planned:
#   entity lookup · event stream · entity state

Why receipts

Autonomy needs provenance more than people do.

A human analyst sanity-checks a source without thinking about it — the byline, the outlet, the date. An agent has none of those instincts. Whatever it is fed, it acts on, at machine speed, unsupervised.

So the check cannot live in the prompt. It has to live in the data: every fact carries its sources, their tier, and when it was asserted — verification is a field read, not a research task.

The action step does not run until the receipts do.

Verificationfact · gx-9c04

Two-week crane maintenance window scheduled from Aug 3

sourceresolves · tier: primary
corroborationindependent × 3
conformanceL2 · complete record
freshnessasserted 2026-07-03 · still current

Sources kept

Ccoastal-trade-news.comprimary
Bbayarea-logistics-daily.comprimary
Ssupply-chain-wire.comsecondary
act() blocked until verified

Early access

Building an agent that needs to know the world?

We are working with a handful of teams building agents that need live world-state. If that is what you are building, we want to hear what you are up against.

Contact us
No signup requiredRead the specification Limited early accessJoin the Signals waitlist