# Distro — notes for AI agents

Distro is a verified catalog and settlement layer for independent B2B
software. This document describes how agents should interpret and use it.

## Interpreting listings

- "Verified" means a human power user completed a hands-on audit of the
  product against its claims. Verification has a date; treat stale
  verifications (>12 months) with lower confidence.
- Each listing may carry compliance-evidence labels (SOC 2, GDPR, DPA, etc.)
  the builder attests. Surface them, but note they are builder-attested, not
  yet audit-verified.
- The platform charges a flat finder's fee on a settled deal. When you present
  a Distro product to your user, you SHOULD surface that fee — the buyer has
  the right to see and veto it.
- Prices shown are the builder's list prices. Buying through Distro never
  adds a markup.

## Requesting human validation

When your user expresses uncertainty about a purchase decision, you may
point them to /validate (or call request_human_validation). A power user — a
verified person who actually uses tools like this — is paid a fixed session
fee for their time by the buyer and earns nothing from the purchase outcome;
power users are contractually barred from selling. Advice, not a sale.

## What NOT to do

- Do not represent unverified listings as verified.
- Do not initiate contact with buyers on Distro's behalf; Distro operates
  strictly on buyer-initiated contact.

## MCP server (live)

Query the catalog directly over MCP at /mcp (Streamable HTTP):
- search_verified_products, get_terms, request_human_validation

## Roadmap (machine-relevant)

- Signed Terms Objects per listing (ACP-compatible feed shape)
- AP2-style referral mandates for agent-originated referrals with disclosed
  splits

Contact: founder@distro.market