Sell a data product
How to sell a Dataset so a buyer, or its agent, trusts it before paying and pays only for what it finds.
A data buyer asks four questions before paying: how many records, how fresh, from where, and whether it may store them. A Dataset answers all four beside its price, then bills only for what a buyer finds.
Facts beside the price
| Fact | Ratebook's answer |
|---|---|
| Record count | Rates for about 13,000 taxing jurisdictions |
| Coverage | Every US address, by state, county, city and district |
| Last refresh and schedule | Each record's refreshedAt; every Source daily |
| Source | Each state's revenue department and each county's ordinances |
| License | internal by default; display and redistribute on a yearly Offer |
A commercial Source shows as a licensed provider, never by name. The facts sit on the pricing page, in the Portal and in the agent card.
How to price it
| Model | Price | Fits |
|---|---|---|
| Per lookup | $0.002 per billed hit | Checkouts and agents that call a key at a time |
| Monthly | $49 a month for 50,000 lookups, then overage | A steady checkout |
| Yearly license | A yearly fee for bulk delivery | display and redistribute buyers |
Only billed hits count: a miss is free, and the same key twice inside 24 hours counts once. Licensing your data covers what each license allows.
What a buyer's agent does
- It reads the Dataset's facts and the Offer from the agent card and the MCP server.
- It checks coverage for its own keys, for free.
- It accepts the Offer inside its Mandate, then looks up records over MCP.
A charge above its Mandate waits as an Approval on the buyer's side. Selling to agents has the exchange call by call.
Samples before money
A buyer tries the Dataset before it pays. A test key returns synthetic records in the real shape, and a free allowance per key returns real ones. Samples covers both.