privacy_score is present and the trust service evaluates clean.
The seller ran AIM Data’s local PII scan and no detectable personal data was found.
AIM Data
AIM Data runs on your own infrastructure. It profiles your data, scans for PII, scores quality, writes the listing for you, and gives builders a local developer surface for catalog search, transaction handoff, and peer-to-peer delivery. You review, you publish, and your raw data stays where it is.
Trust signals
AIM Data listings use nullable privacy and quality scores. A missing score means the scan did not run, and the marketplace says that plainly.
privacy_score is present and the trust service evaluates clean.
The seller ran AIM Data’s local PII scan and no detectable personal data was found.
privacy_score is present and the trust service flagged possible personal data.
The seller ran the scan, AIM Data found content that may be personal data, and the seller acknowledged the flag at publish time.
privacy_score is null.
The seller has not enabled the local PII scan on this listing. We do not fake a clean signal when it is missing.
quality_score is present.
The seller ran AIM Data’s local quality grading. The numeric score surfaces alongside the badge.
quality_score is null.
The seller has not enabled local quality grading on this listing.
“Not run” is an honest buyer signal. The seller has not yet enabled the local PII scan on this listing. AIM Data offers a one-click scan that runs on the seller’s own machine. We do not run it for them, and we do not fake a clean signal when it is missing.
How it works
Python or Docker. Local-first. Nothing leaves your machine during install.
AIM Data profiles structure, detects PII, scores quality, and prepares listing metadata on your infrastructure.
You review the generated metadata and listing copy. Only the listing goes live; raw data stays with you.
When a buyer purchases, ai.market issues a signed delivery token that your AIM Data instance honors.
Developer surface
AIM Data is the local control point for sellers, buyers, and partner platforms. The same local-first conduit supports the non-dev GUI and the developer surface: CLI, SDK, MCP server, and encrypted peer-to-peer delivery.
ai.market coordinates discovery, billing, delivery tokens, and transaction records. AIM Data keeps private keys, raw data, queries, results, and payload movement under endpoint control.
Use the non-dev GUI for seller workflows, or run AIM Data through the CLI, SDK, MCP server, or Docker for application integrations.
Each AIM Data instance generates an Ed25519 keypair locally. The private key stays on your infrastructure.
Query ai.market by capability, schema, license, price, and quality score, then connect catalog access to your user workflows.
Present the signed delivery token and connect directly over an encrypted peer-to-peer channel. Payloads never touch ai.market.
Script installs, local enrollment, listing preparation, catalog queries, and delivery checks from terminal workflows.
Embed AIM Data workflows inside your own product for search, authorization, listing, and transaction handoff.
Expose catalog search and marketplace workflows to AI agents through a local server controlled by your infrastructure.
Keep raw payload movement between buyer and seller endpoints with signed tokens and encrypted peer-to-peer transfer.
Install
Download the AIM Data desktop app when the installer link is available, run it on the machine that can reach your data, then configure the connection locally. Current command-line install paths are below and may require Docker Desktop or OrbStack.
Run the installer from a terminal, then follow the local setup prompts.
curl -fsSL https://get.ai.market/aim-data | bashRun from PowerShell, then configure your local data connection.
irm https://get.ai.market/aim-data/windows | iexUse a Python-native install path or containerized deployment for local control-plane operation.
Enough for local scans, integration workflows, and peer-to-peer connectivity.
Outbound access to the ai.market API plus peer-to-peer connectivity for delivery sessions.
Full documentation is being consolidated with the AIM Data release process. Until then, keep the setup local: install the app or developer surface, connect the data source, enroll the local Ed25519 identity, run scans, review the generated listing, then publish or connect peer-to-peer.
Not a seller? You might want Find Data, or our Partner Program.