The Distribution console & syndication matrix

Each listing is shown against the real distribution surfaces: the server-rendered public page with structured data, the machine formats (.md/.json), the llms-full.txt entity catalog, the /llms-network.txt syndication feed, sitemaps and search indexing, Kariant’s own AI answer surfaces, listing embeds and distribution links, and KDN ad units.

Every status is derived from your actual listing state — publish status, your plan stamp, an active featured window, the distribution links you have actually created, and your own opt-out switches. Statuses read Live (serving now), Plan-gated (published but excluded from that surface on your current plan — Kariant’s own AI answer surfaces require Kariant AI; embeds, distribution links, and KDN require Agentic), Pending (publish to enter), or Opted out (you switched that surface off for the listing). Nothing in the matrix is estimated. Note that the machine corpus itself (/llms-network.txt and its variants) carries every published listing regardless of plan, with tier as a data field — plan tier changes the richness of the syndicated record, and gates Kariant’s own AI surfaces.

The report lists your distribution links with their server-counted clicks — the placement data that exists for your account today. If you have not created links or embeds, the report says so instead of showing placeholder numbers. Embed impressions and KDN ad requests are recorded server-side, and per-placement reporting for those surfaces lands in the console as that reporting rail is wired. On the public partner site, Embeds and KDN are labeled Beta while that rail matures.

Embed attribution is now signature-verified end to end: listing-card snippets are server-signed when a publisher copies them, and unsigned or tampered embeds render unattributed (fail-closed) instead of crediting anyone. Your listing still displays either way — the signature protects who gets credit.

Three levers control inclusion. Publish/unpublish is the master switch — removal is immediate on every surface, including the machine corpus. Your plan tier flips AI-surface, embed, and KDN eligibility, and the richness of your syndicated corpus record. And each listing carries three per-surface opt-out switches in the console: the AI syndication feed (llms-network), embeds & KDN units, and distribution links. Inclusion is default-on — every published listing is in until you switch a surface off. Flipping a switch records only that preference on your listing; the server rails honor it on their next content refresh, and switching back on restores inclusion the same way.