The rules as a file for the repository
GET
/v1/memory/export
const url = 'https://beta-api.plune.ai/v1/memory/export';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://beta-api.plune.ai/v1/memory/export \ --header 'Authorization: Bearer <token>'The rules in force (#2198) as Markdown, rules.md - the file a repository keeps as plune/memory/rules.md, where an agent that works from the repository reads it. Each rule’s words quoted, with its source and who accepted it and when; no date of export, so the same rules make the same file. Any token reads it.
Authorizations
Section titled “Authorizations ”Responses
Section titled “ Responses ”The file
Media type text/markdown
string
Example
# Project memory
The rules a person accepted for this project in Plune. Exported from Plune; change them there - a new export replaces this file.
## 6f1c2b3a-0000-4000-8000-000000002198
> Which flow is the checkout: the one-page form or the three steps?> Answer: Three steps
Source: answer `6f1c2b3a-0000-4000-8000-0000000021a9`. Accepted by `6f1c2b3a-0000-4000-8000-0000000000a2` on 2026-09-16.No / invalid token or session