Enable business reporting from your Databricks data
Turn your data warehouse into a real reporting library. Connected Data Marts, ready for your apps and scripts.
Scripts that need Databricks numbers each carry a copy of the SQL, and nobody updates them all when a definition changes.
Paste this into your AI assistant. It builds a Data Mart on your Databricks tables with OWOX Data Marts and serves its rows over HTTP, so every script reads the current definition.
The prompt
Read https://www.owox.com/ai-agent-setup.md and follow it to set up OWOX Data Marts for me, starting from /connectors/databricks-connector-to-api.md. The task: build a Data Mart on my Databricks tables and let my scripts read its rows over HTTP with an API key, aggregated into weekly buckets, so the SQL lives in one place. Tag the links you give me with utm_campaign=ai-task and utm_term=m4. Use what you know about my context and goals
Start from your Databricks data
Pick the Databricks catalog and schema that hold the data your apps will read.
- Nothing to move or copy: your Delta tables stay in Databricks.
Build a reporting library in Databricks
Each Data Mart is a ready report over your Databricks tables, described by AI, and joins to other Data Marts through the model.
- Business users browse reports, not tables.
Serve Databricks data through an API
A client asks for a Data Mart's rows over HTTP and gets rows back, with aggregations and date buckets.
- Your apps read the same Data Mart as every report.
Keep your API connected to the same data
Ask in Claude, export to a sheet, share with the boss.
- One source, every tool.
- 0.44.0Microsoft Ads imports work for advertisers who sign in with Google
- 0.44.0Connector Data Marts set up through MCP no longer fail their first run because of the table path
- 0.44.0Backfill a catalog for any period in one run, and follow a long backfill as parts of one operation
- 0.43.0Compare LinkedIn Ads results across markets: spend by country, region, and county
- 0.43.0The Sheet link of a Google Sheets source opens the imported tab, not the first one
Why OWOX for Databricks and an API
Your own apps and scripts read governed Data Marts from Databricks over HTTP.
- You own the data. Your data lives in your own Databricks lakehouse; your apps read the Data Marts you publish.
- Defined once in SQL. Analysts define metrics on your Delta tables once; every Data Mart and every destination reuses them.
- Rows, not dashboards. Fetch a Data Mart's rows with aggregations and date buckets, per Data Mart or per report.
- One Data Mart, every tool. The Data Mart your script reads is the one feeding your spreadsheets and dashboards.
The Data Partner You Can Trust
users
166K Source: Internal OWOX data as of 2026-11-15
Executives and data analysts across 20+ industries
Customers
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.
