These Terms of Service explain the rules for using Automated Flight Purchase Conditions, including how AI flight price monitoring and automated purchase assistance (beta) works, what you can expect, and what you should not assume. If you are evaluating the offer, this page is meant to reduce legal friction by making the workflow and responsibilities clear before you start.
Quick answer: The system continuously monitors flight prices and can trigger an automated purchase attempt when a price you select is detected. You provide your own API key and store a credit card on file. The feature is currently in beta, so behavior and availability may change as we test and improve.
What Automated Flight Purchase Conditions covers
Automated Flight Purchase Conditions are the specific terms that apply when you use the flight monitoring and automated purchase features. They supplement the general Terms of Service and focus on the parts of the product that involve automated decisioning, scheduled actions, and payment handling.
In plain language, the terms cover:
- Monitoring behavior: how price monitoring is performed and how often the system checks fares.
- Trigger rules: how your user-defined target price is used to decide when an automated purchase attempt may be initiated.
- Scheduled purchase window: how you select a number of days for the system to attempt purchasing after the trigger condition is met.
- Payment and authorization: how a credit card on file is used for purchase attempts.
- Beta scope: what it means that the feature is in beta and may be updated over time.
Because flight inventory and pricing can change quickly, the terms also explain limitations and responsibility boundaries, including the fact that automated purchasing is not a guarantee of a specific outcome.
Who this is for
This feature is intended for buyers who want continuous flight price monitoring and are comfortable using an automated travel bot. It is most suitable if you:
- Know your target price and want the system to watch for it.
- Are willing to review and set up purchase parameters, including the scheduled number of days you want the system to attempt purchasing.
- Can provide and manage their own API key, and understand that you are responsible for the credentials you supply.
What you should not assume: You should not assume the system will always find the exact route you want at the price you selected, or that it will always secure the cheapest fare. Flight pricing and availability can change between monitoring and purchase attempts.
How it works (and what you control)
AI flight price monitoring and automated purchase assistance (beta) works as an algorithmic travel bot. It runs continuously, monitors flight prices, and can trigger an automated purchase attempt based on your settings.
Key mechanics described in the terms:
- Continuous monitoring: the system continuously monitors flight prices.
- Target price trigger: it triggers when a user-defined target price is detected.
- Scheduled purchase attempts: it can purchase flights on your behalf within a scheduled number of days you select.
- Beta testing focus: the feature is in beta, so workflows and performance may evolve.
- Your API key and payment method: users provide their own API key and store a credit card on file.
To reduce surprises, the terms also outline what happens when conditions change, such as when pricing shifts or purchase attempts cannot be completed. In those cases, the system will follow the rules configured in your settings, within the scope allowed by the beta feature.
If you want to understand related product expectations, review FAQ and Security & Data Protection.
Proof and trust
Because this is a legal terms page, proof is primarily about clarity, transparency, and user responsibility. At the moment, there are no additional third-party proof assets available on this page. Instead, the most important trust signals are the explicit conditions in the terms themselves, including what the system does, what triggers it, and what limitations apply.
When you review the Automated Flight Purchase Conditions, look for these trust anchors:
- Explicit triggers: the target price detection rule is defined so you can set expectations before you start.
- Defined time window: the scheduled number of days you select is the boundary for purchase attempts after a trigger.
- Clear beta language: beta scope is stated, which helps explain why behavior may change.
- Payment and authorization boundaries: the terms explain how your credit card on file is used for purchase attempts.
- Credential responsibility: the terms state that users provide their own API key.
If you have questions about how your data or payment details are handled, see the Privacy Policy and Contact AirScalp-Lab.
Next step
If you are ready to evaluate the beta feature, start by reviewing Pricing and then set up your monitoring parameters. When you get started, you will provide your own API key and confirm payment method details as required by the automated purchase workflow.
Get started when you are comfortable with the trigger and scheduled purchase window rules, and when you understand that automated purchasing is not a guarantee of availability or a guaranteed price.
API Key Requirements can help you prepare before you begin.