> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # Invoke an operation a registered extension exposes > The generic request lane for extension-defined behaviour, and the near half of the registered extension's own `invoke` operation: a client reaches an extension THROUGH this host, needing nothing but the extension's name and never holding its secret. The host signs the forwarded call under the registration's secret, judges the address on the way out and refuses a redirect; the payload is the extension's own contract and the host only routes it. **The address is configuration, not a credential.** `listExtensions` shows `endpoint` to every member of the organisation on purpose — a registry that hid where an extension points would answer "what is reading our conversations" with less than the truth — so what this lane withholds is the secret and the signature, not the URL. Knowing the address buys nothing without the secret: every call in the extension contract is signed, and an extension is required to refuse anything that does not verify. **An ordinary member's token is enough.** Invoking is using, and only registering is owning — `extensions:manage` gates the writes that create, re-point, revoke and re-order a registration. The forward runs under the same deadline a transformation gets. ## OpenAPI ````yaml /pt/openapi/v3-current/narya.yaml post /v1/extensions/{name}/invoke openapi: 3.1.0 info: title: Narya Host API version: 1.0.0 description: >- The contract between the Narya host and every client. One long-lived host serves this API over a Unix socket in your Narya home. The terminal client and the one-shot command that Lerian ships drive this API, and a client you write drives the same one. Requests authenticate with a bearer token issued by the identity provider the host is configured with. An operation that declares another security scheme also accepts that credential. A request without a valid credential gets 401 with NRY-0011. A caller whose role lacks the permission an operation needs gets 403 with NRY-0028. Submitting a message returns 202 with a turn id. Everything the turn produces streams over GET /v1/events as server-sent events with a typed envelope, and a stream resumes from a Last-Event-ID header. One error envelope: code, title and message. Codes are NRY- followed by four digits. Cursors are opaque. servers: [] security: - bearerAuth: [] tags: - name: host description: The host process itself — version, uptime, mode, store. - name: sessions description: Durable conversation containers. Archive, never destroy. - name: messages description: Submitting work into a session and interrupting it. - name: events description: The server-sent event stream every client consumes. - name: lanes description: Parallel tracks inside a session — main, subagent, side. - name: agents description: Named recipes — instructions, tools, model, policy. Read-only in v1. - name: ladder description: >- What a person can type: the skills and command files in force for one repository, and expanding one into text. Five origins merged, nearest winning a name, the repository's own rungs gated on trust. - name: permissions description: Pending permission asks, decisions, and the decision audit. - name: intercom description: Sessions on one machine finding and messaging each other. - name: packages description: The one thing a user installs — resources, Go code, or both. - name: extensions description: >- Host-side extensions and the operations each exposes over the wire. This is the generic lane a host extension uses to serve its own client half (a TUI component, a web panel) or any API-only consumer, without adding routes to this contract. - name: workflows description: Deterministic multi-agent orchestration runs. - name: providers description: Model suppliers, their auth state, and the model catalogue. - name: monitors description: >- Long-running watchers a session keeps beside its conversation — a test runner in watch mode, a build, a log being followed. Started by the model or by the person, always listed, always killable. - name: records description: The queryable local record of everything that happened. - name: environments description: >- Where a session's code lives and its commands run — this machine, or a container narya operates. A session that names none runs here. - name: schedules description: >- Work the host's own clock starts with nobody present — a repository, a prompt, a rule and what one fire may spend. Cancel, never destroy. - name: sharing description: >- Publishing a session from a developer's own home to the organisation's, and what is held back before a byte leaves the machine. - name: refinements description: >- What this owner has taught narya and allowed it to keep — distilled facts, and the skills, agents and commands the model wrote for itself. Propose, read, consent, roll back. Nothing here fires until a person answers. - name: platform description: >- Calls Lerian's control plane made to a home it hosts, as this home recorded them. paths: /v1/extensions/{name}/invoke: parameters: - name: name in: path required: true description: The extension's namespaced name, publisher/extension form. schema: type: string pattern: ^[a-z0-9][a-z0-9-]*\/[a-z0-9][a-z0-9-]*$ examples: - lerian/ring-review post: tags: - extensions summary: Invoke an operation a registered extension exposes description: >- The generic request lane for extension-defined behaviour, and the near half of the registered extension's own `invoke` operation: a client reaches an extension THROUGH this host, needing nothing but the extension's name and never holding its secret. The host signs the forwarded call under the registration's secret, judges the address on the way out and refuses a redirect; the payload is the extension's own contract and the host only routes it. **The address is configuration, not a credential.** `listExtensions` shows `endpoint` to every member of the organisation on purpose — a registry that hid where an extension points would answer "what is reading our conversations" with less than the truth — so what this lane withholds is the secret and the signature, not the URL. Knowing the address buys nothing without the secret: every call in the extension contract is signed, and an extension is required to refuse anything that does not verify. **An ordinary member's token is enough.** Invoking is using, and only registering is owning — `extensions:manage` gates the writes that create, re-point, revoke and re-order a registration. The forward runs under the same deadline a transformation gets. operationId: invokeExtension requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/ExtensionInvokeRequest' responses: '200': description: The operation's result, as the extension defined it. content: application/json: schema: $ref: '#/components/schemas/ExtensionInvokeResult' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '404': description: >- No enabled extension of that name, or no such operation on it (NRY-0013). The three causes are answered identically so a caller cannot enumerate this home's registry by watching which refusals differ. content: application/json: schema: $ref: '#/components/schemas/Error' '413': $ref: '#/components/responses/RequestBodyTooLarge' '422': $ref: '#/components/responses/UnprocessableEntity' '500': $ref: '#/components/responses/InternalServerError' components: schemas: ExtensionInvokeRequest: type: object description: A request to run one operation a host extension exposes. required: - operation properties: operation: type: string description: The operation name, as listed on the extension. maxLength: 128 payload: type: object description: Free-form input — the extension's own contract. additionalProperties: true examples: - operation: start-review payload: sessionId: 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d ExtensionInvokeResult: type: object description: The operation's result, as the extension defined it. properties: payload: type: object description: Free-form output — the extension's own contract. additionalProperties: true examples: - payload: accepted: true Error: type: object description: >- The single error envelope every operation returns. Codes are NRY- followed by four digits and are catalogued in the top-level x-error-catalog extension. required: - code - title - message properties: code: type: string pattern: ^NRY-[0-9]{4}$ description: Machine-readable error code from the NRY catalogue. title: type: string maxLength: 256 description: Short human-readable summary of the error class. message: type: string maxLength: 4096 description: Specific, actionable description of what went wrong. fields: type: object description: Per-field validation problems. additionalProperties: type: string examples: - code: NRY-0002 title: Session not found message: >- No session with id 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d exists on this host. responses: BadRequest: description: Malformed request — invalid parameter, cursor, or JSON body. content: application/json: schema: $ref: '#/components/schemas/Error' Unauthorized: description: >- Authentication required — a request carrying no valid identity token (NRY-0011). content: application/json: schema: $ref: '#/components/schemas/Error' RequestBodyTooLarge: description: >- The request body weighs more than this operation accepts (NRY-0024). The host holds one ceiling per operation and refuses at the door, in front of every handler: a body whose declared Content-Length is past the ceiling is refused before a byte of it is read, and a body that declares no length is read only as far as the ceiling and refused there. Nothing was read past that point and nothing was written. content: application/json: schema: $ref: '#/components/schemas/Error' UnprocessableEntity: description: The request was well-formed but failed validation. content: application/json: schema: $ref: '#/components/schemas/Error' InternalServerError: description: The host failed — including a store that refuses writes (NRY-0012). content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- Enforced on every transport, with no exempt operation. A person's request — over the default local unix socket exactly as over a TCP listener — must carry a JWT issued by the configured identity provider, which the host verifies itself against that issuer's key set: signature, issuer, expiry, and the person and organisation it names. Requests without a valid one receive 401 NRY-0011. The socket's file permissions are transport and are not an authorisation. ````