TravelPulse: Global travel intelligence API for AI agents: weather, hotel deals, theme-park wait times, translation, trip plans, visas, health, currency, insurance, points. Any destination + language. x402 USDC (Base + Solana); no accounts, no keys. Coverage: Global Endpoints: • waits ($0.05): Li...
AI agents use travelpulse to create or update resources in Pulsenetwork — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pulsenetwork environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | — | Destination currency or country name |
date | string | — | YYYY-MM-DD, default today |
days | string | — | days |
from | string | — | Home currency (e.g. USD, EUR, GBP) — default: USD |
goal | string | — | Redemption goal, e.g. 'business class to Japan' or 'free hotel week in Europe' |
lang | string | — | lang |
park | string | — | Park name or slug e.g. magic-kingdom, universal-studios-florida, europa-park |
text | string | — | Text to translate |
cabin | string | — | economy | premium_economy | business | first |
dates | string | — | Travel window, free-form (e.g. 2026-09-10 to 2026-09-20) |
focus | string | — | Phrase focus area (transport, food, emergency, shopping, all) |
route | string | — | Route, e.g. 'LHR-JFK' or 'London to Tokyo' |
Parameters from the server's own tool schema.
An AI agent can call travelpulse faster than any human can review — one bad instruction and it creates or modifies resources in Pulsenetwork by the hundred, each call as confident as the last.
Risk signalsAccepts file system path (destination) · High parameter count (49 properties)
Attacks that exploit this kind of access
TravelPulse: Global travel intelligence API for AI agents: weather, hotel deals, theme-park wait times, translation, trip plans, visas, health, currency, insurance, points. Any destination + language. x402 USDC (Base + Solana); no accounts, no keys. Coverage: Global Endpoints: • waits ($0.05): Live park wait times • hours ($0.05): Park hours and schedule • crowds ($0.08): Crowd prediction • weather ($0.15): Travel weather forecast • deals ($0.08): Travel deals • plan ($0.20): Trip itinerary • visa ($0.08): Visa requirements by nationality and destination • insurance ($0.08): Travel insurance comparison and recommendation • pack ($0.10): AI packing list by destination, climate, and activities • budget ($0.10): Daily travel budget by destination and style • currency ($0.08): Currency exchange rates and money tips for destination • phrasebook ($0.05): Essential travel phrasebook by destination language • translate ($0.03): Real-time travel translation (menus, signs, conversations) • health ($0.08): Destination health advisories and vaccine requirements • fare-intel ($0.12): Flight fare intelligence — when to book, cheapest months • points ($0.12): Points & miles redemption optimizer • trip-check ($0.50): One-call pre-booking trip clearance (visa + health + safety + weather + money) • disruption ($0.25): Flight disruption risk for an airport and date • check ($0.10): Flight compensation eligibility — EU261 / UK261 / Canada APPR / Brazil ANAC 400 / Turkey SHY / India DGCA (deterministic) • letter ($2.00): Citation-backed flight compensation claim letter (6 regimes, ready to send). It is categorised as a Write tool in the Pulsenetwork MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
travelpulse accepts 12 parameters: to, date, days, from, goal, lang, park, text, cabin, dates, focus, route. The full parameter table on this page comes from the server's own tool schema.
Register the Pulsenetwork MCP server in PolicyLayer and add a rule for travelpulse: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Pulsenetwork. Nothing to install.
travelpulse is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the travelpulse rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for travelpulse. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
travelpulse is provided by the Pulsenetwork MCP server (https://pulse.theaslangroupllc.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
travelpulse is one line of Pulsenetwork's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →