Skip to main content
POST
Create a repository memory note

Authorizations

Authorization
string
header
required

Your Reason API key from Settings > API. New keys use reason_; legacy ara_ keys remain accepted. Keys are capability-scoped: run, mcp:read, mcp:write, secrets:read, secrets:write, sessions:read, sessions:debug, knowledge:read, memory:read, memory:write, skills:read, skills:write, repos:read, repos:write, reviews:read, reviews:write, deployment:read, analytics:read, org:read, org:write, attachments:read, attachments:write, guardrails:read, guardrails:write, automations:read, automations:write, agent_auth:read. mcp:write manages MCP server configuration only; it does not authorize remote MCP-tool execution. sessions:debug is privileged: it expands diagnostic session events only for organization owners/admins.

Path Parameters

orgId
string
required

Organization id or slug. Resolve it with GET /v3/self.

Body

application/json
repo
string
required
content
string
required

Non-empty explicit memory content. It is trimmed before storage and limited to 240 KiB UTF-8.

provider
enum<string>
Available options:
github
title
string

Optional title. It is trimmed, defaults to 'Memory note' when omitted or blank, and must be at most 160 characters.

Response

Created.

repo
string
provider
enum<string>
Available options:
github
item
object

An explicit editable note for one connected repository.