The public showcase listing
Every **published** showcase entry, newest publication first. **No bearer token is required** — a showcase anyone can read is the whole point of the public artifact loop (§6.1 loop 1). Only entries whose creator opted in appear. A draft, a withdrawn entry, and a foreign entry are all absent, and their absence is indistinguishable: this route has no owner dimension, so it cannot reveal that a particular person has unpublished work. The `total` field counts everything matching the filter, not the page, so a client can tell "that is all of them" from "that is the first page".
Every published showcase entry, newest publication first. No bearer token is required — a showcase anyone can read is the whole point of the public artifact loop (§6.1 loop 1). Only entries whose creator opted in appear. A draft, a withdrawn entry, and a foreign entry are all absent, and their absence is indistinguishable: this route has no owner dimension, so it cannot reveal that a particular person has unpublished work. The total field counts everything matching the filter, not the page, so a client can tell "that is all of them" from "that is the first page".
Query Parameters
Filter to one Kit. Omit for every Kit.
Value in
- "business"
- "community"
- "contracts"
- "creator"
- "launch"
- "trust"
- "agent"
How many entries to return, newest first. Defaults to all.
1 <= value <= 100Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/showcase"{ "entries": [ { "id": "string", "slug": "string", "kit": "business", "title": "string", "summary": "string", "projectUrl": "string", "chain": "ethereum", "token": "string", "templateOptIn": true, "remixCount": 0, "publishedAt": "string" } ], "total": 0}The referral-on-rails loop's status GET
The configuration state of the referral-on-rails loop (§6.1 loop 4): whether it is switched on, the share and period it would pay, and — when it cannot run — exactly which piece is missing. **No bearer token is required.** These are deployment facts, not user data. The loop is **off by default** and the share and period are **both 0** by default, because the plan fixes neither a share nor a period. A non-null `unavailableReason` is the normal answer, not an error: it is the honest report of a loop whose economics have not been decided. `paidFromTreasury` is always `false`. The plan requires a referral to be paid from the rail and never from treasury up front, and the field is the literal `false` so the document carries that invariant rather than leaving it to prose. There is deliberately no `POST` here that records a referrer or pays one. Putting a guessed share into a live fee split is the thing §5.2 does not decide, so this module publishes the configuration the real loop will read and stops there.
One published showcase entry GET
One published showcase entry, as the **public** shape. **No bearer token is required.** The public shape has no `ownerId` and no `status` field at all, rather than nullable ones: a public entry is published by construction, and the identity of the creator is not on the wire in any form, so there is nothing to filter and nothing to leak. A draft, a withdrawn entry, a foreign entry, and a slug that never existed all answer with the same 404.