Restore Component

Catalog prerequisites

This operates on the database-backed component catalog configured on AgentOS, not on the in-code agents, teams or workflows lists. It requires a supported synchronous BaseDb adapter with component methods.

Published components can be readable across scoped owners, while writes remain owner-scoped; a visible foreign or shared row can still reject a write with 403. Draft versions require preview access. Saving configuration does not validate model credentials, run tools or deploy a service.

Restore an archive

Restoration reinstates the archived component and its retained versions. An already-active component returns 409. Active dependency validation can also prevent restoration with 409; a visible shared component can reject an owner-scoped write with 403.

Restoration does not promise to recreate every related runtime object or undo separate deletions.

POST/components/{component_id}/restore

Restore an archived (soft-deleted) component by ID.

Authorization

HTTPBearer
AuthorizationBearer <token>

In: header

Path Parameters

component_id*Component Id

Component ID

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl --request POST 'https://example.com/components/string/restore'
{  "component_id": "string",  "component_type": "agent",  "name": "string",  "user_id": "string",  "description": "string",  "current_version": 0,  "metadata": {},  "created_at": 0,  "updated_at": 0,  "deleted_at": 0}