Why is ucp.travel unreachable?

Our last check failed to connect — DNS lookup, SSL handshake, or HTTP request didn't complete. This could be a temporary outage, a misconfigured certificate, or DNS issues. We'll re-check on the next crawl cycle automatically.

Is the whole store down?

Not necessarily. We only test the /.well-known/ucp endpoint, so it's possible the main site is up while only the manifest endpoint is broken. Subscribe to alerts on this page to be notified the moment ucp.travel recovers.

How was this UCP report for ucp.travel generated?

Our crawler fetches ucp.travel/.well-known/ucp directly, parses the manifest against the official UCP JSON schema, checks robots.txt for AI bot policies, and runs payment-handler validation. No manual review, no opinions — just what the manifest actually says. The check ran 1 day ago.

How often is ucp.travel re-checked?

Every domain in our directory is re-crawled at least every 24 hours. You can also trigger a fresh check from this page at any time, or subscribe to alerts to get notified the moment the status changes — that's how we built the only continuously updated UCP directory on the internet.

Why does this status matter?

Universal Commerce Protocol is the standard AI shopping agents (ChatGPT, Claude, Gemini, Apple Intelligence) use to discover what a store sells, how to add items to a cart, and how to check out. If a store isn't UCP-verified, agents can still scrape it — but they'll be slower, less reliable, and far more likely to fail at checkout. UCP turns a guess into a guarantee.

Back to status

UCP Score

UCP Score for ucp.travel

UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.

✕Unreachable

A99/100

Analyzed Oct 4, 2026 · 2 recommendations ·Custom · v2026-04-08 upgrade

UCP Conformance Score

No score: ucp.travel did not respond

The manifest endpoint timed out or returned a network error. Check uptime and DNS, then re-run the check.

Working

Agent Discovery is solid (100/100).

Blocking

Resolve connectivity / TLS issues: The manifest URL did not respond to the latest check.

Start Here

Resolve connectivity / TLS issues → Move to the latest UCP protocol version

Top Priorities

Resolve connectivity / TLS issues

The manifest URL did not respond to the latest check.

High impact Medium effort

Move to the latest UCP protocol version

Your manifest declares a valid but older protocol version. A newer one is published.

Low impact Low effort

Impact & Effort Matrix

Prioritised recommendations by expected impact and implementation effort

Quick Wins(0)

High impact, low effort

No items

Strategic Investments(1)

High impact, high effort

Resolve connectivity / TLS issues

Incremental Gains(0)

Medium impact & effort

No items

Consider Later(1)

Lower priority

Move to the latest UCP protocol version

How you compare on Custom

Response time benchmarked against 124 Customs we monitor.

fastCustom median 317msslow

Your store

2006ms

Custom percentile

Bottom quartile

Faster than 2% of Custom stores

Cohort range

165–599ms

p25 to p75 (middle half)

Headless / custom stackCustom-built storefronts have the most flexibility but also the most surface area for inconsistency between environments. Run the score in staging before each deploy that touches manifest, schemas, or transports.

Recommendations

All improvements ranked by priority, with evidence and actionable fixes.

Resolve connectivity / TLS issues

High impact Medium effort

The manifest URL did not respond to the latest check.

Why it matters

Connection timeouts, DNS failures, or TLS handshake errors look identical to "store offline" from an agent's perspective. Continuous unreachability removes the store from agent surfaces.

UCP_UNREACHABLE

Move to the latest UCP protocol version

Low impact Low effort

Your manifest declares a valid but older protocol version. A newer one is published.

Why it matters

Older versions stay valid (agents use the version you declare), but newer abilities (embedded checkout, agent payment mandates, linked customer accounts, card authentication, payment terms and store location lookup) only work against the latest version. The manifest itself barely changes: the signing keys move to a root-level "keys" list, and the rest of the update is in what capabilities can say.

Show fix

Set the version to 2026-08-25 and publish your public keys as a root-level "keys" list. The older "signing_keys" field is still accepted, but "keys" is the one every verifier reads.

"ucp": {
  "version": "2026-08-25",
  ...
},
"keys": [ ... ]   // beside "ucp", not inside it

UCP_VERSION_OUTDATED

Full Check Breakdown

Every signal we evaluate, grouped by category.

Functional probes ran Sep 30, 2026.

Agent Discovery6/8 passed

Can AI agents find your store and its UCP manifest?

HTTPSCore

Manifest served over a secure connection.

Manifest URL uses https://

Why it matters
Agents reject non-HTTPS endpoints outright. Signed payloads over HTTP are meaningless because the channel itself is tamperable.
UCP manifest reachableCore

Manifest fetched OK from /.well-known/ucp.

Not assessed: the store did not answer our request, so there was no manifest to read.

Why it matters
Agents start every session by fetching this URL. If it 404s or times out, the store is invisible to agent commerce.
AI bot accessCore

robots.txt allows agent crawlers to fetch the manifest.

No robots.txt detected (default-allow assumed)

Why it matters
Agents respect robots.txt. Even a published manifest gets ignored if the file is disallowed for known agent user-agents.
llms.txtExperimental

Hand-written brief at /llms.txt for AI agents.

Found at /llms.txt

Why it matters
Emerging convention (analogous to robots.txt). Recommendation/discovery agents read it for brand context, return policy, and crawl preferences.
sitemap.xmlCore

XML sitemap published at /sitemap.xml.

Found at /sitemap.xml

Why it matters
Tells agents which pages are canonical and how often they change. Without it, agents fall back to following internal links.
Open Graph tagsCore

OG meta tags on the homepage.

og:title and og:type/url present

Why it matters
OG tags drive how your store unfurls in agent surfaces, Slack, iMessage, and ChatGPT shares.
Organization schema (JSON-LD)Core

Schema.org Organization (or OnlineStore) JSON-LD on homepage.

Organization-typed JSON-LD detected

Why it matters
Gives agents a structured representation of your brand identity — used to verify you are who your manifest claims you are.
Mobile viewport metaCore

Viewport meta tag for mobile rendering.

<meta name="viewport"> present

Why it matters
Mobile agent sessions render in browser sandboxes that respect this. Without it, screenshots taken by agents are unreadable.

UCP Conformance1/2 passed

Does your manifest meet the published spec?

Manifest present for spec validationCore

Conformance checks require a fetchable manifest.

Not assessed: the store did not answer our request, so there was no manifest to read.

Why it matters
Once the manifest is fetchable, this section will show 4+ structural checks (validity, version format, signing keys, validation warnings).
Spec & schema URLs resolve (22)Core

Resolves the 22 spec/schema URLs declared across the manifest to confirm agents can fetch each one.

All 22 URLs resolved.

Why it matters
Spec and schema URLs let agents validate request/response shapes before sending. Broken URLs degrade runtime validation to "best effort" and cause strict agents to refuse the capability entirely.

Capability Coverage1/2 passed

What operations can agents actually perform?

Capabilities visibleCore

Capability checks require a fetchable manifest.

Not assessed: the store did not answer our request, so there was no manifest to read.

Why it matters
Once the manifest is fetchable, this section will show capability count, checkout coverage, transports, and payment handler health.
MCP transport reachableInterop

Live reachability check against https://mcp.ucp.travel/mcp.

tools/list returned a JSON-RPC response in 469ms

Why it matters
A declared transport that does not respond means agents will hit a dead end the moment they try to use the capability — even if the manifest itself looks perfect.

/llms.txt content

The plain-text brief this store publishes to AI agents. Captured on the most recent check.

2.1 KB015ffbee9a42f1fe

mentions UCP

# UCP Travel

> The travel transaction layer for AI agents. Built by Zologic (https://zologic.nl).

UCP Travel enables AI agents to search, authorize, and book travel autonomously — with traveler consent, spending controls, and complete auditability.

## What it does

- Connects any MCP-compatible AI agent (Claude, Gemini, ChatGPT) to live flight and stay inventory
- Enforces traveler spending mandates (AP2 Intent Mandate) before any transaction
- Validates offer availability and price in real time before committing
- Manages async booking state and webhook confirmation
- Provides multi-tenant governance with per-traveler identity and audit trails

## Who it's for

- AI platforms that want to offer travel booking without building supplier integrations
- Travel Management Companies (TMCs) that need AI-powered booking with policy enforcement
- Corporate travel teams that want employees to book autonomously within approved budgets
- Travel operators and OTAs that want to expose inventory to AI agents

## Guides and insights

- Governed AI travel booking: https://ucp.travel/blog/governed-ai-travel-booking
- Price confirmation for AI travel booking: https://ucp.travel/blog/ai-travel-booking-price-confirmation
- Traveler mandates for AI booking: https://ucp.travel/blog/traveler-mandates-for-ai-booking

## Protocol support

- UCP (Universal Commerce Protocol) version 2026-04-08 — https://ucp.travel/.well-known/ucp
- MCP (Model Context Protocol) endpoint — https://mcp.ucp.travel/mcp
- AP2 (Agent Payments Protocol) — travel.ucp.mandate capability
- OAuth 2.0 identity linking — https://api.ucp.travel/.well-known/oauth-authorization-server

## Verified capabilities

- travel.ucp.mandate (only verified implementation globally per UCPChecker)
- travel.ucp.offer (TTL enforced, revalidation required)
- travel.ucp.flight
- travel.ucp.passenger
- dev.ucp.shopping.checkout
- dev.ucp.shopping.ap2_mandate
- dev.ucp.common.identity_linking

## UCPChecker status

Score: 99/100 — https://ucpchecker.com/status/ucp.travel

## Contact

Zologic — https://zologic.nl — [email protected]

View source ↗

Capabilities Detected

UCP capabilities supported by this endpoint
Order Management ✓ Bound	2026-04-08
Travel Ucp Order Extension ✓ Bound	2026-04-08
Checkout ✓ Bound	2026-04-08
Travel Ucp Offer Extension ✓ Bound	2026-04-08
Travel Ucp Flight Extension ✓ Bound	2026-04-08
Travel Ucp Passenger Extension ✓ Bound	2026-04-08
AP2 Mandate Extension ✓ Bound	2026-04-08
Identity Linking ✓ Bound	2026-04-08
Travel Ucp Mandate Extension AP2 Mandate ✓ Bound	2026-04-08

Technical Vitals

Technical details for this UCP endpoint
UCP Status	Unreachable
Endpoint	https://ucp.travel/.well-known/ucp
HTTP Status	—
UCP Version	2026-04-08
Transports	MCP
Last Observed	2026-10-04T19:02:12+00:00
Last Full Index	Sep 30, 2026 2:15 PM UTC

Embed your UCP Score

Drop the live grade into your README, status page, or marketing site. The badge auto-updates as your score changes.

Live preview

Markdown

[![UCP Score for ucp.travel](https://ucpchecker.com/score/ucp.travel/badge.svg)](https://ucpchecker.com/score/ucp.travel)

HTML

<a href="https://ucpchecker.com/score/ucp.travel"><img src="https://ucpchecker.com/score/ucp.travel/badge.svg" alt="UCP Score for ucp.travel"></a>

New · Early access open

Is ucp.travel yours? Claim it & monitor it daily

Prove ownership with one DNS record and the new monitoring dashboard watches it every day — score trends, break alerts, staging drift and a watchlist that benchmarks you against the field. Free while in beta.

Start monitoring →

This score reflects data from the most recent crawl. Run a fresh check to update, or read the methodology to see how each signal is scored.

Save this report

Track ucp.travel's UCP score over time. We'll re-run the full check weekly and email you if the score drops, a capability regresses, or status flips.

Free. One email when something changes — no marketing. Privacy.