Point your agent harness at the MXTK Data Exchange MCP. Ask for a cohort; get the bundle, quality report, licence and price. The owner sets the reserve, the buyer accepts the DUA, and the exchange records the receipt.
Your agent does the diligence. You keep the pen.
Create a scoped agent token. Your agent gets the catalogue, quotes and DUA — not your password or payment authority.
Search by cohort, geography, licence and unit. Read the quality report and the data use agreement.
The agent prepares the checkout. You accept the DUA and create the deal; the agent never signs for you.
The buyer recomputes the manifest root. A receipt is written before delivery is accepted.
Our agent gives you an indicative seller range in minutes. It is not a promise: deeper evaluation covers schema, completeness, consent, licence and buyer demand.
Sell it on the exchange, or keep the asset and explore MXTK RWA. You choose.
List a de-identified bundle, set a reserve, and let buyers compete.
Retain the asset and explore how it fits the MXTK RWA stack.
Explore the handoff →The old model is simple: an intermediary buys or aggregates data, then resells it. The original owner often has no price, no visibility and no ongoing say. We are building the opposite: if you own the data, you should be able to price it, license it and get paid.
Not every data broker operates the same way. The problem is the default: the person closest to the data is usually the last person paid. We put the owner in the transaction, with a price and a contract.
Package the cohort, the components, the licence and the evidence. Let buyers see exactly what they are getting before the first call.
Your agent searches, compares and prepares. You read the DUA, approve the deal, and check the delivery against the manifest before money moves.
A listing is a claim. A quality report is a measurement. A manifest is a commitment. A receipt proves the buyer received the bytes that match it.
That is the difference between a data marketplace and a folder of links.
Connect your agent harness over MCP. The token is scoped to your organization, expires, and can be revoked. It can discover and prepare; it cannot accept the DUA or pay.
A DUA is a contract. Payment is a transfer. Neither belongs to an agent. The agent returns an approval link; the portal records who accepted, when and for which listing.
Scoped tokens, expiry, revocation and audit. No organization key in a chat.
No listing fee. The exchange earns when a deal closes.
of gross, paid on the deal. The seller sets a reserve per unit; nothing clears below it.
of gross, all-in. The buyer sets a ceiling per unit; nothing clears above it.
A traditional broker often buys or aggregates data and resells it, with little direct payment or visibility for the original owner. On MXTK Data Exchange the owner is the seller: they set the reserve, the licence is recorded, and they are paid when a deal clears. We do not take title to the data or resell it.
A DUA is the contract that says what the buyer may do with the data: the permitted use, term, territory and restrictions. On MXTK Data Exchange it is generated from the listing licence and must be accepted before checkout.
No. Sellers must de-identify before upload and attest to the method. The platform screens and quarantines failures; it is a fail-safe, not a de-identification proof.
It holds encrypted staging and active objects, not rows in Postgres. Buyers receive a delivery file and a manifest; the exchange stores the commitment and the receipt.
It can discover, compare, quote and prepare a checkout. A human must accept the DUA and approve the payment; the agent never signs for you.
The exchange records the deal and a settlement entry. Card payment is handled by the payment provider identified at checkout.
Give your agent the market. Keep the signature.
