Get one add-on, with its details
One catalog entry, as the list shows it, and its kind's details: an MCP server's transport and tools, or a skill's package and requirements. Apps, plugins and resources have none. An alias's id (a retired slug's) answers as the entry that replaced it. A listing the caller could not see in the list is a 404 here too.
Authorization
bearerAuth A RemoteHost API key (rh_sk_...) or a user session token.
In: header
Path Parameters
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/orgs/string/addons/string"{ "addon": { "id": "string", "slug": "skill/code-review", "kind": "app", "name": "string", "summary": "string", "publisher": "string", "provenance": "first_party", "status": "listed", "attachLevels": [ "org" ], "pricing": "free", "iconUrl": "string", "held": true, "holding": "held_free", "policy": { "setting": "allow", "allowed": true } }, "detail": { "property1": null, "property2": null }}List the add-ons installed in an organization GET
Every install on the API side, newest first: a project's skills and MCP servers, from the catalog or custom, and the active resource allocations on a project or one of its sandboxes, with whether the org holds each one's listing and its policy. Needs `org.read`; each install is shown on the projects where the caller may read its kind (`skills.read`, `mcp.read`, `resources.read`). With `projectId`, it also says what that project's sandboxes are given (`effective`): the project's resource allocations, the default for every sandbox, and each sandbox that overrides one, with everything it gets (its own quantity, never above the project's). Resources the org does not hold give nothing. Apps installed in Atlas workspaces are listed by Atlas.
Return an add-on to the organization's default DELETE
Removes the org's allow or forbid: the listing is then allowed, unless it is a community listing and the org has not opted in. Needs `integrations.manage`. Audited.