Historical component index
Example identifiers, categories, decade labels and editorial source-note status. Quarterly cadence is illustrative only.
Make the lawful purchase path easy to discover.
A fictional/composite sample for a specialist data publisher: human access summary, intended-use decisions, field catalog, custom machine-readable policy, human enquiry routing and a dated change log.
Fictional sample: “Atlas Parts Archive” is a composite business created only to demonstrate the workflow. This page makes no claim about a real publisher, dataset, licence, endpoint, record count, customer or commercial result. The JSON is a custom example—not an industry standard, contract or crawler-control mechanism.
1. Human access summary
The short version is readable by a buyer, an agent operator and the publisher’s reviewer. It routes ambiguous use to a person instead of silently granting or denying rights.
Fictional publisher
Atlas Parts Archive
A composite specialist archive used only for this readiness sample.
- Ordinary browsing and search discovery: refer to the approved human terms.
- Prompt-time retrieval, bulk export or API use: submit a request with scope and volume.
- Model training, fine-tuning, resale or redistribution: not pre-authorized.
- When the intended use is unclear: route to human review.
Decision owner
No automated licensing approval
Every request records dataset/fields, intended use, geography, users, volume, retention, attribution and start date. A publisher owner—and customer/counsel where needed—approves final terms.
2. One “AI allowed” flag is not enough
Six use cases stay separate. These statuses are workflow labels in a fictional sample; they do not create legal rights.
| Intended use | Sample status | What the requester should do | What this does not mean |
|---|---|---|---|
| Ordinary human browsing | Refer to human terms | Read the publisher-approved terms. | Not a new licence from this page. |
| Search discovery / short reference | Refer to human terms | Confirm scope, attribution and limits. | Not blanket permission for bulk copying. |
| Prompt-time retrieval | Request required | Describe fields, users, volume and retention. | Not a promised API or endpoint. |
| Bulk export / API access | Request required | Ask for a scoped commercial decision. | Not proof that a bulk product is available. |
| Model training / fine-tuning | Not pre-authorized | Obtain a separate written decision. | Public visibility does not establish training rights. |
| Resale / redistribution | Not pre-authorized | Obtain a separate written decision. | No downstream rights are implied. |
3. Publish a purchasable surface—not imaginary availability
The fictional catalog names two possible data products and eight example fields. Record counts are left null, and every delivery status remains enquiry_only_not_promised.
Cross-reference notes
Example source/candidate identifiers, evidence status and last-reviewed date. No compatibility conclusion is claimed.
Custom JSON + field CSV
Policy discovery and buyer qualification are structured, while owner and customer/counsel review remain mandatory.
4. Founder-readable five-bullet review
1
Lead with the data product and buying route
A bot note or llms.txt alone is not the offer. Name the datasets, fields, intended uses and human decision path.
2
Keep approved human terms authoritative
A custom JSON file can improve discovery and routing. It does not replace terms, grant a licence or provide legal advice.
3
Separate discovery, retrieval, bulk use and training
Different use cases need distinct review states. Avoid a misleading universal “AI allowed” boolean.
4
Leave unconfirmed inventory visibly unknown
Do not invent API availability, prices, record counts, rights or update guarantees merely to make the catalog look complete.
5
Version the decision surface
Record effective date, owner, evidence reference and review status so machine-readable copy does not silently drift from approved terms.
5. The bounded paid scope
A$149–299 Agent-readable Access & Licensing Readiness Review
One public/redacted data-product surface, returned in 48–72 hours with a human access summary, intended-use matrix, custom machine-readable policy example, field catalog, enquiry-routing brief, source/change log, safe-claims edits and one intake path.
One public/redacted data-product surface, returned in 48–72 hours with a human access summary, intended-use matrix, custom machine-readable policy example, field catalog, enquiry-routing brief, source/change log, safe-claims edits and one intake path.
Promote gate
Three qualified publishers request a custom pack, or one publisher pays for a setup after approved distribution.
Kill gate
Publishers do not control a licensable product, only want a free crawler firewall, or ten approved high-specificity touches produce no commercial conversation.
Boundary: workflow and product-readiness only. No legal opinion, rights determination, contract drafting, security assessment, crawler blocking, robots enforcement, pay-per-crawl setup, API implementation, licence grant, revenue uplift or agent/crawler compliance guarantee.