For data brokers
Send it the way it already moves.
Your team does not need a new pipeline to open a new channel. Tell us how the data leaves your systems today, and we wire that path into the desk.
Ways to send data in
API push
Post rows to a keyed door over HTTPS. Best for data that changes through the day.
Storage bucket
Drop exports in a bucket the desk reads on a schedule. Best for nightly or hourly batches.
File drops
Send CSV or JSON files on a schedule: a full dump, or only what changed.
SFTP
Push files to an SFTP drop, if that is how your systems already deliver.
Upload by hand
Upload a CSV, or a zip of CSVs, from the Data tab of your DRM3 account. Good for a first look.
Have a path that is not on this list? Tell us. If your systems can export it, we can take it in.
What we need from you
- A sample of the data, or a description of its fields.
- Which fields say what a record is, when it happened and where it came from.
- How often it changes.
- Who may read it.
Updates and corrections
Each delivery is turned into signals and indexed for search. Send a full replacement or only the changes. A correction replaces the version before it, and the earlier version stays on the record, so a buyer can always see what changed.
Ways your buyers get data out
The desk
Search by meaning, filters, and a page for every signal with its source behind it.
Alerts and digests
Watchlists that email a buyer when something new matches, daily or weekly.
The API
Signals, search and sections as JSON, with a playground and an OpenAPI document.
Agents
An MCP door for AI agents, and a plain-text edition of the desk a model can read.
The key is yours
The desk reads your data with a key that belongs to that desk alone, and you can revoke it at any time. More on how your data is protected.
Have a customer in mind?
Tell us about them and their data, and we will show you what their desk would look like.