Creates Databox data sources and datasets, pushes records into them, verifies each ingestion landed, and removes what is no longer feeding a dashboard.
7actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro sends data points to a Databox dataset for visualization and tracking. Your team logs metrics and KPIs into dashboards without manual entry.
Ayro sets up a new data source in Databox during a conversation. Your team can instantly create analytics pipelines without leaving chat.
Ayro checks the status of a specific data ingestion to a dataset. Your team monitors pipeline health and debugs failed data loads.
Each card is one request a support team gets, and the Databox actions Ayro runs to close it.
Ayro finds the account ID, creates the data source with its title and timezone, then creates a dataset inside it with the primary keys that identify a unique record.
Ayro sends an array of records matching the dataset schema into the dataset by ID, so a number that changed in a source system reaches the dashboard reading from it.
Ayro takes the ingestion ID returned by the push and checks its status against the dataset, so a silent failure is caught rather than showing up as a dashboard that quietly stopped moving.
Ayro removes a dataset that no longer feeds anything, or the whole data source when a tool is decommissioned, keeping the account free of feeds nobody reads.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Databox actions it has and picks the ones a request needs.
Authorize the Databox account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Databox actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeDatabox · Ayro
What can you do in Databox without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Databox.
No. Every action in this toolkit sits on the ingestion side: List Accounts, Create Data Source, Create Dataset, Push Data to Dataset, Get Dataset Ingestion Status, Delete Dataset, and Delete Data Source. Ayro feeds the dashboards and verifies the feed arrived; reading a metric back is still done in Databox.
All 7 actions your agent can call on Databox, straight from the live MCP connection.
Create a new dataset in Databox data source.
Create a new data source in Databox.
Delete a dataset by ID in Databox.
Delete a data source by ID in Databox.
Check the status of a specific data ingestion for a dataset.
Retrieve all Databox accounts accessible to the authenticated user.
Push data points to a Databox dataset using the v1 API.
Same connection, same setup. Pick the next one your team already uses.
Profiles a domain's current and historical stack, finds every site running a given technology, and packages the result as a domain list.
Reports a map's layers and elements, adds or updates features as GeoJSON, organises maps into projects, and clones maps as templates.
Pulls a lead's sessions and event history, retags records as qualification changes, and logs conversions back from the conversation.
Retrieves every scraping project on a ParseHub account, so a team confirms what is already configured without a dashboard login.
Lists pipelines, workflow runs, and compute environments, submits Wave container builds, and returns build status and logs.
Returns short, spoken or LLM-formatted computed answers, checks how a query parses, and recovers pods from a timed-out computation.

Authorize the account and your agent has all 7 actions from the first conversation.
