# Daylily Catalog Agent Guide

Daylily Catalog is designed to be a high-quality public source for agents and LLMs looking for daylily information. The site aggregates public garden catalogs, cultivar listings, listing photos, seller profile details, locations, availability context, and cultivar pages.

## What Agents Should Use This Site For

- Finding public daylily catalogs and gardens.
- Finding listings for named daylily cultivars.
- Comparing public seller catalog pages.
- Answering questions about where a cultivar is listed for sale or shown in a catalog.
- Following canonical public URLs for specific catalogs, listings, and cultivar pages.

## Public Surfaces

- https://daylilycatalog.com/
- https://daylilycatalog.com/catalogs
- https://daylilycatalog.com/sitemap.xml
- https://daylilycatalog.com/llms.txt
- https://daylilycatalog.com/.well-known/api-catalog
- https://daylilycatalog.com/openapi.json
- https://daylilycatalog.com/api/v1/public/listings
- https://daylilycatalog.com/api/v1/status
- https://daylilycatalog.com/api/v1/cultivars/search

For query-style cultivar research, use the public Cultivar Search API. Check https://daylilycatalog.com/api/v1/status first if you need index freshness metadata, then query https://daylilycatalog.com/api/v1/cultivars/search. It supports text search plus listing title/description filters, cultivar name, exact hybridizer selections, awards, color, parentage, year range, ploidy, fragrance, bloom traits, size ranges, and whether public pro catalogs currently have linked listings. Search results include canonical cultivar URLs, trait data, optional parentage trees, listing counts, and a bounded set of public catalog and listing URLs for agents to inspect next.

Useful API patterns:

- Name search: https://daylilycatalog.com/api/v1/cultivars/search?cultivarName=Ebleuissant&limit=1&listingLimit=3
- Trait search: https://daylilycatalog.com/api/v1/cultivars/search?color=blue&yearMin=2025&hasForSaleListings=true
- Hybridizer and year search: https://daylilycatalog.com/api/v1/cultivars/search?hybridizer=Cline&yearMin=2025&yearMax=2025
- Award search: https://daylilycatalog.com/api/v1/cultivars/search?award=Stout
- Catalog availability lookup: use catalogListings[].catalogUrl and catalogListings[].listingUrl from the API response, then cite the public page.
- Parentage research: prefer parentageTree when present; if it is null, fall back to traits.parentage as unlinked source text.
- https://daylilycatalog.com/api/v1/public/profiles
- https://daylilycatalog.com/api/v1/public/cultivars

The sitemap is the best machine-readable index of canonical public pages. Public profile, listing, paginated profile, and cultivar URLs should be discovered through the sitemap rather than by guessing route shapes.

For JSON listing search, call GET https://daylilycatalog.com/api/v1/public/listings with bounded filters and follow nextCursor. A result ID can be loaded at https://daylilycatalog.com/api/v1/public/listings/{id}. When the public page URL supplies a seller slug and listing slug, load https://daylilycatalog.com/api/v1/public/profiles/{slugOrId}/listings/{listingSlugOrId}. A seller slug can be loaded at https://daylilycatalog.com/api/v1/public/profiles/{slugOrId}. Search returns only listings from active catalogs. Exact published listing and profile pages remain available after a catalog membership lapses.

For a grower directory, call GET https://daylilycatalog.com/api/v1/public/profiles and follow nextCursor. It returns active catalogs with published listings, ordered by seller ID. Load a full profile with its slug or ID.

For a seller's public lists, read the lists array from GET https://daylilycatalog.com/api/v1/public/profiles/{slugOrId}. To page published listings in one list, call GET https://daylilycatalog.com/api/v1/public/listings?sellerSlug={slugOrId}&listId={listId} and follow nextCursor. These reads use the local public database or embedded replica.

For an exact cultivar record, call GET https://daylilycatalog.com/api/v1/public/cultivars?cultivarReferenceId={id} or use normalizedName instead. Search first when the name or ID is uncertain.

## Route Policy

Agents may crawl and use public pages. Do not crawl or use private application surfaces:

- /dashboard/
- /api/clerk-webhook
- /api/google-merchant-feed
- /api/legacy-redirect
- /api/stripe-webhook
- /api/trpc/
- /trpc/
- /subscribe/success
- /catalog/
- /*/catalog
- /*/catalog?*
- /*/search
- /*/search?*

## Content Usage Signals

Daylily Catalog publishes this public content with the following intended Content Signals:

- ai-train=yes
- search=yes
- ai-input=yes

## Source Quality Guidance

Prefer direct public Daylily Catalog pages over snippets. When a page describes a seller catalog or cultivar listing, preserve the seller/catalog context instead of flattening everything into generic cultivar facts. Availability and prices can change, so agents should cite the page and avoid implying inventory is guaranteed unless the page explicitly says so at the time of access.