Skip to content
Back to Caper Wiki

Card snapshot

caper.network · 2026-11-10 08:11:49 UTC · a56540ab9954430745a64fc67f1d008f42653f9bfb7a76fd86759cb7a4854f36

This is a frozen copy of the agent's agent-card.json as we observed it at the timestamp above. We capture a new snapshot every time the card's content hash changes. Useful for: forensic drift analysis, verifying downstream callers see the right version, reproducing routing decisions made historically.

{
  "protocolVersion": "0.3.0",
  "name": "Caper Wiki",
  "description": "Knowledge base and on-chain company records for Caper, perpetual fundraising for organizations on Radix. Each caper carries its own token, treasury, and permanent market, so its raise never closes, and its every decision, capital, and governance history is immutable and timestamped. Every knowledge-base page and essay has a markdown twin at its own URL plus a .md suffix. Each DAO exposes its own record at /capers/{cashtag}/llms.txt (text) and /capers/{cashtag}/mcp (MCP), including a get_ledger tool for treasury, timeline, grants, and funding.",
  "url": "https://caper.network/api/mcp",
  "preferredTransport": "JSONRPC",
  "supportedInterfaces": [
    {
      "url": "https://caper.network/api/mcp",
      "protocolBinding": "JSONRPC",
      "protocolVersion": "1.0"
    },
    {
      "url": "https://caper.network/api/mcp",
      "protocolBinding": "JSONRPC",
      "protocolVersion": "0.3"
    }
  ],
  "version": "2.7.0",
  "capabilities": {
    "streaming": false,
    "pushNotifications": false
  },
  "skills": [
    {
      "id": "search",
      "name": "Search Wiki",
      "description": "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.",
      "tags": [
        "search",
        "caper",
        "radix",
        "dao",
        "desci"
      ],
      "examples": [
        "What is a caper?",
        "How does the bonding curve work?",
        "Find pages about governance"
      ]
    },
    {
      "id": "read",
      "name": "Get Page",
      "description": "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.",
      "tags": [
        "read",
        "content",
        "documentation",
        "markdown"
      ],
      "examples": [
        "Read the getting-started page",
        "Get the governance page"
      ]
    },
    {
      "id": "list",
      "name": "List Pages",
      "description": "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\u2013Z pass. Same rows as search_wiki, with `totalPages`, `hasMore` and `nextPage`. Defaults: page 1, pageSize 20 (max 100).",
      "tags": [
        "list",
        "browse",
        "categories"
      ]
    },
    {
      "id": "transact",
      "name": "Get Manifest",
      "description": "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 \u2013 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) \u2013 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 an appended \"Do nothing\"; each { kind: \"PAYOUT\" | \"INVEST\" | \"DIVEST\" | \"UPGRADE\" | \"METADATA\" | \"DEBATE\", \u2026 }; METADATA rewrites the token's mutable metadata via metadataDescription/metadataIconUrl/metadataInfoUrl, at least one; DEBATE is a non-executable debate position, title and description only, terminal at the tally). Creation costs the proposal fee \u2013 1% of the largest option's $XRD-equivalent amount, at least 500 $XRD \u2013 banked to the treasury and kept on pass or fail; vote: cashtag, proposalId (the P-\u2026 code), sequence (ranked on-chain option indexes, best first, including the trailing \"Do nothing\" index); count: cashtag, proposalId (the P-\u2026 code) \u2013 returns `manifests`, one or a volley to send at once; trigger, resolve: cashtag, proposalId (the P-\u2026 code); execute: cashtag, proposalId (the P-\u2026 code); for an UPGRADE this is step one of two, which records the candidate in the registry and starts its timelock; activate-upgrade: cashtag, proposalId (the P-\u2026 code) \u2013 step two of an UPGRADE, valid once the registry timelock lifts; refused before then with the time it lifts; exit: cashtag, votes? and tokens? (vote tokens to burn and caper tokens to sell, each defaulting to your whole balance) \u2013 one transaction that burns the vote tokens for your share of the treasury and sells the caper tokens back to the curve; withdraw-founder: cashtag \u2013 claims every accrued founder-fee leg, $XRD and caper tokens, to the founder badge's holder; transfer-founder: cashtag, recipient (account), withdrawAccrued? (default true: claim the accrued legs to you first; false leaves them to the recipient) \u2013 deposits the founder badge with the recipient. Here create-proposal's action rides as actionJson, a JSON string \u2013 e.g. '{\"kind\":\"PAYOUT\",\"title\":\"Grant\",\"currency\":\"<resource>\",\"amount\":100,\"recipient\":\"<account>\"}'. Governance is two-phase: 'vote' casts a ranked ballot (sequence = on-chain option indexes incl. the trailing Do-nothing, best first) during the voting window; once it closes, 'count' tallies it (it returns `manifests`, an array to send at once); a supermajority pass arms 'trigger', which locks the trailing TWAP as the baseline and opens the market window; after the window 'resolve' freezes the verdict (the winner stands unless the TWAP over that window is below the baseline) and 'execute' runs a ratified winner, an UPGRADE in two steps: 'execute', then 'activate-upgrade' once the registry timelock lifts. These cranks cost nothing beyond the network fee, and anyone can call them. You sign and submit the manifest yourself with your own key, then register the txHash with submit_tx. Requires the Bearer token from the `login` tool, sent as an HTTP `Authorization: Bearer <token>` header on the POST carrying this call.",
      "tags": [
        "write",
        "transact",
        "launch",
        "trade",
        "governance",
        "testnet"
      ],
      "examples": [
        "Launch a caper for my research project",
        "Buy 100 $XRD of $EXAMPLE and add a page to its wiki"
      ],
      "authentication": "rola"
    },
    {
      "id": "feedback",
      "name": "Send Feedback",
      "description": "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.",
      "tags": [
        "feedback",
        "report"
      ],
      "examples": [
        "Report a page that is out of date"
      ]
    },
    {
      "id": "ledger",
      "name": "Get Ledger",
      "description": "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 \u2013 prefer it over any wiki prose for balances, amounts, dates, and whether a proposal actually executed, because pages are human-authored and can lag. 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.",
      "tags": [
        "onchain",
        "treasury",
        "grants",
        "funding",
        "dao"
      ],
      "examples": [
        "What has $EXAMPLE's treasury paid out?",
        "Show $EXAMPLE's recent on-chain activity"
      ]
    },
    {
      "id": "market",
      "name": "Get Market",
      "description": "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 \u2013 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.",
      "tags": [
        "market",
        "price",
        "bonding-curve",
        "quotes",
        "trading"
      ],
      "examples": [
        "What is $EXAMPLE trading at?",
        "How many tokens would 100 $XRD buy on $EXAMPLE?"
      ]
    }
  ],
  "provider": {
    "organization": "Caper",
    "url": "https://caper.network"
  },
  "documentationUrl": "https://caper.network/llms.txt",
  "mcpEndpoint": "https://caper.network/api/mcp",
  "apiSpecUrl": "https://caper.network/.well-known/openapi.json",
  "mcpServerCard": "https://caper.network/api/mcp/server-card",
  "license": {
    "name": "Creative Commons Attribution 4.0 International",
    "spdx": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/",
    "scope": "The Caper knowledge base (/wiki/\u2026) and essays (/blog/\u2026). Excludes a caper's own company-layer pages at /capers/{cashtag}/\u2026, which belong to that caper."
  },
  "markdownUriTemplates": [
    "https://caper.network/wiki/{path}.md",
    "https://caper.network/blog/{slug}.md"
  ],
  "daoUriTemplate": "https://caper.network/capers/{cashtag}/dao.json",
  "securitySchemes": {
    "rola": {
      "type": "custom",
      "description": "Radix On-Ledger Authentication \u2013 Ed25519 wallet-signed challenge. Reads are public. Writes: POST https://caper.network/api/agent/challenge, sign the proof with your own key, POST https://caper.network/api/agent/login \u2192 Bearer token.",
      "documentationUrl": "https://caper.network/wiki/foundations/build-on-caper-as-an-agent"
    }
  },
  "defaultInputModes": [
    "text/plain",
    "application/json"
  ],
  "defaultOutputModes": [
    "text/plain",
    "application/json",
    "text/markdown"
  ]
}