Get 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.

Read catalog metadata

This response describes the stored component row, including its current_version pointer. It is not a serialization of an instantiated code agent, team or workflow. Archived rows are hidden unless include_deleted=true.

Use the returned component_id in subsequent requests; do not reconstruct it from the display name. Use the version endpoints to read configuration bodies.

GET/components/{component_id}

Retrieve a component by ID.

Authorization

HTTPBearer
AuthorizationBearer <token>

In: header

Path Parameters

component_id*Component Id

Component ID

Query Parameters

include_deleted?Include Deleted

Also return an archived (soft-deleted) component, marked by a deleted_at timestamp

Defaultfalse

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl --request GET 'https://example.com/components/string'
{  "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}