Tell AI what data you need, and it figures out how to retrieve it.
AI Data generates the appropriate R script, runs it, reviews the result, and automatically improves the approach when necessary—then imports the data into Exploratory, ready for analysis.
From files and databases to APIs, websites, and open data—all through natural language.

AI Data handles the work between “I need this data” and “the data is ready to analyze.”
You do not need to know the exact file, table, API endpoint, or query syntax. Simply describe the result you want.
AI examines the available data sources and determines the appropriate approach. Depending on the source, this might mean:
It then generates the required R script and runs it inside Exploratory.
AI checks the returned data to determine whether it matches the original request. If not, it re-evaluates the approach, updates the script, and runs it again. Once the result is ready, the data is imported into Exploratory.
If Exploratory already supports the service, AI can use its existing integration or R functions. When no built-in integration exists, AI can use publicly available API documentation to generate the required data acquisition script.
Review the resulting data preview and give AI additional instructions.
| respondent_id | year | satisfaction |
|---|---|---|
| 000123 | 2024 | 4 |
| 000124 | 2024 | 5 |
| 000125 | 2025 | 3 |
| 000126 | 2025 | 4 |
Getting access to data is only part of the problem.
AI Data can also perform the basic preparation required before visualization or analysis.
Move directly from data acquisition to visualization and analysis.
AI Data does not simply return a snapshot of the data. It creates the R script that produces the data.
That script becomes part of the Exploratory project. When you need updated data, simply click Re-import and run the same process again.

Turn a one-time AI request into a reusable data pipeline.
As you refine your request, the underlying R script changes. Each generated version is preserved.
You can inspect previous versions or restore an earlier approach when needed.

The first time AI works with a particular data source, it may need to explore different approaches. Once a successful method has been established, that knowledge can be saved as a Skill.
The next time a similar request is made, AI can reuse the proven approach instead of starting from scratch. Skills can also be shared with others.
Turn one person’s successful AI workflow into a team-wide best practice.
When configuring a database connection, you can choose which schema information to make available to AI.
Without saved schema information, AI can still inspect the database schema, but doing so requires additional discovery.
AI determines the appropriate SQL based on the available schema and database capabilities.
Connecting to a database often means installing drivers, configuring connection settings, and entering credentials. APIs come with their own setup, including API keys, client IDs, and authentication details.
With AI Data, you can let AI guide you through the setup and handle much of the configuration—so you can spend less time figuring out how to connect and get to the data faster.
Challenge: Survey response data often contains question codes and response codes rather than readable labels.
Challenge: Each year’s survey or business data lives in a different Excel file, and column names change slightly from year to year.
If multiple tables are detected, AI can identify them and ask you which table should be imported. After you select one, AI extracts and cleans the relevant table.
AI determines the appropriate GA dimensions, metrics, and retrieval process and returns the result as an analysis-ready data frame.
The exact geographic concept you have in mind may not exist directly in the published dataset.
AI can determine which official geographic units correspond to the requested area, retrieve the necessary records, combine them, and produce a usable result.
Even if this requires nested SQL, window functions, or database-specific syntax, you only need to describe the output.
AI generates the appropriate query, runs it, inspects the result, and revises it when necessary.
Describe the result you need without having to know the schema or query syntax.
Combine and standardize fragmented files without repetitive manual preparation.
Let AI identify the right public dataset and turn it into a usable analytical table.
Retrieve data even when there is no dedicated Exploratory connector.
Extract useful structured data from sources that are otherwise difficult to import.
Turn a successful process into a reusable and shareable workflow.
Any data source you can use in Exploratory today is also available in AI Data. Connections you have already created are listed in the AI Data window, so you don’t need to set them up again.
The main supported data sources are:
You can also get data from public statistics such as e-Stat (the Japanese government’s statistics portal), a wide range of public APIs, and documents published on the web. For data sources without a predefined procedure, AI Data researches their specifications and tries to retrieve the data, so just tell it what you need.
No. AI Data is responsible only for retrieving the data you asked for and shaping it into a form ready for analysis. It never invents metrics you didn’t ask for.
Processing at import time is limited to converting the data into a tidy format and converting data types. AI Data never adds new columns, such as totals or ratios, on its own judgment.
You can trace which values in the source data each number came from through the generated R script.
If you do need additional processing at import time, just ask for it in the AI Data chat.
Yes. Before importing, AI Data shapes the data so that:
It also removes empty rows and rows that aren’t data, such as footnotes and source notes. Once the import completes, you can go straight to creating charts.
No. Credentials are handled as follows:
For data sources that require an API key, a dedicated dialog asks you to enter it. The value you enter is kept inside Exploratory and is never passed to AI as is.
Only the information needed to work out how to retrieve the data: the column names and first few rows of files, and database schema information. When a file’s structure is complex and the first few rows aren’t enough to tell where the headers end and the data begins, AI Data may read more rows.
The retrieved data itself is imported by running the generated R script in your environment.
No.
Once an import completes, the generated R script is saved as the data source. After the source file or database is updated, just click the Re-import button, and only the saved script runs.
AI doesn’t run again, so you get the latest data with the same steps every time.
Because the same process runs the same way every time, you can rely on it for data that is updated regularly.
Imported data is treated just like any other data frame in Exploratory. So even after the import, you can keep making adjustments, such as changing conditions or removing unwanted rows.
To do this, reopen AI Data from the token (the gray box) in the source step, which is the first step.
It opens with the conversation from the import still there. Enter your additional instructions and send them, and only the new changes are applied on top of what was done before. You don’t need to start over.
No.
When you create or update a data frame, the steps used at that time are automatically saved as a Skill. The next time you specify data with a similar structure, AI Data applies the same process based on the saved steps, adjusting for differences such as column names.
A Skill is a Markdown file that describes what R script to write for what kind of request. Skills are saved under the “datasource” path in the “ai_skills” folder of the .exploratory repository, so you can review them later to make sure nothing unintended has been saved.