Knowledge
List your knowledge scopes
List every knowledge namespace your credential can read or write, with its scope type, entity and name, exactly as every knowledge route enforces them. Requires knowledge:read.
GET
List the caller's knowledge scopes
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.
v2 compatibility notes
GET /api/v2/knowledge/scopes/list lists the calling credential’s own knowledge scopes. It needs knowledge:read. The readable and writable sets are exactly the ones every knowledge route enforces for this credential (see Scope resolution), so a client can pick a scopeType and scopeId, or a source target, before it calls. MCP hosts call it with forge_list_knowledge_scopes.
Each item is { namespace, scopeType, entityId, label, readable, writable }: the namespace parsed into its scope type and entity (entityId is null for company and global), the entity’s name when one resolves (label, else null), and whether the credential may read and write it. Every scope is returned, in one response without limit, or in pages of limit with cursor. A credential that resolves no scope answers an empty list.
The scopes resolve from the credential, never from the request. The route takes no query parameter but limit and cursor; any other answers 400 bad_request.
Authorizations
Query Parameters
Response
The caller's knowledge scopes

