Developers / Data
Plant correctness data for agents and garden tools
Plotwright publishes a free, versioned JSON feed beside the human catalog so downstream tools can ground plant advice in the same source-cited climate, native-range, and provenance contract.
License
Free with attribution
The public correctness feed is licensed CC-BY-4.0. Attribute reused data as "Plotwright, https://plotwright.com" and keep links back to the source pages when your interface can show them.
Open feed index
Commercial use
Talk to us before high-volume integration
Small public reuse is ungated. Commercial, bulk, or high-volume integrations should start on this page and contact Plotwright so rate limits, attribution, and support expectations are explicit.
Contact Plotwright
Endpoints
Feed index
/plants/index.json
Lists every plant and genus/species hub record, with schemaVersion, license, coverage, canonical page paths, and per-record JSON paths.
Per-plant record
/plants/<botanical-slug>.json
A place-independent correctness record for one catalog page. Use the canonicalPath in the index rather than inventing slugs.
Schema descriptor
/plants/schema.json
JSON Schema for the index document. Consumers should gate on schemaVersion before assuming fields are stable.
Correctness contract
Botanical names stay literal
Scientific names and structured enum values are not translated. Localized pages change surrounding copy, not the machine record contract.
Climate values are edges, not guesses
Hardiness and heat values describe an honest envelope. Plotwright does not collapse a zone range to a midpoint just to make a page look simpler.
Provenance travels with the claim
Records expose sources and citation pointers so downstream tools can show where a fact came from instead of flattening it into anonymous advice.
Version policy
Read schemaVersion first
The feed index advertises schemaVersion and schemaPath before the record listings. Consumers should check those fields before reading record bodies, cache the index as the contract root, and treat unknown future versions as a review trigger rather than silently guessing.
Read the data methods