dip db load.
Each file is private to you. Another member cannot list, download or delete it, and asking for
someone else’s file reports it as not found.
Upload a file
object_ref, for example 3f9c0a.../report.xlsx. Keep it: every other command
and tool takes it. The file goes straight from your machine to object storage, so size is limited by
your connection and the storage service, not by Dippr’s servers. dip also prints the file’s SHA-256 so
you can check a later download.
Get, list and delete
dip file get --url prints a download link that works for a few minutes, for a tool that fetches the
file itself, such as read_parquet('<link>') in DuckDB. Deleting is permanent.
From an agent
The same four actions are the MCP toolsfile_upload_url, file_download_url, file_list and
file_delete; see Plane file tools. An upload is a short-lived URL
that the agent sends the bytes to with an HTTP PUT, so an agent that cannot make an HTTP request
outside MCP cannot complete one.
An agent connected through OAuth the usual way does not hold the file permissions below. If a file tool refuses
that OAuth connection, the tools are listed but a standard connection cannot use them. Use dip file list and the
other dip file commands in a terminal instead; dip asks you to approve once in the browser if it needs to.
For an API-key connection missing a file permission, the refusal instead says to use a workspace
API key minted with that permission.
What you need
An API key needs the capability above and
query_engines:list, because every MCP connection
requires it.
Neither is part of the default consent, so a client asks for them by name and you approve the line on
the consent screen. dip asks for both lines together the first time you run any dip file command,
so you approve once and can then upload, list, download and delete on that data plane without being
asked again until the approval is revoked or expires (after 30 days by default; a workspace can be
set up with a shorter or longer period). See OAuth scopes. A service user’s API key can carry
them too; see Service users and API keys.
Limits
- An upload link and a download link each work for five minutes by default and never longer than 15.
- A single file is limited to 5 GiB by default.
- Files stay until you delete them. There is no automatic expiry yet. Deleting your tenant removes its files.
- An upload link keeps working until it expires. If you delete a file while its upload link is still valid, a late upload to that link recreates it, so delete again once the link has expired.
- A list returns 1000 files at a time;
dip file listfollows the pages for you.