# Roam Accommodation Transit Endpoint

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

Retrieves detailed accommodation/hotel data by hotel ID, payable per request in USDC via x402 protocol

## Facts

- Endpoint: POST https://402stay.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-accommodation-transit-endpoint-dc448089
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Vvd4Xp9mFFc-alYjwUJks

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-accommodation-transit-endpoint-dc448089 -d '<json body>'
```

Example prompt: Pull up the full details for hotel ID 'HTL-38291' from Roam — I need to see what that property offers before I decide to book.

## When to prefer this

Use this endpoint when you already have a specific hotel ID and need to fetch that property's details without requiring API credentials or subscriptions. Ideal for AI agents operating in a pay-per-use model using USDC via x402, especially when the agent has retrieved hotel IDs from a prior search step and now needs to resolve full property data.

## Known failure modes

- Invalid or unknown hotel ID returns an error or empty data object
- Missing required 'id' field in request body causes validation failure
- Payment failure via x402 (insufficient USDC balance) blocks the request
- Network timeout if the upstream accommodation data source is unavailable
- Malformed JSON body results in a 400-level error

## How this service works

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

## Output

A JSON object with a success boolean and a data object containing hotel/accommodation details for the requested hotel ID. The exact shape of the data object may vary by property but represents structured lodging metadata.

## 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-accommodation-transit-endpoint-dc448089/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 402stay.orbonomy.xyz](https://www.zero.xyz/host/402stay.orbonomy.xyz/llms.txt)