TripGenie Actions

Overview

Use tripgenie for travel-related queries. The agent calls TripGenie HTTP APIs with a token in the JSON body; how to obtain it is defined only in Setup.

Security & privacy (read first)

1. API keys — API keys are sensitive credentials. They must be handled via environment variables (TRIPGENIE_API_KEY) set by the user. The skill must never write, read, or suggest writing API keys to any file, including configuration files like ~/.openclaw/.env. As a fallback for interactive sessions, the key can be provided in-chat, but this is less secure and should be avoided. Do not log or echo tokens.
2. Trust the endpoint — Confirm you intend to use https://tripgenie-openclaw-prod.trip.com and that TripGenie / Trip.com is an acceptable data processor for your use case before enabling this skill.
3. External responses — API output is third-party content. It may include links, promotional text, or structured data. Do not assume it is safe to relay verbatim in every context; summarize or filter when policy, safety, or privacy requires it. Avoid echoing raw responses into places that retain full history if they are unnecessary.
4. Operational — Review the key’s scope, billing, and rate limits with Trip.com. If you limit autonomous skill invocation, configure that in your agent/platform settings so travel queries are not sent to TripGenie more often than you want.

Inputs to collect

• query: User's travel query text (required for all requests).
• locale: Language/region code (e.g., en-US, zh-CN). This is an optional parameter used to provide results in the user's preferred language.
• For flight searches: departure, arrival, date, flight_type.

Setup

1. Obtain API key — From www.trip.com/tripgenie/openclaw (or your Trip.com-provided channel), per provider terms. Do not share full keys in screenshots or public channels.
2. Provide the token
   • Environment variable (recommended): The user should set the TRIPGENIE_API_KEY environment variable. This is the most secure method. The skill will automatically use this variable.
   • In conversation (fallback): If the environment variable is not set, the user can provide the API key in the chat. This key is used for a single call and is not stored. The environment variable always takes priority.
3. Smoke test — After configuration, run a minimal query; do not log bodies that expose the token.

Endpoints

Before running any command, resolve the token (in priority order):

1. If TRIPGENIE_API_KEY is set in the environment, use it as token.
2. Otherwise, use the key the user provided in this conversation as token (single-use only, no persistence).

General Query (/openclaw/query)

# The 'locale' argument is optional and can be omitted if not provided by the user.
jq -n --arg token "$TOKEN" --arg query "$USER_QUERY" '{token: $token, query: $query}' | curl -s -X POST https://tripgenie-openclaw-prod.trip.com/openclaw/query -H "Content-Type: application/json" -d @-

Flight Search (/openclaw/airline)

Domestic flight example:

jq -n --arg token "$TOKEN" --arg query "$USER_QUERY" --arg departure "BJS" --arg arrival "SHA" --arg date "2026-03-15" --arg flight_type "1" '{token: $token, query: $query, departure: $departure, arrival: $arrival, date: $date, flight_type: $flight_type}' | curl -s -X POST https://tripgenie-openclaw-prod.trip.com/openclaw/airline -H "Content-Type: application/json" -d @-

International flight example:

jq -n --arg token "$TOKEN" --arg query "$USER_QUERY" --arg departure "FRA" --arg arrival "HKG" --arg date "2026-03-17" --arg flight_type "0" '{token: $token, query: $query, departure: $departure, arrival: $arrival, date: $date, flight_type: $flight_type}' | curl -s -X POST https://tripgenie-openclaw-prod.trip.com/openclaw/airline -H "Content-Type: application/json" -d @-

Presenting results to the user

Always process the API response before presenting it. Do not return the raw response directly to the user. Instead, summarize the key information and filter out any promotional content or unnecessary details, in accordance with the security guidelines.