Hermes Agent,
wired for every airline.
Drop FlightAPI into your Hermes Agent flow as a single skill. Routes go in, ranked fares from 700+ airlines and OTAs come out, billed per search. The shape of the call matches Hermes Agent's skill contract — declare it once, then forget it.
Real Hermes flows that rely on this skill.
Each pattern below is a single Hermes Agent flow with FlightAPI registered as one skill. The math works because the flow only spends when it actually returns useful fares.
End-to-end trip plans from a one-line goal.
A user messages "book me to Tokyo in June, cheap." The Hermes flow runs round-trip and one-way searches, narrows by total cost and flight time, and presents top options. No human-managed GDS credentials anywhere in the chain.
Scheduled fare drops with zero idle cost.
A scheduled Hermes flow watches popular routes on cron. When fares drop below threshold, it pushes alerts via Slack or email. Days without a hit cost zero, so leaving a fleet of watchers running is cheap.
Benchmark every booked route.
Feed historical employee routes through the flow. Hermes queries FlightAPI for the same dates, surfaces where the booked fare was 20%+ above the lowest available, and produces a savings report — without paying a TMC for the same insight.
Auto-rebook when flights break.
A Hermes flow watches active flights. On delay or cancellation, it queries FlightAPI for alternates same calendar day, presents 3 options ranked by arrival time + price, and waits for human approval to book.
Stop wrapping GDS contracts into your flows.
Register one skill, connect a wallet, and your Hermes Agent flow gets fares from 700+ airlines on every relevant call. Idle runs cost zero. Tool migrations later cost zero. That's the entire deal.
- Single Hermes skill
- Flow caps honored
Hermes Agent specific questions.
If something below doesn't cover your case, ping us — we work directly with Hermes Agent builders, no SDR funnel.
How does this register as a Hermes Agent skill?
+
It's a single POST endpoint with a typed body. You register it in Hermes the same way you'd register any HTTP skill — endpoint, schema, price-per-call. Hermes Agent uses the price to plan flow budgets and to show the user what each run will cost before it fires.
Does Hermes Agent need a long-lived API key?
+
No. FlightAPI accepts x402-signed requests, so Hermes can pay per call from a wallet you connect. There's no shared secret to leak in flow logs or rotate every quarter.
What happens when a Hermes flow hits its budget cap?
+
FlightAPI returns whatever it has resolved so far and Hermes stops the next call. The flow can decide whether to ask the user for more budget or hand off with the fares it has.
Can the flow book flights through this?
+
Not directly — this skill is read-only flight data (prices, status, schedules). For booking, your Hermes flow should hand off to your booking surface (carrier site, OTA, internal travel system). The API gives the flow the inputs; the human-approved action does the booking.
How is this different from giving Hermes an Amadeus seat?
+
Amadeus requires enterprise contracts and significant onboarding. The skill can't report a true per-call cost, so Hermes can't do real budget planning. FlightAPI reports an honest per-call cost up front, which is what Hermes was designed to consume.
Can Hermes call this concurrently across many flows?
+
Yes. Per-key rate limits apply with concurrency-fair queueing — a noisy flow never starves another flow on the same key.