Metabase

briq_run({
  recipe: "metabase",
  params: {
    "size": "small",
    "dbSize": "nano"
  },
  wait: true
})

curl -X POST https://api.briq.cloud/v1/briqs \
  -H "Authorization: Bearer $BRIQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "recipe": "metabase",
    "params": {
      "size": "small",
      "dbSize": "nano"
    },
    "wait": true
  }'
# → { "briqs": [{ "id": "bq_…", … }], "outputs": { "METABASE_URL": "…" }, … }

# ... when done, for each briq id
curl -X DELETE https://api.briq.cloud/v1/briqs/<id> \
  -H "Authorization: Bearer $BRIQ_API_KEY"

When to use it

• The agent has analysed a dataset and you would rather open charts than read a table in chat.
• You want a dashboard someone can open from a link, without an account.
• You want SQL questions over data the agent loaded, kept and rerun on fresh data.

Two briqs: metabase serves the dashboards, postgres is the warehouse it reads. On first boot Metabase makes its admin account (password in METABASE_ADMIN_PASSWORD) and connects the warehouse as Warehouse, read through a read-only role: nobody signed in to Metabase can change the data. The full walk-through, from a CSV on the web to a shared link, is Report on a dataset.

Tips

• Load from inside the warehouse: the image has wget, so wget -qO- <csv url> | psql -U postgres -d warehouse -c "\copy t from stdin with (format csv, header)" in briq_exec never sends the data through the agent.
• Tables the agent creates as postgres in public are readable by Metabase. Another schema needs GRANT USAGE ON SCHEMA s TO reporter; GRANT SELECT ON ALL TABLES IN SCHEMA s TO reporter.
• mb calls Metabase's API as the admin from briq_exec on the metabase briq: ["mb", "GET", "/api/database"]; ["mb", "POST", "/api/card", "-"] with the JSON as stdin.
• Native SQL questions (dataset_query.type: "native") are the shortest way to a chart. After loading a new table, POST /api/database/<id>/sync_schema makes it browsable in the UI too.
• Share one dashboard: POST /api/dashboard/<id>/public_link returns a uuid; the page is /public/dashboard/<uuid> on the briq's URL. Run with expose: "private" and keep the ?briq_token= on the link you send, so the link is the only way in.
• First boot takes about three minutes while Metabase migrates its database: briq_run can answer while metabase is still creating; briq_status says when it runs. Later starts are faster, and the dashboards survive stops.
• Our World in Data files: aggregate rows (World, continents, income groups) have an empty iso_code, not OWID_WRL. Match the world on country = 'World'; iso_code IS NOT NULL keeps the countries.