Changelog
Changes to the contract of the API v1 and of the MCP server, newest first. An additive change breaks no integration; a deprecation announces a path that keeps answering for one release cycle and then goes away.
2026-11-02 — subscription and prepaid AI credits
Additive, with a change of values. AI usage is now paid by two credits: the subscription ones (the plan's monthly allowance, with an optional excess) and the prepaid ones (bought separately). In GET /v1/ai_usage (MCP tool dashboards_ai_usage_get):
- New
subscription_credits:contracted,allowance_usd(the monthly allowance),consumed_usd(what it paid this month),excess_availableandexcess_consumed_usd. - New
prepaid_credits:balance_usdandconsumed_usd. entitlement(has_plan,monthly_limit_usd) andcredit_balance_usdstay, meaning what the new names say: subscription credits and the prepaid balance.- Changed values:
next_turn.funded_byis nowsubscription,courtesy,prepaidorsubscription_excess(wasentitlement,courtesyorbalance), andrecent[].funded_byis nowSUBSCRIPTION,COURTESY,PREPAIDorSUBSCRIPTION_EXCESS(wasENTITLEMENT,COURTESYorBALANCE). If you compare these strings, update the comparison.
2026-11-02 — actions named by what they do
Additive. Seven POST operations whose last segment was a noun got a path that says what the POST does. The reason is the kobana CLI, which derives each command name from the route: kobana dashboards builder secrets read as a collection while it encrypts a single value.
| New path | Replaces | What it does |
|---|---|---|
POST /v1/builder/test_action | POST /v1/builder/action_runs | Tests a draft action button |
POST /v1/builder/test_form | POST /v1/builder/form_submissions | Tests a draft form |
POST /v1/builder/encrypt_secret | POST /v1/builder/secrets | Encrypts a block secret |
POST /v1/builder/upload_og_image | POST /v1/builder/og_image | Uploads the og:image |
POST /v1/portal_settings/verify_sender | POST /v1/portal_settings/sender_identity | Verifies the notifications sender e-mail |
POST /v1/data_sources with kind: "openapi" | POST /v1/data_sources/openapi | Creates an OpenAPI data source |
POST /v1/data_sources with kind: "mcp" | POST /v1/data_sources/mcp | Creates an MCP data source |
POST /v1/data_sources with kind: "database" | POST /v1/data_sources/database | Creates a database data source |
Creating a data source became one operation on the collection: the body carries kind (openapi, mcp or database) and the fields of that kind — the same ones each old path accepted. The response always carries authorization_url (set only for an MCP server with OAuth). POST /v1/data_sources/catalog and POST /v1/data_sources/openapi/analyze did not change.
Deprecations. The eight paths in the "Replaces" column keep answering, with the same behaviour and the same response as before, for one release cycle. Each of their responses carries the headers Deprecation: true and Link: </v1/...>; rel="successor-version" pointing at the new path, and the operation is marked deprecated in the OpenAPI specification. Switch your calls before the next release.
MCP. The matching tools were renamed and now call the new paths; the old names are no longer in tools/list:
| New tool | Old name |
|---|---|
dashboards_builder_test_action | dashboards_builder_action_runs_create |
dashboards_builder_test_form | dashboards_builder_form_submissions_create |
dashboards_builder_encrypt_secret | dashboards_builder_seal_secret |
dashboards_builder_upload_og_image | dashboards_builder_og_image_upload |
dashboards_portal_settings_verify_sender | dashboards_portal_settings_verify_sender_identity |
dashboards_data_sources_create (with kind) | dashboards_data_sources_create_openapi, dashboards_data_sources_create_mcp, dashboards_data_sources_create_database |