Kalicart Global

Public machine-readable discovery for federated commerce catalogs

This host gives agents, retrievers, and crawlers a stable entry point for structured multi-merchant catalog discovery. It exists so systems do not have to infer commerce semantics by crawling unrelated storefront pages. No API key, no writes, no checkout. Capabilities, endpoint map, and inclusion rules live in the JSON — not in slogans.

GET https://global.kalicart.com/v1/global-catalog/discovery

Why this host exists

Semantic orientation: Kalicart Global exposes a single public discovery surface for agent-readable commerce data: scope, endpoints, profiles, and constraints are explicit instead of inferred from generic web pages.
Retrieval stability: Stable URLs, link relations, JSON-LD, .well-known documents, and vendor-aware JSON responses give crawlers and agents durable anchors for interpretation.

Scope and limits

Discovery kind: global_multi_merchant_catalog — aggregated browse/search. Product payloads include an explicit merchant object (who sells).
Federated discovery, merchant authority: This layer helps discover and compare eligible catalog records across merchants. The merchant remains the authority for the actual offer, product page, checkout, fulfillment, terms, and customer relationship.
Single-merchant catalogs: Store-scoped discovery uses https://dashboard.kalicart.com/v1/agent-bridge/{token} from that store’s own <link rel="kalicart-catalog">. It is orthogonal to this host; do not treat it as a hop for reading the global index.
Commerce handoff: Price and availability in responses are informational for discovery; purchase, tax, shipping, and PSP are always on the merchant storefront.

Governed publication

Omission over hallucination: Product attributes may be omitted when semantic confidence or applicability rules are insufficient. Missing fields are intentional boundaries, not invitations to invent values.
Publishability: Global visibility is sync-first and read-only: public records come from synchronized merchant catalogs, explicit eligibility rules, and opt-out controls.

Contracts and machine-readable entry

Discovery JSON — primary contract; same body with GET / and Accept: application/json, application/ld+json, or application/vnd.kalicart.global-discovery+json.
kalicart-discovery-profile.json — semantics and separation from merchant bridge.
kalicart-global-discovery.json — stable bootstrap pointer (RFC 8615).
llms.txt — bootstrap order and endpoint table for tools.
sitemap.xml — crawl hints; discovery remains the agent entry.
Human narrative (www) — longer prose on why the global layer exists; behavior still defers to discovery JSON.

Prefer discovery + profile over this HTML when implementing clients. Kalicart · merchant dashboard at dashboard.kalicart.com