Travel connector concepts
The prototype inventory includes search, offer, hold, order, cancellation, provider-proxy, and payment-recovery ideas. Tool names and local tests do not prove that airline penalties, duplicate-booking recovery, ticket delivery, refunds, personal-data handling, exchange rates, or provider terms are safe.
Stele does not book travel, pay a provider, hold a wallet, or proxy provider credentials. Its hosted public-web preview is a services surface with public discovery and a private provider-listing draft Studio. Its live hosted MCP exposes a different nonbinding booking-approval draft tool, but production currently has 0 published services, so no successful booking-approval draft can be created. Provider-listing drafts remain unpublished and unavailable to MCP search. Provider contact, booking, payment, escrow, disputes, reviews, hosted signing, and agent-wallet execution remain disabled.
Safe scope today
Section titled “Safe scope today”An agent may help a user compare public information. The user must verify the itinerary and complete any booking directly through a provider’s own human checkout under that provider’s terms. Do not invoke prototype booking or payment tools.
Release evidence required
Section titled “Release evidence required”A future supported connector needs a versioned public contract, provider sandbox certification, PII threat model, explicit review UI, idempotency and recovery tests, durable receipts, cancellation/refund reconciliation, independent security review, and a separately approved production release.