# Roam Hotel Details Lookup

> Roam Hotel Details Lookup is a paid API for AI agents from 402roam.orbonomy.xyz, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-13).

Retrieves detailed accommodation data for a specific hotel by its ID, payable per-request in USDC via x402 protocol

## Facts

- Endpoint: POST https://402roam.orbonomy.xyz/api/transit
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/roam-hotel-details-lookup-99de2968
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_S2bEjUOzBouoM2IsSs76j

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability roam-hotel-details-lookup-99de2968 -d '<json body>'
```

Example prompt: Can you pull up the details for hotel ID 'htl_abc123xyz' on Roam so I can see what that property offers?

## When to prefer this

Use this endpoint when you already have a specific hotel ID and need to retrieve its full details. This is ideal after a search step that returned hotel IDs, or when a hotel ID is known from a prior session. It requires no API key or subscription — just pay $0.03 USDC per call via the x402 protocol, making it suitable for lightweight, on-demand agent workflows.

## Known failure modes

- Invalid or unknown hotel ID returns an error or empty data object
- Missing required 'id' field causes a 400-level validation error
- Payment failure via x402 results in a 402 Payment Required response
- Service downtime returns 5xx errors
- Malformed request body returns a parsing error

## How this service works

Accommodation search for AI agents. No auth, no subscriptions. Pay per request in USDC via x402.

## Output

Returns a JSON object with a success boolean and a data object containing accommodation details for the requested hotel ID. The specific fields within data depend on what the hotel record contains (name, location, amenities, rates, etc.).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "id"
 ],
 "properties": {
  "id": {
   "type": "string",
   "description": "Hotel ID"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "success",
  "data"
 ],
 "properties": {
  "data": {
   "type": "object"
  },
  "success": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/roam-hotel-details-lookup-99de2968/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 402roam.orbonomy.xyz](https://www.zero.xyz/host/402roam.orbonomy.xyz/llms.txt)