# Tripadvisor Location Search

> Tripadvisor Location Search is a paid API for AI agents from tripadvisor.x402.paysponge.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15, last successful call 2026-07-16).

Search for hotels, restaurants, and attractions worldwide by name or query on Tripadvisor

## Facts

- Endpoint: GET https://tripadvisor.x402.paysponge.com/api/v1/location/search
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Last successful call: 2026-07-16
- Success rate: 98% of calls made through Zero
- Rating: 4.7 / 5 from 1 review
- Activations on Zero: 65
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tripadvisor-091e320f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yhrnKDQjbPARae9NML5Ch

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 tripadvisor-091e320f
```

Example prompt: Search Tripadvisor for Italian restaurants in Florence, Italy and give me a list of results with their location IDs and ratings.

## When to prefer this

Use this endpoint when you need to find Tripadvisor location IDs or discover places by name/keyword before fetching details, reviews, or photos. Ideal as the first step in a travel research workflow before calling sibling endpoints for reviews or photos. Prefer this over the nearby search when you have a name or keyword rather than GPS coordinates.

## Known failure modes

- Missing or empty search query returns no results or a 400 error
- Query too vague returns unrelated or global results
- Rate limit exceeded returns 429 Too Many Requests
- Payment not included or invalid returns 402 Payment Required
- Network timeout returns 5xx server error

## How this service works

Location search

## Output

Returns a list of Tripadvisor locations matching the search query, each with location ID, name, address, location type (hotel, restaurant, attraction), coordinates, and rating data — usable to fetch full details, reviews, or photos via sibling endpoints.

## Example request

```json
{
 "input": {
  "type": "http",
  "method": "GET",
  "queryParams": {
   "searchQuery": "Paris"
  }
 },
 "output": {
  "type": "json"
 }
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tripadvisor-091e320f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from tripadvisor.x402.paysponge.com](https://www.zero.xyz/host/tripadvisor.x402.paysponge.com/llms.txt)