What happened: how the Booking.com X-ray was made

Step 1 of 6

1. The ask

On 7 November 2026 at 21:16 UTC, xray@web-summit.dinis typed one line into the search tool (admin/tools/xray-search.mjs): "Booking.com AI Trip Planner and AI agents", as a company. It was not typed at the booth: that path is still being built (WS-194).

The search tool is the orchestrator. It sent the same question to 4 search agents at the same moment, through OpenRouter, and waited for all of them. Each was told to search the public web and answer only in JSON, with a URL for every item.

1. Perplexity search perplexity/sonar
2. OpenAI search openai/gpt-5.4-nano:online
3. Gemini search google/gemini-3.1-flash-lite:online
4. OpenRouter web search anthropic/claude-haiku-5.5

You are a research agent for RiskMandate X-ray. Subject (a company): "Booking.com AI Trip Planner and AI agents".
Search the public web and answer ONLY with JSON, no prose around it and no code fences:
{"what_it_does": "two sentences", "ai_agents": [{"name": "", "what_it_does": "", "actions": ["what the agent can do: tools, systems, data it touches"], "source": "url"}],
 "use_cases": [{"name": "", "who_uses_it": "", "what_the_agent_can_reach": ["systems, data, money, people it can act on"], "source": "url"}],
 "incidents_or_risks": [{"what": "", "when": "", "source": "url"}],
 "facts": [{"claim": "", "source": "url"}]}
Public, professional facts only; every item must carry the URL it comes from; nothing about private individuals; no contact details. If you find nothing for a field, give an empty list.

Step 2 of 6

2. Each search agent's call

Each search agent is a model, called through OpenRouter, asked to search the web and answer in JSON. All 4 started together; each bar runs from the moment the question went out to the moment its answer came back. The whole fan-out took 24.8 s, the time of the slowest.

"Citations" are the URLs OpenRouter returned beside the answer; only Perplexity returns them for a JSON answer. "Named in its answer" are the URLs inside the JSON. Both are leads: nothing is taken from them until a source is read. "Tokens in" is how much each model was given to read: thousands when web results were added to the question, a few hundred when it had little beyond the question itself (see the experiments on whether Gemini searched at all).

Step 3 of 6

3. From claims to facts

What a model says is a lead. Only what we read on its source reaches the page.

The reading agent turned the 4 answers into 48 leads, each tagged with the model that said it, and looked for each one on a source it read. 30 confirmed, 1 not found, 17 unverified.

confirmednot foundunverified

• Confirmed: a source we read says it.
• Not found: we read the source, or looked for one, and it does not say it.
• Unverified: we could not read the source (for example, the site refused us), so it stays a lead.

What did not hold up, and why

Step 4 of 6

4. The reading agent

A reading agent: a Claude Code sub-agent of xray@web-summit.dinis, one per subject. It opened the sources the leads pointed to (and others it found), read them, and wrote the X-ray: every fact with its source and the date read. It finished at 7 November 2026 at 21:26 UTC.

The sources, by kind

Step 5 of 6

5. The review

xray@web-summit.dinis reviewed the X-ray on 2026-11-07 before it was published. What the review changed or checked:

1. Kept the two phishing waves through guest messaging, labelled as not involving the AI agents; removed three business risks and audit notes.

Step 6 of 6

6. What it cost

The search cost $0.1243 in all, as OpenRouter reported it for each call.

Perplexity search: $0.0063 (5%)OpenAI search: $0.0343 (28%)Gemini search: $0.0578 (47%)OpenRouter web search: $0.0258 (21%)

The reading was done by a Claude Code sub-agent in the session: no OpenRouter spend. Its cost is not recorded in dollars, only as about 169 thousand tokens.

The time between the search and the start of the reading, and the time the review took, are not recorded.