> ## 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. # Re-point, re-order, re-grant or disable a registered extension > Changes the endpoint, the points, the slots, the position, the grants or the enabled flag. Requires `extensions:manage`. **Widening a grant additionally requires the caller to hold that permission themselves**, so nobody hands an extension reach they do not have; narrowing one never does. **Four things here can reach the extension, and a disable outranks all four.** A moved `endpoint`, an explicit `refreshModels`, a `tool-server` slot this update claims that the row did not already hold, and — belonging to that slot alone — an `enabled` going from `false` to `true` on a row that already holds it. And then only for what the row has to answer for. A moved `endpoint` reads BOTH, the model list if the row claims `model-supplier` and the tool listing if it claims `tool-server`, because a new address is a new answer to both questions; `refreshModels` reads the model list alone; a newly-claimed `tool-server` slot, or an enable of a row already holding it, reads the tool listing alone — an enable being the moment this home starts serving that registration's tools, and the one road onto that which nothing else here checks. **Claiming `model-supplier` reaches it not at all by itself**: the claim alone stores that slot claimed and unserved, and `refreshModels` is what reads its catalogue, so an extension that verifies signatures is never called under a secret it does not hold yet. Everything else — a narrowed grant, a moved position, a changed point list, another slot, the switch itself — is a write against this home's own row that completes whether or not anything answers there. **Each of those reads FAILS CLOSED.** A model list or a tool listing this host asked for and could not read — a refused connection, a timeout, a non-`200`, a body that does not parse — answers `422` and changes nothing, rather than storing a claim it could not check. Either way, check the endpoint answers `/tools` — or `/models` for a supplier — under the secret it holds, then make the write again. **Carry `refreshModels: true` in the same body to claim the supplier slot and read its catalogue in one write**, so long as the row that update produces remains enabled. The flag outranks every other field the body carries but never the switch, so `{"slots": ["model-supplier"], "refreshModels": true}` does call the endpoint — the shortest correct road once the far side already holds the secret — while that same body carrying `"enabled": false` calls nothing at all and stores the claim unserved. Where the read does happen it is all or nothing: if it fails, the whole update answers 422 and **nothing is stored**, so the slot is never left claimed behind a read that did not happen. **When the row this update produces is switched off, nothing is asked of that address, however the body is written.** `{"enabled": false, "refreshModels": true}` and a disable that also moves the endpoint store the change and call nothing: the moment an owner most needs to disable an extension is the moment it has stopped answering, and a veto its subject can refuse by going quiet is not one. What such a body asked for is stored rather than performed — the new address and the newly claimed slot are on the row — and **re-enabling does not read the model list either**, because switching a row back on says nothing about what that address now serves. Send `refreshModels: true`, with the enable or after it, to read the list at the address the row now carries. The tool listing is the exception: an enable of a row holding `tool-server` reads it, as above. On a row Lerian installed (`installedByOperator`), `enabled` is the only field this may touch, in both directions. Off is the owner's standing veto and on again is allowed because re-enabling Lerian's own endpoint discloses nothing that was not disclosed when Lerian installed it. Every other field is refused: an owner who could re-point that endpoint could aim an operator-marked, Lerian-audited registration at an address of their own. ## OpenAPI ````yaml /en/openapi/v3-current/narya.yaml patch /v1/extensions/{publisher}/{name} 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/{publisher}/{name}: parameters: - $ref: '#/components/parameters/ExtensionPublisherParam' - $ref: '#/components/parameters/ExtensionNameParam' patch: tags: - extensions summary: Re-point, re-order, re-grant or disable a registered extension description: >- Changes the endpoint, the points, the slots, the position, the grants or the enabled flag. Requires `extensions:manage`. **Widening a grant additionally requires the caller to hold that permission themselves**, so nobody hands an extension reach they do not have; narrowing one never does. **Four things here can reach the extension, and a disable outranks all four.** A moved `endpoint`, an explicit `refreshModels`, a `tool-server` slot this update claims that the row did not already hold, and — belonging to that slot alone — an `enabled` going from `false` to `true` on a row that already holds it. And then only for what the row has to answer for. A moved `endpoint` reads BOTH, the model list if the row claims `model-supplier` and the tool listing if it claims `tool-server`, because a new address is a new answer to both questions; `refreshModels` reads the model list alone; a newly-claimed `tool-server` slot, or an enable of a row already holding it, reads the tool listing alone — an enable being the moment this home starts serving that registration's tools, and the one road onto that which nothing else here checks. **Claiming `model-supplier` reaches it not at all by itself**: the claim alone stores that slot claimed and unserved, and `refreshModels` is what reads its catalogue, so an extension that verifies signatures is never called under a secret it does not hold yet. Everything else — a narrowed grant, a moved position, a changed point list, another slot, the switch itself — is a write against this home's own row that completes whether or not anything answers there. **Each of those reads FAILS CLOSED.** A model list or a tool listing this host asked for and could not read — a refused connection, a timeout, a non-`200`, a body that does not parse — answers `422` and changes nothing, rather than storing a claim it could not check. Either way, check the endpoint answers `/tools` — or `/models` for a supplier — under the secret it holds, then make the write again. **Carry `refreshModels: true` in the same body to claim the supplier slot and read its catalogue in one write**, so long as the row that update produces remains enabled. The flag outranks every other field the body carries but never the switch, so `{"slots": ["model-supplier"], "refreshModels": true}` does call the endpoint — the shortest correct road once the far side already holds the secret — while that same body carrying `"enabled": false` calls nothing at all and stores the claim unserved. Where the read does happen it is all or nothing: if it fails, the whole update answers 422 and **nothing is stored**, so the slot is never left claimed behind a read that did not happen. **When the row this update produces is switched off, nothing is asked of that address, however the body is written.** `{"enabled": false, "refreshModels": true}` and a disable that also moves the endpoint store the change and call nothing: the moment an owner most needs to disable an extension is the moment it has stopped answering, and a veto its subject can refuse by going quiet is not one. What such a body asked for is stored rather than performed — the new address and the newly claimed slot are on the row — and **re-enabling does not read the model list either**, because switching a row back on says nothing about what that address now serves. Send `refreshModels: true`, with the enable or after it, to read the list at the address the row now carries. The tool listing is the exception: an enable of a row holding `tool-server` reads it, as above. On a row Lerian installed (`installedByOperator`), `enabled` is the only field this may touch, in both directions. Off is the owner's standing veto and on again is allowed because re-enabling Lerian's own endpoint discloses nothing that was not disclosed when Lerian installed it. Every other field is refused: an owner who could re-point that endpoint could aim an operator-marked, Lerian-audited registration at an address of their own. operationId: updateExtension requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/ExtensionUpdate' responses: '200': description: The registration as it now stands, without its secret. content: application/json: schema: $ref: '#/components/schemas/Extension' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': description: >- The caller's role does not carry `extensions:manage`, or the change widens a grant the caller does not hold, or it touches a field other than `enabled` on an operator-installed row (NRY-0028). content: application/json: schema: $ref: '#/components/schemas/Error' '404': $ref: '#/components/responses/NotFound' '409': description: >- The change claims an exclusive slot somebody else holds (NRY-0006, naming both) with no `[extensions] prefer` entry naming which of the two occupies it, or it moves this registration onto a position another one already occupies on a decision point they share (NRY-0004, naming both and the point), or — on a change whose resulting row is enabled and that moves the endpoint, claims the `tool-server` slot the row did not already hold, or switches on a row already holding that slot, the three changes that read the tool listing — the extension publishes a tool under a name this host already serves (NRY-0004, naming the tool). A refresh reads the model list, not the tools, and a disable reads nothing. content: application/json: schema: $ref: '#/components/schemas/Error' '413': $ref: '#/components/responses/RequestBodyTooLarge' '422': $ref: '#/components/responses/UnprocessableEntity' '500': $ref: '#/components/responses/InternalServerError' components: parameters: ExtensionPublisherParam: name: publisher in: path required: true description: >- The publisher half of the extension's namespaced name. The name is `publisher/extension` and travels as TWO path segments rather than one. The single-segment spelling is not broken — a generated client percent-encodes a path parameter's slash and the router decodes it back — so this is a deployment choice rather than a repair: an encoded slash is normalised or rejected by most reverse proxies a hosted home sits behind, and two segments read the way the name reads, `/v1/extensions/lerian/redactor`. schema: type: string pattern: ^[a-z0-9][a-z0-9-]*$ examples: - lerian ExtensionNameParam: name: name in: path required: true description: The extension half of the namespaced name. schema: type: string pattern: ^[a-z0-9][a-z0-9-]*$ examples: - redactor schemas: ExtensionUpdate: type: object description: >- What a change to a registration may carry. An omitted property is left alone; a change carrying nothing at all is refused rather than answered 200, because a caller who believes they changed something and did not is exactly who that saves. properties: endpoint: type: string format: uri points: type: array items: type: string slots: type: array items: type: string position: type: integer grants: type: array items: type: string models: type: array items: $ref: '#/components/schemas/ExtensionModel' enabled: type: boolean description: >- The owner's switch, and the only property this operation may carry on an operator-installed row. **Switching a `tool-server` row ON reads its tool listing**, and is refused `422` if that listing cannot be read or `409` if a name in it is one this home already serves. **The cost is stated rather than hidden**: an owner switching a tool server back on is held up while that endpoint is down, and must wait for it or drop the slot. **Switching OFF reaches the endpoint not at all**, in either direction of that rule and whatever else the same body carries. The moment an owner most needs to disable an extension is the moment it has stopped answering, so a kill switch that first waited on its own subject would work only while the thing it kills is healthy. refreshModels: type: boolean description: >- Ask this host to call the extension's list-models operation and replace the models stored on its registration. **On a supplier whose catalogue has never been read it is the FIRST read rather than a re-read**, and it is one of the two mechanisms that perform that first read: claiming `model-supplier` stores the slot unserved, and this flag is the direct way to make it serve anything at all. The other is a moved `endpoint` in the same update or a later one, which reads the list for its own reason — a new address is a new list — and so serves a claimed-and-unserved slot as a side effect. Either works only while the row the update produces is enabled. Send it once the far side holds the secret the registration response handed over. **It is a flag on a write rather than a background poll**, so the catalogue moves when the owner says it moved and nobody has to reason about a model list that changed on its own. The host also refreshes on its own when this update MOVES the endpoint, because a new address is a new list by definition. **Every other change contacts the extension not at all, with two exceptions this flag is not part of**: a `tool-server` slot this update claims that the row did not already hold reads that registration's tool listing, for the same reason a moved `endpoint` does — a new claim is a list this home has never read — and so does an `enabled` going from `false` to `true` on a row already holding that slot. A disable, a narrowed grant and a moved position are writes against a row in this home and complete whether or not anything answers at that address — which is what makes the owner's disable a kill switch that works at the moment it is most needed, rather than one that works only while the thing it kills is healthy. **Carried alongside `enabled: false`, this flag does nothing**, and neither does a moved endpoint in the same body: the resulting row is off, so this host asks that address nothing. The move is stored; the refresh is not deferred and not queued. Ask again — the flag on the update that switches the row back on, or on a later one — when the extension is live and you want its list read. examples: - enabled: false - refreshModels: true Extension: type: object description: >- An extension this host carries: a program this home REGISTERED at an HTTPS address. Never its secret, on any response that uses this schema. `package` is absent on a registered extension, which has no package — it is another deployment rather than anything installed here. required: - name properties: name: type: string description: Namespaced name, publisher/extension form. pattern: ^[a-z0-9][a-z0-9-]*\/[a-z0-9][a-z0-9-]*$ package: type: string description: >- The installed package that carries this extension. Absent for a registered extension, which has no package. description: type: string maxLength: 500 operations: type: array description: Operations invokable via POST /v1/extensions/{name}/invoke. items: type: object required: - name properties: name: type: string maxLength: 128 description: type: string maxLength: 500 endpoint: type: string format: uri description: The HTTPS address this host calls. points: type: array description: The decision points this extension sits on. items: type: string slots: type: array description: The slots it occupies. items: type: string position: type: integer description: Where it sits in the ordered pipeline, lowest first. grants: type: array description: >- The permission slugs granted ON this registration. An extension reaches every unmarked session in its home; a private one only where `sessions:read-private` is granted here. items: type: string models: type: array description: >- What a registered supplier serves. Absent unless the extension occupies a supplier slot — and absent there too while that slot is CLAIMED AND UNSERVED. A supplier with nothing here offers nothing to any turn: the catalogue skips such a row exactly as it skips a disabled one, so a slot nobody has served yet is not selectable and not a provider anybody sees. items: $ref: '#/components/schemas/ExtensionModel' servingTools: type: boolean description: >- Whether this home is serving the tools this registration publishes RIGHT NOW — that is, whether a model in this home can call them. Present on every extension that occupies the `tool-server` slot and absent on every one that does not, because it is a fact about that claim and about nothing else. It is false far more often than an owner expects, and that is the reason this field exists. The write that registers a tool server reaches the endpoint not at all, so the slot is stored CLAIMED AND UNSERVED and stays that way until a sweep has read the endpoint's tool listing; and a listing whose names collide with tools this home already serves is refused by the tool registry, which leaves the registration standing and publishing nothing. It is the last answer this home RECORDED, never a guess made at read time, so it survives a restart: a home brought back up under a standing collision still says it is refusing those tools rather than reporting them unread. notServingBecause: type: string description: >- Why this home is not serving that registration's tools, in this host's own words — never a sentence the far side wrote. Present exactly when `servingTools` is false, and absent when it is true, because a reason for something that is not the case would be the two fields disagreeing. It can say: that no sweep of this home has read the listing yet (every claim starts here, and a host built without a registered-extension pool stays here); that the tool registry refused the listing because another source already owns one of those names, naming both claimants; that the endpoint could not be reached or would not answer; that the listing carried no tool this host can serve; or that the owner has the registration switched off. enabled: type: boolean description: >- The owner's switch. A disabled registration is still listed, and still says where it pointed, because a registry that hid one would answer "what reads our conversations" with less than the truth. installedByOperator: type: boolean description: >- True when Lerian installed this on a home Lerian hosts, without the owner's act. It travels on every read because it is the notice standing where consent would otherwise be: a member can always tell which extensions are theirs and which are Lerian's. registeredBy: type: string description: >- The subject of the verified token that registered it. Absent on an operator install, where there is no person to name. registeredAt: type: string format: date-time examples: - name: lerian/redactor endpoint: https://redactor.example.com/narya points: - before-model-request - after-tool-call slots: - tool-definitions position: 10 grants: - sessions:read-private enabled: true installedByOperator: false registeredBy: user_01J8XQ registeredAt: '2026-09-17T10:04:00Z' 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. ExtensionModel: type: object description: >- One model a registered supplier serves. Stored on the registration rather than asked for per turn, because narya's catalogue holds no entry for a model it has never heard of. required: - id properties: id: type: string description: The id the endpoint itself accepts, with no "/" in it. maxLength: 128 name: type: string description: The label a picker shows. Absent falls back to the id. maxLength: 128 contextWindow: type: integer minimum: 0 maxOutput: type: integer minimum: 0 pricing: allOf: - $ref: '#/components/schemas/ExtensionModelPricing' description: >- What the model costs. **A model registered without it is refused**, and this is optional in the schema rather than required for that very reason: a required object arrives as a value that cannot be absent, so "no price" would reach the server indistinguishable from a price of zero — which means free. Absent means unknown and is refused; zero is a price and is accepted. ExtensionModelPricing: type: object description: >- What a model costs, in US dollars per million tokens, carried through unconverted so a value here reads against a published price page without arithmetic. **A model registered without one is refused, and zero is a price.** Absent means unknown, and a turn on an unpriced model reports no cost at all. A model that is genuinely free says so by carrying zeros. The field is OPTIONAL in `ExtensionModel` rather than required, and that is what makes the refusal reachable: a required object generates as a value that cannot be absent, so an omitted price would arrive indistinguishable from a price of zero and be stored as free. required: - input - output properties: input: type: number format: double minimum: 0 output: type: number format: double minimum: 0 cacheRead: type: number format: double minimum: 0 cacheWrite: type: number format: double minimum: 0 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' NotFound: description: The addressed resource does not exist on this host. 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. ````