Onboarding

Onboarding for AirScalp-Lab is designed to get you from “I want to track fares” to “the system can watch and assist” as quickly as possible. If you are here for the AI flight price monitoring and automated purchase assistance (beta), this page explains what to expect, what you need to provide, and what you should not assume.

Quick start: Join the beta when you are ready. You will set your monitoring targets, confirm your settings, and connect the data source using your own API key. The bot then runs continuously according to your rules.

What you get during onboarding

Onboarding is the setup step that turns your travel intent into an automated monitoring workflow. The system continuously monitors flight prices, then triggers when a user-defined target price is detected. From there, it can assist with purchasing within the time window you select.

Because this is beta testing focus now, onboarding also includes guardrails around how the assistance works, how you control timing, and how you review the settings before anything runs.

  • Continuous monitoring: the algorithmic travel bot keeps checking without you manually refreshing.
  • Target price triggers: you define the price threshold and the conditions that matter to you.
  • Scheduled purchase assistance: you choose a number of days for the purchase window.
  • Your credentials and payment: you provide your own API key and store a credit card on file.

How AI flight price monitoring and automated purchase assistance (beta) works

The beta feature is built around a simple loop: monitor, detect, and assist. During onboarding, you configure what the system should watch and what actions are allowed when your target price appears.

Monitoring and triggers

The system continuously monitors flight prices and triggers when a user-defined target price is detected. Triggers are based on the rules you set, not on a promise of availability or a specific fare outcome.

Automated purchase assistance

If you enable purchase assistance, the system can purchase flights on the user’s behalf within a scheduled number of days they select. You control the time window during setup, so you are not forced into an immediate decision.

What onboarding requires from you

For the beta, users provide their own API key and store a credit card on file. This keeps your configuration aligned with your account and allows the system to operate continuously once everything is connected.

How to get started

Onboarding is mostly configuration. You will set your monitoring targets, confirm the purchase window, and connect your API key. If you are comparing options, start with one or two trips so you can validate the settings before scaling up.

  • Step 1: Join the beta and open the onboarding flow.
  • Step 2: Add your flight monitoring targets and set your target price.
  • Step 3: Choose the scheduled number of days for purchase assistance.
  • Step 4: Enter your API key and confirm your payment method, then review the final settings.
  • Step 5: Let it run. The bot is designed to work continuously as an algorithmic travel bot.

CTA: Ready to try it? Join the beta.

Common questions

Who is this for?

This beta is for travelers who want continuous flight price monitoring and are comfortable setting a target price and a purchase window. It is also a good fit if you prefer automation over manual checking, but still want control over the rules.

What should buyers not assume?

Do not assume the system can guarantee specific route availability or a specific price. Also, avoid expecting instant results, or assuming it will always find or buy the cheapest fare. Flight inventory and pricing change, and your target price is a trigger, not a promise.

Is this a one-time setup?

Once configured, the monitoring is designed to run continuously. You can adjust your targets and purchase window as your plans change, especially if you want to refine thresholds or timing.

What happens to my payment and API key?

During onboarding, users provide their own API key and store a credit card on file. Those inputs are used to enable continuous operation and the beta’s assistance workflow. If you have questions about how data is handled, review Security & Data Protection.

How to get help

If something does not match your expectations during onboarding, you can reach the team for guidance. For the fastest help, include what you are trying to set up, what step you are on, and any error messages you see.

Contact AirScalp-Lab

If you want to plan your setup before you begin, start with the product overview and pricing pages.

Related resources

These resources help you understand what to configure and how to think about outcomes in a beta environment.

  • Monitoring setup tips: Learn how target prices and conditions translate into triggers.
  • Purchase window guidance: Understand how the scheduled number of days affects decision timing.
  • Beta expectations: Review what continuous monitoring can and cannot guarantee.

Not sure where to start? Join the beta, then use the help options if you want a walkthrough.

CTA: Join the beta and begin onboarding for AI flight price monitoring and automated purchase assistance.

Scroll to Top