Caper Wiki bronze

Search Wiki

Keyword search across the Caper knowledge base: the first call when you know what you are looking for but not where it lives. Matches titles and body prose, ranked in four tiers: titles starting with the term, titles containing it, literal body hits, then English full-text hits by relevance, which stem words and drop stopwords. Not semantic: one distinctive word beats a sentence. A query that finds nothing is retried with its misspelled words corrected, and `corrected` then names what was searched. Each row carries a `path`, its size in `chars` and a snippet windowed on the match. Feed the paths to get_pages in one call rather than looping get_page. Narrow with tagPath when a term is common. Defaults: page 1, pageSize 20 (max 50); keep paging while `hasMore` is true.

• What is a caper?
• How does the bonding curve work?
• Find pages about governance

Get Page

One page of the Caper knowledge base in full: its text, version, update date and metadata. Address it by `path` ("tag/path/slug", exactly the `path` or `url` a listing returns), or by `tagPath` + `slug`; a category's own path reads its hub article. Not a title. For 2 to 20 pages call get_pages, one round trip rather than N. A miss names the nearest pages, so a wrong guess is fixed in one retry. A page's URL with `.md` appended is its markdown. With `blocks: true`, `content` is the stored block array, ids and all, beside the page `id` and its whole `metadata`: read a page this way before editing it, and send its `version` back as the edit's baseVersion.

• Read the getting-started page
• Get the governance page

List Pages

Browse the Caper knowledge base by tag path rather than by keyword: every page under a branch, newest first by default. `tagPath` matches the branch and everything beneath it; omit it to walk the whole wiki. Sort by title for an A–Z pass. Same rows as search_wiki, with `totalPages`, `hasMore` and `nextPage`. Defaults: page 1, pageSize 20 (max 100).

Get Manifest

Step 3: a ready-to-sign transaction manifest. Kinds: create-caper, buy, sell, swap, create-proposal, vote, count, trigger, resolve, execute, activate-upgrade, exit, withdraw-founder, transfer-founder. Per-kind parameters – create-caper: name, cashtag, description, infoUrl?, iconUrl?, originToken? (resource address, vampire launch); buy: cashtag, xrd ($XRD to spend); sell: cashtag, tokens (caper tokens to sell); swap: from, to (cashtags), tokens (of `from` to sell) – one transaction that sells `from` into $XRD and buys `to` with it, so it pays the skim on both legs; create-proposal: cashtag, title, description, action (one action object, or an array of up to 4 the voters rank against each other and an always-appended "Do nothing"; each is { kind: "PAYOUT" | "INVEST" | "DIVEST" | "UPGRADE" | "METADATA" | "DEBATE", … }. METADATA rewrites the token's mutable metadata via metadataDescription / metadataIconUrl / metadataInfoUrl, at least one; DEBATE is a non-executable position in a debate – title and descr

• Launch a caper for my research project
• Buy 100 $XRD of $EXAMPLE and add a page to its wiki

Send Feedback

Tell the maintainers of Caper what you needed and did not find, what is wrong, or what broke. One issue per call, in 300 characters at most. Reports are read, not published.

• Report a page that is out of date

Get Ledger

This DAO's verified on-chain record: current treasury balances, the activity timeline (proposals, trades, executions), executed grants and payouts, and inter-DAO funding edges. This is ledger truth derived from settled transactions – prefer it over any wiki prose for balances, amounts, dates, and whether a proposal actually executed, because pages are human-authored and can lag. A proposal event carries `status` (the on-chain lifecycle state), `label` (its stage as the site names it) and, while one is due, `next`: the permissionless crank it waits on (count | trigger | resolve | execute), which the knowledge-base server's get_manifest builds under that kind and anyone may send. Defaults: limit 25 rows per section (max 100); each section reports `truncated` when the limit cut it, so raise `limit` rather than assuming the list is complete. This DAO's prose pages come from search_wiki / list_pages on this same endpoint; general Caper and DAO-governance reference lives on the knowledge-base server.

• What has $EXAMPLE's treasury paid out?
• Show $EXAMPLE's recent on-chain activity

Get Market

This DAO's live market state, read from the bonding curve and the swap mirror: price in $XRD, 24h change and volume, market cap, circulating vs total supply, curve allocation, holder count, and the most recent trades. Pass `candles` to also get OHLC history at one interval. Numbers are live reads – prefer them over any wiki prose, and over a stale earlier call. Every figure is denominated in the `network` the response names; on a testnet it is test $XRD and worth nothing. Defaults: trades 10 (max 50); candles omitted unless requested (last 100 per interval). Nothing here executes anything; to price a specific trade size, call quote_swap.

• What is $EXAMPLE trading at?
• How many tokens would 100 $XRD buy on $EXAMPLE?