YALineo
EN
Install

The cost of Genie and AI agents in Databricks

Genie, model endpoints, agents and apps each have their own lines in Databricks billing. Here is how to find them in the system tables, what is free, and what YALineo does.

Updated on 6 November 2026 · Abdouramane Youssouf

One question to Genie, several billing lines

In system.billing.usage, the billing_origin_product column says which product consumed, usage_metadata which object, and product_features of what type. An AI workload often spreads over several billing lines. A question asked of a Genie Agent runs a language model, billed under GENIE, then runs SQL queries, billed by the SQL warehouse. An AI agent pays for a server, calls to a model, and sometimes a search in documents.

Productbilling_origin_productWhat identifies it
Genie Code, Genie One, Genie Agents (the model)GENIEusage_metadata.genie.surface
SQL queries of a Genie AgentSQLwarehouse_id, then query_source.genie_space_id in system.query.history
Serving endpointMODEL_SERVINGendpoint_name, type in product_features.serving_type
Knowledge Assistant, Supervisor AgentAGENT_BRICKS, SUPERVISOR_AGENTagent_bricks_id
Databricks AppsAPPSapp_id, app_name
Unity GatewayMODEL_SERVING, AI_GATEWAYusage_metadata.ai_gateway.endpoint_name

Genie: what is free, what is billed

Databricks describes three Genie products: Genie One for business users, Genie Agents that data teams set up on their tables, and Genie Code, the assistant for developers. The usage_metadata.genie.surface field says which one consumed: GENIE_CODE, GENIE_ONE or GENIE_AGENTS.

Two SKUs, by price

Genie usage is split between two SKUs depending on whether it is free or billed, whatever the product:

Until 31 January 2027, a 25% promotional discount on billed usage is already included in usage_quantity: the list price applies as is. By Genie product and by day:

SELECT u.usage_date,
       u.usage_metadata.genie.surface AS genie_product,
       SUM(CASE WHEN u.sku_name = 'GENIE_FREE_USAGE' THEN u.usage_quantity ELSE 0 END) AS free_dbus,
       SUM(CASE WHEN u.sku_name <> 'GENIE_FREE_USAGE' THEN u.usage_quantity ELSE 0 END) AS billed_dbus,
       COALESCE(SUM(u.usage_quantity * p.pricing.effective_list.default), 0) AS list_price_cost
FROM system.billing.usage AS u
LEFT JOIN system.billing.list_prices AS p
  ON u.cloud = p.cloud
 AND u.sku_name = p.sku_name
 AND u.usage_unit = p.usage_unit
 AND u.usage_end_time >= p.price_start_time
 AND (p.price_end_time IS NULL OR u.usage_end_time < p.price_end_time)
WHERE u.billing_origin_product = 'GENIE'
  AND u.usage_date >= date_sub(current_date(), 30)
GROUP BY ALL

The outer join keeps the free rows, which have no price. A plain join would drop them, and their DBUs with them.

The SQL queries of a Genie Agent

A Genie Agent needs a pro or serverless SQL warehouse. According to Databricks, the compute for the queries Genie generates is billed separately, by that warehouse. In system.query.history, those queries carry the Genie Agent's id:

SELECT query_source.genie_space_id AS genie_agent,
       compute.warehouse_id,
       COUNT(*) AS queries,
       SUM(total_task_duration_ms) / 3600000 AS task_hours
FROM system.query.history
WHERE query_source.genie_space_id IS NOT NULL
  AND start_time >= date_sub(current_date(), 30)
GROUP BY ALL

This result is compute time. To turn it into dollars, you share the warehouse's cost between its queries, hour by hour, in proportion to that time. That share is already part of the warehouse's cost: adding it to the Genie line would count it twice.

Endpoints, agents and apps

A serving endpoint is billed under MODEL_SERVING, with its name in usage_metadata.endpoint_name. product_features.serving_type is FOUNDATION_MODEL, MODEL, GPU_MODEL or FEATURE. The Model Serving examples in the documentation filter on the Serverless Real-Time Inference SKU, where Genie's billed usage also lands: filter on billing_origin_product instead.

Agent Bricks is now the Databricks platform for developing agents in code. New agents run on Databricks Apps, with Agent Runtime: their server shows in the billing as an app, with app_id and app_name. Older ones run on a Model Serving endpoint. Knowledge Assistant and Supervisor Agent are no longer recommended for a new agent; their usage carries usage_metadata.agent_bricks_id. The cost of an agent adds up its server, its models, its AI Search retrieval and the tools it calls.

When a request goes through Unity Gateway, its MODEL_SERVING row also carries the service called (usage_metadata.ai_gateway.endpoint_name), the model (destination_model) and the caller (identity_metadata.run_by). The AI_GATEWAY product carries the costs of using the gateway. External models, called at another provider, are not in system.billing.usage: their spend is estimated, for information only, in system.ai_gateway.external_model_spend.

By object, over 30 days (for the cost, add the price join of the first query):

SELECT billing_origin_product,
       usage_metadata.endpoint_name,
       usage_metadata.agent_bricks_id,
       usage_metadata.app_name,
       usage_unit,
       SUM(usage_quantity) AS quantity
FROM system.billing.usage
WHERE billing_origin_product IN ('MODEL_SERVING', 'AGENT_BRICKS', 'SUPERVISOR_AGENT', 'APPS', 'AI_GATEWAY')
  AND usage_date >= date_sub(current_date(), 30)
GROUP BY ALL

What these lines do not tell

What YALineo does

YALineo reads these tables in your browser, with your Databricks permissions, read only, with no YALineo server.

AI costs. The "AI and Genie" page names each line by the product the billing gives: Genie Code, Genie One, Genie Agents, Model Serving, Databricks Apps... A Genie line without a product is called "Genie, type not indicated": YALineo does not guess, and its cost stays measured, on its own. The DBUs of GENIE_FREE_USAGE are counted apart, at a cost of 0, without making the total partial. "By product" adds up to the AI cost, to the cent. See the tutorial, filtering by product and the rule for each product.

The Genie Agent behind the queries. YALineo ties each warehouse query that carries query_source.genie_space_id to its Genie Agent, and gives the agent the share of the warehouse's cost its queries used, hour by hour. That share is shown next to the Genie Agents line, never added to the AI cost. In the Databricks pages, a link to a Genie Agent carries this amount as a badge, preceded by "≈". See how a warehouse is shared.

Before you build. In the Simulations, the "AI: Genie and agents" page prices the month of a Genie Agent or an AI agent, in DBUs and in dollars, at list price and then after your discounts. For a Genie Agent: the warehouse, sized on your users and questions, then the model, during the promotion, after it or for a service principal. For an agent: the model, retrieval, the server, the gateway and evaluation. The documentation read does not give the DBUs of a Genie question: outside the promotion, the page asks you for them, measured on a trial. While a value is missing, its part is not priced and the total is marked partial. See the tutorial and the formulas.

Frequently asked questions

Is Genie free?

In part. Each user has 150 free DBUs per month, and Genie One and Genie Agents are free for users until 31 January 2027. Genie Code beyond the allowance and the usage of service principals are billed. The SQL queries of a Genie Agent are still paid by its warehouse.

Where is the cost of a Genie Agent?

In two places. Its model is on the GENIE lines whose surface is GENIE_AGENTS, together with the other Genie Agents. Its SQL queries are in its warehouse's cost, where query_source.genie_space_id isolates its share.

Sources

Documentation read on 6 November 2026.