# Orbonomy Accommodation Compare

> Orbonomy Accommodation Compare is a paid API for AI agents from main.orbonomy.xyz, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-15).

Compares accommodation options for a given location, date range, and budget via a pay-per-call API

## Facts

- Endpoint: POST https://main.orbonomy.xyz/api/accommodation/compare
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/orbonomy-accommodation-compare-c89a59e5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZWBX_cDr3CeUaPmzsclgD

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 orbonomy-accommodation-compare-c89a59e5 -d '<json body>'
```

Example prompt: Can you compare accommodation options in Paris from July 10 to July 14 within a $200 budget and show me what's available?

## When to prefer this

Use this endpoint when you need to compare multiple accommodation options programmatically for a specific location and date range within a budget constraint, especially in a pay-per-call context using the x402 protocol. Prefer it when you want a single API call to aggregate and compare lodging options rather than querying individual hotel booking APIs.

## Known failure modes

- Missing required fields (location, checkin, checkout, budget) returns a validation error
- Invalid date formats may cause parsing failures
- No results found for the given location or budget range
- Payment failure via x402 protocol returns 402 Payment Required
- Service unavailability returns 5xx error

## How this service works

50+ pay-per-call API endpoints across accommodation, AI, content, fact-checking, and data services. Powered by x402 protocol.

## Output

A JSON object with a success boolean and (presumably) a list of accommodation options compared across the specified location, check-in/check-out dates, and budget — though the response schema only guarantees a success field.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "budget",
  "checkin",
  "checkout",
  "location"
 ],
 "properties": {
  "budget": {
   "type": "string"
  },
  "checkin": {
   "type": "string"
  },
  "checkout": {
   "type": "string"
  },
  "location": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "success": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/orbonomy-accommodation-compare-c89a59e5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from main.orbonomy.xyz](https://www.zero.xyz/host/main.orbonomy.xyz/llms.txt)