AI Data Sidekick

What is AirOps?

AirOps is an AI-powered search insights and content management platform designed for SEO, content, and growth teams. It connects traditional search data, the visibility provided by AI response engines, brand knowledge, and actionable workflows, thereby helping teams identify opportunities and produce or update content on a large scale.

The focus of current products has shifted from early general-purpose data assistants to AI-driven search and content management. The platform includes Insights, Workflows, Grid, Power Agents, Brand Kits, Knowledge Bases, as well as various business integrations.

A one-sentence summary

AirOps helps teams monitor a brand’s performance in AI-driven and traditional search, and transforms insights into content through workflows that include manual review, brand knowledge, and CMS publishing capabilities.

Core functions

• AI Search Insights: Track a brand’s presence and mentions across various search engines.
• Prompt monitoring: Observing the possible questions raised by target users and the changes in their answers.
• Page monitoring: Analyze the visibility opportunities for both own pages and external pages.
• Content workflow: combination of models, search, data, code, manual review, and publishing steps.
• Grid batch processing: Handles a large number of pages, keywords, and content tasks on a row-by-row basis.
• Power Agents: Use intelligent agents with pre-made content that can be copied and modified.
• Brand Kit: Defines the tone, terminology, rules, and brand expression.
• Knowledge Base: Links to files, web pages, and internal documents.
• Content update: Outdated pages are identified, and suggestions for modifications are generated based on current data.
• CMS integration with business tools: linking publishing, SEO, analytics, as well as project and collaboration tools.

AI Search Insights

Insights is used to track a brand’s performance in various answering platforms such as ChatGPT, Gemini, Perplexity, and Google AI Overviews. Teams can view the questions that are being monitored, the pages cited, competing brands, as well as opportunities for taking action.

• Check whether the brand appears in the answers to key questions.
• Check which domain names and specific pages the response engine references.
• Compare different competitors, regions, roles, and issue topics.
• Identify the internal pages that need to be updated and the external discussions to participate in.
• Transfer insights into content creation, refreshing, or distribution workflows.

Synergy between traditional SEO and AEO

AirOps focuses not only on traditional rankings but also includes the optimization of answer engines as part of its content strategy. Its goal is to enable teams to understand search traffic, AI citations, and content performance simultaneously, rather than creating separate processes for each channel.

• Plan topics by combining keywords, competitive pages, and AI response opportunities.
• Compare the performance of the search page with that of AI citations.
• Find external content and community opportunities based on the referenced domain names.
• Convert AEO findings into actionable editing and publishing tasks.

Visual workflow

Workflows are composed of four types of elements: inputs, steps, variables, and outputs. Users can use a visual editor to connect text generation, web research, SEO data, code, conditions, loops, manual review, and CMS publishing into a cohesive production process.

• Input: Receives text, files, options, and runtime parameters.
• Steps: Perform operations on models, searches, images, code, or data.
• Variable: Pass the result of the previous step to subsequent steps.
• Output: Returns articles, analyses, images, or structured data.
• Log: Records the results of each step, errors, and operational information.

Workflow step type

Manual review and quality control

The Human Review step allows the automated process to be paused, waiting for editorial review, modifications, or approval before proceeding. Content Comparison also enables comparison between different versions, helping teams assess the scope of updates and preserving human decision-making.

• After the research is completed, experts verify whether the data is reliable.
• After generating the text, check the facts, opinions, and brand tone.
• Compare the old version with the new version before publishing.
• Different review paths are used for high-risk or low-confidence results.
• Provide clear warnings when an error occurs, and prevent erroneous content from entering the CMS.

Batch content management via Grid

Grid functions as a structured workspace tailored for content management; each row can represent a page, a keyword, or a content task. The workflow column allows processing of either a single row, the first 10 rows, the remaining rows, or all rows, and it can also operate automatically according to a scheduled plan.

• Batch refresh a large number of old articles.
• Generate a draft of content based on keywords or product records.
• Map the workflow output back to the specified columns.
• View the queued, running, successful, and failed statuses.
• Record the time taken for each run, step-by-step logs, and error messages.
• Retry failed rows to avoid processing all data from scratch.

Brand Kit brand rules

The Brand Kit is used to define the brand’s voice, tone, vocabulary, rules, and writing guidelines. By using the same set of brand settings across various workflows, it is possible to reduce differences in expression among different authors, models, and channels.

• Define the brand’s personality, level of formality, and target audience.
• List the terms that must be used or are prohibited from use.
• Explain the product’s positioning, core values, and unique selling points.
• Set legal disclaimers, risk statements, and editing boundaries.
• Establish separate rules for different brands or business lines.

Knowledge Base knowledge repository

The Knowledge Base allows for the uploading of files, scraping of websites, and connection to data sources, thereby providing an organization-specific context for workflows. It is suitable for storing product information, research materials, style guides, and internal knowledge; however, it is necessary to handle permissions and sensitive data before importing such content.

Power Agents pre-built intelligent agents

Power Agents are pre-built Agent workflows designed for common content tasks, which users can copy and modify. They help to reduce the time required to create a process from scratch, but adjustments still need to be made using actual brand materials, examples, and approval criteria.

Content refresh and optimization

AirOps can analyze existing pages, competitive content, and real-time SEO data to identify opportunities for updates, and it generates new versions through workflows. The team can also send these updated versions to a CMS or project management system, where they are reviewed by editors before being published.

• Identify the pages whose traffic, rankings, or AI citations have declined.
• Identify missing topics, expired facts, and new user questions.
• Compare the differences between the competitive pages and the current content.
• Generate a targeted update version that retains the original value.
• Monitoring and refreshing are carried out at regular intervals.

Content creation

The content creation process combines external research, internal expert knowledge, brand guidelines, model generation, and manual editing. Unlike one-time conversations, this workflow emphasizes repeatability, monitorability, and the ability to run tasks in batches.

• Study the research topics, target audience issues, and competing content.
• Extract product and brand facts from the knowledge base.
• Generate outlines, chapters, and versions for different channels.
• Include the opinions of expert humans and real-world cases.
• After completing the quality check, write it to the CMS draft.

Supported integrations

The AirOps documentation categorizes integrations into areas such as CMS, SEO research, AEO research, analysis, project management, company data, social media, and collaboration. The availability of specific connectors varies depending on the package; it is necessary to verify each one against the existing technology stack before making a formal purchase.

• CMS: Writes the results of the workflow into the website content system.
• SEO and AEO: Introduction of keyword, page, and answer engine data.
• Analysis: Determine priorities by considering traffic and conversion performance.
• Project management: Create tasks and track edits and approvals.
• Social and community: Supports content distribution and external engagement.
• Custom API: Connects internal systems to public interfaces through code.

Which users are it suitable for

• An SEO team is needed to create and update content on a large scale.
• Brands that wish to monitor the visibility of answer engines such as ChatGPT.
• Content marketing agencies that manage a large number of clients and pages.
• Enterprise teams that need to combine human experts with AI to create content.
• Organizations that have multiple CMS platforms, data sources, and approval processes.
• Growth teams that aim to connect content strategy with production and performance data.
• Content engineers who need APIs and custom workflows.
• Large enterprises that are responsible for multiple regions, roles, and languages.

Typical use cases

• AI search monitoring: Tracking brand mentions, citations, and competitive performance.
• Content refresh: Batch update outdated or underperforming articles.
• New content creation: a standard process from research to the development of CMS drafts.
• Product page expansion: Generate pages in bulk based on structured data.
• Community and external content: Plan external involvement based on opportunities for citation.
• Multilingual operation: Adjust content versions according to region and role.
• Expert content: Incorporate interviews and internal knowledge into brand articles.
• Agent delivery: Assign separate knowledge sets and brand rules to different customers.

AirOps usage guide

1. Create a workspace, choose the Solo trial option, or work with the sales team to determine the best approach.
2. Create a Brand Kit and enter the tone, terminology, target audience, and content guidelines.
3. Create a Knowledge Base and import the web pages, files, and data that are permitted to be used.
4. Choose a pre-built Agent or start designing inputs and outputs from a blank workflow.
5. Include research, modeling, processes, manual review, and release steps.
6. Use test data to run each step gradually and check the logs.
7. Publish a workflow, which can then be executed via a single run, Grid, scheduled tasks, or API.
8. Monitor task consumption, failure rate, edits and modifications, as well as the results of content-related operations.

How to set up a content refresh workflow

1. Import the pages to be updated, keywords, and current performance data into the Grid.
2. Add steps for web scraping and SEO research to extract existing content and competitive information.
3. Use conditional filtering to identify the pages that truly need to be updated.
4. Invoke the knowledge base and Brand Kit to generate brand-compliant draft updates.
5. Add content comparison and manual review to check the deleted and added sections.
6. The approved content is written into the CMS draft, rather than being made publicly available automatically.
7. After publication, traffic, rankings, and citation performance are retrieved at regular intervals.

How to test workflows

1. Enter representative test inputs for the initial steps.
2. First, run each step one by one to examine the output structure and variable names.
3. Test the true and false branches of the conditional statements, as well as the boundary values within the loops.
4. Check whether the model’s output maintains the specified JSON, HTML, or text format.
5. Error handling is provided for extremely long contexts, null values, failures of external interfaces, and timeouts.
6. After achieving stability in a single step, run the entire process and compare it with the expected output.
7. Before going live, run it with a small amount of real data to determine the task costs and the amount of manual editing required.

APIs and automation

AirOps offers public APIs that use Bearer tokens for authentication, enabling the synchronous or asynchronous execution of published workflows, as well as the ability to check their status, cancel them, retry them, and submit feedback. Long-running or large-scale tasks are better suited for asynchronous processing, with results obtained through status checks or Webhooks.

• Structured input is fed into published workflows via API.
• Reads the execution status, output, runtime, and usage statistics.
• Cancel or retry the failed workflow execution.
• Integrate AirOps into internal content systems and approval processes.
• Use Webhooks to receive asynchronous completion events.
• Securely store API keys on the server side and maintain call logs.

Packages and public prices

The current official website of AirOps lists three main packages: Solo, Pro, and Enterprise. However, it does not show the fixed monthly fees for the Solo and Pro packages on that public page. According to the official information, the prices are determined based on the volume of tasks and specific requirements; therefore, the catalog should not include old fixed prices.

Comparison of package features

How is task billing handled?

A Task is the unit of measurement used in AirOps; tasks are created whenever specific actions such as generating content or extracting data are successfully carried out. Not every step in a workflow incurs a charge, and the number of tasks depends on the type of step and the amount of data processed.

• Solo includes 20,000 production tasks per month.
• Pro includes 75,000 production tasks per month.
• The task quota for Enterprise is customized according to the contract.
• The public price for Solo excess tasks is 0.025 USD per unit.
• The limit is reset at the beginning of each calendar month.
• Work area billing settings and workflow monitoring allow you to view usage levels.
• Multiple billing steps in complex processes increase the cost per piece of content.

Free trial and testing quotas

The official pricing page offers a 14-day free trial, without the need to enter payment details in advance. The trial ends when the time runs out, when all the trial tasks have been completed, or when the user upgrades to the paid version ahead of schedule.

Both the document and the pricing FAQ mention 50,000 free test tasks available in the workflow editor, but there have been historical differences regarding the name of the package applicable to these tasks. It is necessary to check the amount of test tasks available and their scope of application on the billing page of the current workspace before starting actual use.

Built-in model API key

The pricing comparison table lists Bring Your Own Model API Keys as one of the organizational capabilities, but the FAQ states that Solo users can contact the team to purchase it; the older versions of this text used historical package names such as Scale and Agency. Whether this service is included and what the additional costs are depend on the current contract or the dashboard settings.

Product advantages

• Place AI search insights and content execution on the same platform.
• Workflows can combine models, data, code, manual review, and deployment.
• Grid is suitable for processing large numbers of pages and content items in bulk.
• The Brand Kit and Knowledge Base help maintain brand consistency and factual accuracy.
• It supports conditions, loops, error handling, and comparison of content versions.
• It offers a variety of CMS, SEO, analytics, project, and collaboration integration tools.
• Public APIs allow workflows to be integrated into internal corporate systems.
• Pro offers an unlimited number of team seats, making it suitable for collaborative work among multiple people.

Usage restrictions and precautions

• The basic subscription prices for Solo and Pro are not disclosed; it is necessary to contact the official authorities to find out the costs.
• Complex workflows may involve multiple tasks for a single piece of content.
• For tasks that exceed the Solo quota, a charge of $0.025 will be applied continuously.
• Historical plan names such as Scale, Agency, and Pro Plus still appear in different documents.
• AI-generated search responses and citations can change, and short-term fluctuations should not be overinterpreted.
• Batch generation can amplify factual errors, repetitive content, and brand deviations.
• A manual review and rollback mechanism should be maintained before automatic writing to CMS.
• External search, model, and data providers can affect stability and costs.
• Knowledge bases and workflows handle corporate content, and strict permission management is required.
• AEO performance does not guarantee an increase in traffic, citations, or revenue.

Data and security recommendations

• Isolate workspaces, knowledge bases, and access rights by brand, customer, and region.
• Only internally generated materials that are authorized and related to the task are imported.
• Anonymize customer, employee, and confidential business data first.
• API keys are stored only on the server side and are rotated regularly.
• Manual approval is set for the steps of CMS publishing, social media posting, and external data writing.
• Retain workflow versions, operation logs, and change history.
• Before making a purchase, enterprises verify SSO, data retention policies, regional considerations, and contract terms.

GitHub and open source

The AirOps official website, documentation, and pricing page do not provide any links to an official GitHub repository for its core products. Many projects listed in search results under the name AIOps are different from the AirOps content platform; they cannot therefore be considered as evidence of open-source nature.

AirOps is a managed business platform; its Insights, Workflows, Grid, Agent, and knowledge base systems are not open source. The availability of public APIs and the possibility to write custom code steps merely indicate scalability, but they do not mean that the platform can be deployed on one’s own.

Basic information

Recommendation score

4.6 / 5. AirOps is suitable for mature content teams that need to integrate AI-driven search monitoring, SEO data, brand knowledge, batch processing, and manual approvals into repeatable processes; however, the public pricing information is incomplete, the costs associated with various tasks require modeling, and there are historical discrepancies in the package names and some documents.

Frequently Asked Questions

What does AirOps mainly do?

It monitors a brand’s performance in AI-based and traditional search methods, and it creates, updates, and publishes content through workflows and grids.

Is AirOps free?

The official website allows users of Solo and Pro to start a trial period, offering 14 days of free use; however, the price of the regular subscription plan is not disclosed.

How much is AirOps?

The prices for Solo and Pro are determined based on the volume of tasks and requirements, while Enterprise offers a customized quote.

What is a Task?

A Task is a unit of measurement used to indicate the successful completion of specific actions such as generating content or extracting data; not every step incurs a charge.

What to do once the tasks are completed?

Solo can continue to be used, with additional tasks costing $0.025 each; the rules applicable to other packages are those specified in the contract.

Does AirOps support response engines other than ChatGPT?

Pro and Enterprise support multi-engine insights; Solo currently offers only ChatGPT Insights.

Does AirOps support manual review?

Supported: It is possible to include a Human Review step in the workflow, so that processing or publication can proceed only after approval.

Does AirOps provide APIs?

It allows for executing, querying, canceling, and retrying published workflows; it also supports asynchronous operation and Webhooks.

Is AirOps open source?

Not making the code open source – making the API and code available publicly does not mean that the source code of the core platform is made available.