TravelHub
Your stay at Hoshi Shinjuku is confirmed
BK-TYO-78329 · 20–24 Jun · Premium King · USD 756 paid
now
TravelHub
An enterprise travel agent will book a hotel on Kenji's behalf, end to end, without ever holding a credential it could lose.
The starting point
The agent carries its rules with it.
A Smart Verifiable Credential, issued by Acme Corp through Agent Auth, defines what this agent is allowed to do.
← see VC in panel 1
Map
Stays
Filters
Tokyo · 20–24 Jun · 1 guest
128 stays · Tokyo
Map
Stays
Filters
Shinjuku · 20–24 Jun
Shinjuku
All ratings
Any price
5 stays · Shinjuku
Map
Stays
Filters
Shinjuku
4★ min
≤USD 200
Non-smoking
VC constraints applied · 1 selected
Back
Hoshi Shinjuku
♡
Hoshi Shinjuku Residences
★ 4.8
·
4-star
·
1,284 reviews
Available rooms · 20–24 Jun
Premium King selected · USD 189 / night · 4 nights · USD 756 total
Back
Checkout
Guest information
First nameKenji
Last nameTanaka
Date of birth{user.dob}
Nationality{user.nationality}
Passport details · Sensitive
Passport number{user.passport.number}
Expiry{user.passport.expiry}
Payment · Sensitive
Card number{user.default_card.number}
Expiry{user.default_card.expiry}
CVV{user.default_card.cvv}
Cardholder{user.default_card.name}
◆ Placeholders, not values. Sensitive fields stay as references. Real values live in Enterprise Private Storage and are resolved inside the TEE.
Total: USD 756
Handoff to T3 Network
Agent cannot complete this step alone
Confirming the booking requires your passport and credit card. The TravelOps Agent is not permitted to hold or request these values. It hands the request to T3 Network, which resolves the credentials inside a hardware-attested enclave.
From
TravelOps Agent
did:t3:...travelops-001
execute
→
To
T3 Network
SGP endpoint · TEE
Placeholder refs (T3N resolves these)
5 fields
{user.default_card}
payment
{user.passport.number}
identity
{user.passport.expiry}
identity
{user.dob}
identity
{user.nationality}
identity
Smart VC attached as proof of authorisation
Awaiting T3N execution…
Booking
Done
✓
Booking confirmed
The agent received a minimal receipt: payment id, booking reference, status, and audit root. No PII.
Booking reference
BK-TYO-78329
see full receipt in panel 2 →
Booking
Done
✓
Confirmation sent
The booking platform emails confirmation to the registered user address. The agent has no email access.
Trip details
Share
Hoshi Shinjuku Residences
Your stay
Check-inSat, 20 Jun
Check-outWed, 24 Jun
RoomPremium King
Booking refBK-TYO-78329
Total paidUSD 756
From the user's view, that's the whole story.
next: how did that actually work? →
next: how did that actually work? →
Behind the scenes
Inside T3 Network.
Same flow, different vantage point.
✓
The full picture
Enterprise Claw turns "an agent doing something" into "an agent doing something you can prove, constrain, and audit".
Agent never saw
Passport · DOB · Nationality
Card number · CVV · Cardholder
User's email · Booking confirmation
Card number · CVV · Cardholder
User's email · Booking confirmation
see panels 1 + 2 for the full audit trail
Inside T3 Network.
The request crosses into a hardware-attested TEE. Placeholders are resolved against Enterprise Private Storage. The transaction executes. An audit entry is sealed. None of this is visible from the agent runtime.
Remote attestation verified
Incoming request
action: "travel.hotel.book"
amount: 75600
card: {user.default_card}
passport: {user.passport.*}
dob: {user.dob}
nationality: {user.nationality}
amount: 75600
card: {user.default_card}
passport: {user.passport.*}
dob: {user.dob}
nationality: {user.nationality}
⌬
Enterprise Private Storage
SG-residency · enforced at storage layer
TEE Node · WASM Runtime
sealed
Payment API call
POST /v1/charges
status: "succeeded"
id: "pi_3OQzXR7..."
status: "succeeded"
id: "pi_3OQzXR7..."
Merkle audit entry
block #1,284,701
0x9c4f1a02e8f33b7d9b4a6...e21a
Receipt to agent
only: payment_id, booking_ref, status, audit_root
T3N · TEE-attested confidential compute
nothing on this screen is visible to the agent runtime