DocsWhat you can doShare data publicly
For agentsShare a dataset with the world.
Put your data in its own catalog and publish it. Anyone can query it, no account needed; the rest of your data stays private.
Before you start: Claude Code (or any other agent)Your data (a CSV or Parquet file)An admin login to your account
Ask your agent to load and publish it
Say what the data is and that it should be public. A good agent keeps it apart from your private data.
I measure NO2 around my neighbourhood (~/Downloads/no2-barrio-2026-09.csv). Put it in LakehouseBox and publish it so anyone can query it. Follow lakehousebox.com/docs/
I've installed the LakehouseBox command line. First, approve this computer in your browser.
My plan: put your readings (3,600 rows, one month) in a separate catalog called no2_barrio, since publishing makes a whole catalog public; your other data stays private. Then load the CSV as one table and publish that catalog.
Before you agree: everything in it becomes readable by anyone, including the station names, their coordinates and the table's history.
Approve and decide
You approve the sign-in and confirm the plan. Publishing is your decision.
Your turn · in the browser
Approve your agent's access
Open the link your agent gives you (or the page it opens in your browser) and click Allow; when the page asks for a code, type the one your agent gives you. Then tell your agent the plan is fine, or what to change (another catalog name, fewer columns: say if the coordinates should not be public).
Publish it yourself
Your agent loads the data; making a catalog public is a decision for a person.
Your NO2 data is in LakehouseBox, but it isn't public yet: publishing is your decision. To publish: log in at lakehousebox.com/app/, open the no2_barrio catalog's Settings, type its name under Visibility and click Make public. Only no2_barrio becomes public.
Your turn · in the browser
Publish the catalog
On your account page, open the catalog's Settings tab, type the catalog's name under Visibility and click Make public. Making data public is a decision for a person with admin rights (or a member with write, if an admin lets members publish). An agent connected through MCP cannot publish; the key lhbox login gives your agent acts as you, so if you are an admin it could also run lhbox catalog publish when you tell it to. Then tell your agent "published".
Your agent checks it from the outside
It queries the data with no account and no keys, the way a stranger would, and gives you what to share.
published
Your NO2 data is public. I queried it from a fresh DuckDB with no account and no keys, and all 3,600 rows came back.
Public page: lakehousebox.com/app/your-account/no2_barrio
For September, Escuelas Aguirre and Plaza de España had the highest averages, about 26 µg/m³; the peak was 53.1 at Plaza de España.
- Only no2_barrio is public. Your other catalogs stay private.
- You can make it private again at any time, but anyone who already copied the data keeps their copy.
Example · verified connection
What becomes public, exactly
Everything in the published catalog: every table's data files and its history (older versions, until they are cleaned up), the catalog's guide for agents if it has one, and the list of its files. Your account's handle appears in every public link. People can read and query; nobody can write or delete. Other LakehouseBox users can also attach your catalog read-only by name. Making it private again stops new reads at once.
Make no2_barrio private again.
Add October's readings to the public table.
Write a short description of the dataset for people who find it.