LogitAtlas
Delivery is where most data deals fall apart. The listing was perfect, the price was agreed, escrow is funded, and now the seller has to actually hand over the data in a way the buyer can trust and the seller can repeat. A modern marketplace standardises delivery into three modes. Picking the right one is a product decision as much as a technical one.
Mode 1: Secure file transfer
The platform hosts the files. The seller uploads them during listing or at the moment of sale. The buyer receives signed, time-limited download URLs on fund release. The platform handles storage, checksums, and expiry. The seller never has to run infrastructure.
This mode is the right default for most datasets. It works well for labelled corpora, historical snapshots, documents, and any file-based deliverable. Buyers trust it because the download URL is clearly tied to the order ID and expires if not used.
- Best for: static snapshots, labelled sets, historical data, archives.
- Operating cost for seller: close to zero after upload.
- Buyer experience: predictable, no setup, download and audit.
Mode 2: Seller-hosted link
The seller keeps the data where it already lives, often an S3 bucket or similar object store. The marketplace reveals the private URL to the buyer only after escrow is funded. This is the right mode for very large datasets that would be inefficient to upload to the marketplace, and for sellers who have strong internal controls over their object store.
The tradeoff is that the seller is responsible for availability and for making sure the link stays valid for the agreed access window. The marketplace helps by keeping the URL confidential, but cannot force a seller's bucket to be reachable.
- Best for: multi-terabyte datasets, data governed by the seller's existing storage policies.
- Operating cost for seller: moderate; must maintain the storage and signed URLs.
- Buyer experience: still simple, but hinges on seller uptime.
Mode 3: Scoped API credentials
Instead of delivering a snapshot, the seller delivers access to an API. The marketplace issues the credentials to the buyer with the scope and duration agreed in the listing. The seller rotates or revokes keys through the dashboard without renegotiating the deal.
This mode is the right choice for continuously refreshing data where the buyer benefits from live access. Examples include weather observations, foot-traffic indices, enrichment APIs, and price feeds. The seller gets ongoing engagement data, which helps them pitch an upsell when the subscription renews.
- Best for: feeds, enrichment services, anything the buyer calls into their own systems.
- Operating cost for seller: real; must maintain the API, monitor rate limits, support buyers.
- Buyer experience: integrates with their stack but requires engineering time to adopt.
Should you support more than one mode?
Yes, if your dataset lends itself to it. A common pattern is to offer both a flat-fee snapshot and a subscription API that stays current. Buyers who need to experiment buy the snapshot. Buyers who go into production renew the API. The two tiers rarely cannibalise each other and together they maximise your addressable market.
What buyers actually look for in each mode
- File transfer: checksum, file manifest, and a schema document in the archive.
- Hosted link: proof of availability (uptime SLA, status page), expected access window, data residency.
- API credentials: rate limits, authentication method, SDK or openapi document, test environment.
The delivery mode you pick is the first thing a buyer thinks about. It is also the first thing they will complain about if you get it wrong.
Common delivery mistakes
- Promising API delivery and then shipping a one-time file export because the API is not ready.
- Using a seller-hosted link to a staging bucket that gets wiped weekly.
- Forgetting to include the schema or data dictionary with a file transfer.
- Issuing API credentials with no documented scope, forcing the buyer to guess what endpoints are allowed.
- Not revoking credentials when a subscription lapses, exposing both sides to compliance risk.
Operating a reliable delivery pipeline
Delivery becomes an operational practice as soon as you have more than a handful of orders. The sellers who do best treat each mode as a product with runbooks: who to call when storage fails, how to rotate credentials, how to re-send a signed URL. The marketplace helps by logging every delivery and every re-send, but the seller's own habits determine how smooth the experience feels.