> ## Documentation Index > Fetch the complete documentation index at: https://cadenya.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # List objective tool calls > Every tool an objective invoked, what it was called with, and whether it ran. The endpoint a bare-tool harness polls. One row per tool invocation, carrying the arguments the model chose and where the call stands. This is what a [bare tool](/docs/api-reference/objectiveservice/set-a-bare-tool-calls-content) harness polls, and what an approval UI reads. ```typescript TypeScript theme={null} const calls = await client.objectives.toolCalls.list(objectiveId, { workspaceId }); for await (const call of calls) { const c = call.data.callable; console.log(c.type === 'tool' ? c.tool.name : c.type, call.executionStatus); } // GenerateFake TOOL_CALL_EXECUTION_STATUS_COMPLETED // GenerateFake TOOL_CALL_EXECUTION_STATUS_COMPLETED // GetFakerOptions TOOL_CALL_EXECUTION_STATUS_COMPLETED // GenerateFake TOOL_CALL_EXECUTION_STATUS_COMPLETED // GenerateFake TOOL_CALL_EXECUTION_STATUS_COMPLETED ``` ```go Go theme={null} calls := client.Objectives.ToolCalls.ListAutoPaging(ctx, objectiveID, cadenya.ObjectiveToolCallListParams{WorkspaceID: cadenya.String(workspaceID)}) for calls.Next() { call := calls.Current() fmt.Println(call.Data.Callable.Tool.Name, call.ExecutionStatus) } // GenerateFake TOOL_CALL_EXECUTION_STATUS_COMPLETED // GetFakerOptions TOOL_CALL_EXECUTION_STATUS_COMPLETED ``` ```ruby Ruby theme={null} calls = cadenya.objectives.tool_calls.list(objective_id, workspace_id: workspace_id) calls.auto_paging_each do |call| puts [call.data.callable.tool&.name, call.execution_status].join(" ") end # GenerateFake TOOL_CALL_EXECUTION_STATUS_COMPLETED # GetFakerOptions TOOL_CALL_EXECUTION_STATUS_COMPLETED ``` ```bash cURL theme={null} curl "https://api.cadenya.com/v1/workspaces/${WORKSPACE_ID}/objectives/${OBJECTIVE_ID}/tool_calls" \ -H "Authorization: Bearer ${CADENYA_API_KEY}" ``` ## Two statuses, and they sit on the call `status` answers "may it run." `executionStatus` answers "did it." Both are **top-level**, not inside `data`, which is easy to get wrong because everything else lives under `data`. ```typescript theme={null} call.status; // TOOL_CALL_STATUS_AUTO_APPROVED call.executionStatus; // TOOL_CALL_EXECUTION_STATUS_COMPLETED call.data.arguments; // { "name": "company.name" } ``` A tool with `requiresApproval: false` reads `AUTO_APPROVED` before it ever runs. One behind [approval](/docs/api-reference/objectiveservice/approve-a-tool-call) sits at `TOOL_CALL_STATUS_WAITING_FOR_APPROVAL` until a person decides, then moves to `APPROVED` or `DENIED`. Both filter server-side: ```typescript theme={null} const parked = await client.objectives.toolCalls.list(objectiveId, { workspaceId, executionStatus: 'TOOL_CALL_EXECUTION_STATUS_WAITING_FOR_CONTENT', }); ``` That one filter is the bare-tool harness: every call waiting on your code, and nothing else. ## The list omits results. Get by ID returns them. A list row holds `callable`, `arguments`, and the two statuses. It carries no `result`, so paging a long objective stays cheap. [Get a tool call](/docs/api-reference/objectiveservice/get-an-objective-tool-call-by-id) returns the same call plus `result`, at the **top level** rather than under `data`, with no `includeInfo` needed. The response schema is named `ObjectiveToolCallWithResult`, which tells you where the line falls. ```typescript theme={null} const call = await client.objectives.toolCalls.retrieve(toolCallId, { workspaceId, objectiveId }); console.log(JSON.stringify(call.result)); // {"content":[{"text":{"text":"{\"name\":\"company.name\",\"value\":\"Weissnat, Weissnat and Weissnat\"}"}}]} ``` | You want | Read | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | What was the tool called with? | This endpoint, `data.arguments` | | Was it approved, and did it run? | This endpoint, `status` and `executionStatus` | | What did it return? | [Get a tool call](/docs/api-reference/objectiveservice/get-an-objective-tool-call-by-id), `result`, or the `toolResult` event from [List objective events](/docs/api-reference/objectiveservice/list-objective-events) | ## `callable` names what was invoked A discriminated union, like an [assignment](/docs/api-reference/agentvariationservice/add-an-assignment-to-a-variation): `type` reads `tool`, `agent`, or `cadenyaProvidedTool`, and the payload sits under the matching key. ```typescript theme={null} const c = call.data.callable; switch (c.type) { case 'tool': c.tool.name; // 'GenerateFake' case 'agent': c.agent.name; // a sub-agent case 'cadenyaProvidedTool': c.cadenyaProvidedTool.name; // 'get_memory' } ``` Unlike the [`toolCalled` event](/docs/api-reference/objectiveeventstreamsservice/stream-objective-events), which ships a built-in's `name` empty, this endpoint fills it in. When a transcript rendered from the stream hits an unnamed built-in, this is where its name lives. ## `resolvedSecrets` gives the key and source, never the value Each entry gives the secret's `key` and which scope supplied it, so you can prove a per-user token overrode a workspace credential without the value ever crossing the wire. ```json theme={null} { "key": "EXAMPLE_TOKEN", "source": "RESOLVED_SECRET_SOURCE_OBJECTIVE" } ``` Sources rank `RESOLVED_SECRET_SOURCE_OBJECTIVE`, then `_TOOLSET`, then `_WORKSPACE`: the narrowest scope wins. The array is empty when the tool needs no secrets. ## The harness loop ```typescript theme={null} const parked = await client.objectives.toolCalls.list(objectiveId, { workspaceId, executionStatus: 'TOOL_CALL_EXECUTION_STATUS_WAITING_FOR_CONTENT', }); for await (const call of parked) { const result = await runItYourself(call.data.arguments); await client.objectives.toolCalls.setContent(call.metadata.id, { workspaceId, objectiveId, content: [{ type: 'text', text: { text: JSON.stringify(result) } }], }); } ``` Poll, execute, answer. Cadenya never opens a connection into your network. ## Related Answer a parked call. Your code is the tool runtime. Where `WAITING_FOR_APPROVAL` gets resolved. The same call, plus its `result`. What `resolvedSecrets.source` is telling you. ## OpenAPI ````yaml get /v1/workspaces/{workspaceId}/objectives/{objectiveId}/tool_calls openapi: 3.1.0 info: title: Cadenya API description: API for the Cadenya Agent Runtime platform. version: '1.0' servers: - url: https://api.cadenya.com description: Production server security: - bearerAuth: [] tags: - name: AIProviderKeyService - name: APIKeyService description: |- Issue, rotate, disable, and revoke a workspace's API keys. Every key belongs to exactly one workspace; the system-managed global account key is managed via GlobalAPIKeyService instead. - name: AccountService description: >- Manage the authenticated account. Accounts are the top-level organizational unit and contain one or more workspaces. - name: AgentScheduleService description: >- Manage recurring schedules attached to agents. Schedules trigger objectives on a cadence defined by AgentScheduleSpec.Schedule. - name: AgentService description: >- Manage AI agents within a workspace. Agents define AI behavior and tool access. - name: AgentVariationService description: >- Manage variations of an agent and their tool, sub-agent, and memory layer assignments. - name: GlobalAPIKeyService description: |- Manage the account's system-provisioned global API key. The global key is the only key that spans every workspace; it is created by the system and cannot be deleted, so the surface is retrieve, rotate, and the disable/enable kill switch. - name: MemoryService description: >- Manage memory layers and their entries. Layers are named containers that can be composed into an objective's memory cascade; entries are the keyed values within a layer. System-managed layers (e.g., episodic layers created by the runtime) cannot be mutated through this API. - name: ModelService description: |- Manage LLM models available to a workspace. Models represent provider and family pairs (e.g., "anthropic/claude-sonnet-4.6"). Workspaces are seeded with the supported models and you can enable or disable each one. - name: ObjectiveEventStreamsService - name: ObjectiveService - name: ProfilesService description: |- Operations on profiles, the account-level principals (users, API keys, system) that authenticate against the API. - name: SearchService - name: TenantService description: >- Read and erase tenants and the subjects under them. Tenants and subjects are created by assertion — on objective creation or widget session mint — never directly, so this service has no create or update: it exists to enumerate what assertions have produced, and to destroy it on request. - name: ToolService description: >- Manage tool sets and the tools they contain. Tool sets group related tools, and tools define specific capabilities available to agents. When a tool set is managed, only API key actors can modify its tools; human (profile) actors cannot. - name: UploadService description: |- Issue short-lived presigned URLs for direct client-to-object-storage uploads. Created uploads can be referenced by id when creating or updating resources that accept binary content (e.g., MemoryEntry). - name: WidgetService description: |- Manage embeddable chat widgets. A widget binds an agent to a globally unique hostname with a per-widget origin allowlist; browsers reach it with session tokens minted via WidgetSessionService. - name: WidgetSessionService description: >- Mint and manage widget sessions. Session creation is server-to-server only: the customer's backend authenticates its visitor, asserts tenant/subject context, attaches any per-visitor secrets, and receives a short-lived bearer token the browser uses against the widget host. - name: WorkspaceAdminService description: >- Administer workspaces across the account: create and archive workspaces and manage their membership. These operations are account-scoped and require the admin role (a token whose profile holds the WorkOS admin role); they live under /v1/account/workspaces rather than the workspace-scoped /v1/workspaces tree so an admin can manage any workspace in the account, including ones they are not themselves a member of. - name: WorkspaceSecretService - name: WorkspaceService description: |- Manage workspaces within an account. Workspaces provide organizational grouping and isolation for resources such as agents, tools, and API keys. This is the workspace-scoped, end-user surface. Administrative operations (create / archive workspaces, manage members) live in WorkspaceAdminService under /v1/account/workspaces and require the admin role. paths: /v1/workspaces/{workspaceId}/objectives/{objectiveId}/tool_calls: get: tags: - ObjectiveService - Objectives summary: List objective tool calls description: Lists all tool calls for an objective operationId: ObjectiveService_ListObjectiveToolCalls parameters: - name: workspaceId in: path required: true schema: type: string example: workspace_01HXKD2E5NQM3T9AYWCF133E3Q - name: objectiveId in: path description: The objective ID to return tool calls for required: true schema: example: obj_01HXKD2E5NQM3T9AYWCFQAZGFV type: string - name: limit in: query description: Maximum number of results to return schema: type: integer format: int32 - name: cursor in: query description: Pagination cursor from previous response schema: type: string - name: status in: query description: Filter by tool call status schema: enum: - TOOL_CALL_STATUS_UNSPECIFIED - TOOL_CALL_STATUS_AUTO_APPROVED - TOOL_CALL_STATUS_WAITING_FOR_APPROVAL - TOOL_CALL_STATUS_APPROVED - TOOL_CALL_STATUS_DENIED type: string format: enum - name: includeInfo in: query description: When set to true you may use more of your alloted API rate-limit schema: type: boolean - name: executionStatus in: query description: |- Filter by tool call execution status. Useful for reverse-harness polling of bare tool calls waiting for externally supplied content (TOOL_CALL_EXECUTION_STATUS_WAITING_FOR_CONTENT). schema: enum: - TOOL_CALL_EXECUTION_STATUS_UNSPECIFIED - TOOL_CALL_EXECUTION_STATUS_PENDING - TOOL_CALL_EXECUTION_STATUS_RUNNING - TOOL_CALL_EXECUTION_STATUS_COMPLETED - TOOL_CALL_EXECUTION_STATUS_ERRORED - TOOL_CALL_EXECUTION_STATUS_WAITING_FOR_CONTENT type: string format: enum - name: labels in: query description: |- Filters by metadata labels. Comma-separated key=value pairs, e.g. "env=prod,team=ai". A resource matches only if every pair matches exactly (AND semantics). schema: type: string responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/ListObjectiveToolCallsResponse' default: description: Default error response content: application/json: schema: $ref: '#/components/schemas/Status' x-codeSamples: - lang: JavaScript source: >- import Cadenya from '@cadenya/cadenya'; const client = new Cadenya({ apiKey: process.env['CADENYA_API_KEY'], // This is the default and can be omitted }); // Automatically fetches more pages as needed. for await (const objectiveToolCall of client.objectives.toolCalls.list( 'obj_01HXKD2E5NQM3T9AYWCFQAZGFV', { workspaceId: 'workspace_01HXKD2E5NQM3T9AYWCF133E3Q' }, )) { console.log(objectiveToolCall.data); } - lang: Python source: |- import os from cadenya import Cadenya client = Cadenya( api_key=os.environ.get("CADENYA_API_KEY"), # This is the default and can be omitted ) page = client.objectives.tool_calls.list( objective_id="obj_01HXKD2E5NQM3T9AYWCFQAZGFV", workspace_id="workspace_01HXKD2E5NQM3T9AYWCF133E3Q", ) page = page.items[0] print(page.data) - lang: Go source: "package main\n\nimport (\n\t\"context\"\n\t\"fmt\"\n\t\"go.cadenya.com/cadenya-go\"\n\t\"go.cadenya.com/cadenya-go/option\"\n)\n\nfunc main() {\n\tclient := cadenya.NewClient(\n\t\toption.WithAPIKey(\"My API Key\"),\n\t)\n\tpage, err := client.Objectives.ToolCalls.List(\n\t\tcontext.TODO(),\n\t\t\"obj_01HXKD2E5NQM3T9AYWCFQAZGFV\",\n\t\tcadenya.ObjectiveToolCallListParams{\n\t\t\tWorkspaceID: cadenya.String(\"workspace_01HXKD2E5NQM3T9AYWCF133E3Q\"),\n\t\t},\n\t)\n\tif err != nil {\n\t\tpanic(err.Error())\n\t}\n\tfmt.Printf(\"%+v\\n\", page)\n}\n" - lang: Ruby source: |- require "cadenya" cadenya = Cadenya::Client.new(api_key: "My API Key") page = cadenya.objectives.tool_calls.list( "obj_01HXKD2E5NQM3T9AYWCFQAZGFV", workspace_id: "workspace_01HXKD2E5NQM3T9AYWCF133E3Q" ) puts(page) - lang: CLI source: |- cadenya objectives:tool-calls list \ --api-key 'My API Key' \ --workspace-id workspace_01HXKD2E5NQM3T9AYWCF133E3Q \ --objective-id obj_01HXKD2E5NQM3T9AYWCFQAZGFV components: schemas: ListObjectiveToolCallsResponse: type: object properties: items: type: array items: $ref: '#/components/schemas/ObjectiveToolCall' pagination: $ref: '#/components/schemas/Page' Status: type: object properties: code: type: integer description: >- The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code]. format: int32 message: type: string description: >- A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client. details: type: array items: $ref: '#/components/schemas/GoogleProtobufAny' description: >- A list of messages that carry the error details. There is a common set of message types for APIs to use. description: >- The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors). ObjectiveToolCall: required: - metadata - data - status - executionStatus type: object properties: metadata: $ref: '#/components/schemas/OperationMetadata' data: $ref: '#/components/schemas/ObjectiveToolCallData' status: enum: - TOOL_CALL_STATUS_UNSPECIFIED - TOOL_CALL_STATUS_AUTO_APPROVED - TOOL_CALL_STATUS_WAITING_FOR_APPROVAL - TOOL_CALL_STATUS_APPROVED - TOOL_CALL_STATUS_DENIED type: string description: Current status of the tool call format: enum info: $ref: '#/components/schemas/ObjectiveToolCallInfo' executionStatus: readOnly: true enum: - TOOL_CALL_EXECUTION_STATUS_UNSPECIFIED - TOOL_CALL_EXECUTION_STATUS_PENDING - TOOL_CALL_EXECUTION_STATUS_RUNNING - TOOL_CALL_EXECUTION_STATUS_COMPLETED - TOOL_CALL_EXECUTION_STATUS_ERRORED - TOOL_CALL_EXECUTION_STATUS_WAITING_FOR_CONTENT type: string format: enum description: >- ObjectiveToolCall is a record of a tool call made during an objective's execution. Tool calls are mutable — their status changes as they are approved, denied, or executed. Page: type: object properties: nextCursor: type: string description: >- Page carries cursor-based pagination state. There is no total: the cursor walks the result set without ever counting it, and a count would cost a second query on every list. GoogleProtobufAny: type: object properties: '@type': type: string description: The type of the serialized message. additionalProperties: true description: >- Contains an arbitrary serialized message along with a @type that describes the type of the serialized message. OperationMetadata: required: - id - accountId - workspaceId - profileId - createdAt type: object properties: id: readOnly: true type: string description: >- Unique identifier for the operation (prefixed ULID, e.g., "obj_01HXK...") accountId: readOnly: true example: account_01HXKD2E5NQM3T9AYWCFTJHJVF type: string description: >- Account this operation belongs to for multi-tenant isolation (prefixed ULID) workspaceId: readOnly: true example: workspace_01HXKD2E5NQM3T9AYWCF133E3Q type: string description: >- Workspace this operation belongs to for organizational grouping (prefixed ULID) labels: type: object additionalProperties: type: string description: |- Key-value pairs for categorization and filtering. Values are 0-63 alphanumeric characters with "-", "_", or "." allowed between; keys follow the same shape and additionally accept an optional DNS-subdomain prefix (e.g. "cadenya.com/") of at most 253 characters. Examples: {"priority": "high", "source": "api", "workflow": "onboarding"} createdAt: readOnly: true type: string description: |- Timestamp when this operation was created ULID includes timestamp information, but this explicit field enables easier querying format: date-time externalId: type: string description: >- External ID for the operation (e.g., a workflow ID from an external system) profileId: readOnly: true example: profile_01HXKD2E5NQM3T9AYWCFS0AP08 type: string description: >- ID of the actor (user or service account) that created this operation description: >- Metadata for ephemeral operations and activities (e.g., objectives, executions, runs) ObjectiveToolCallData: required: - callable type: object properties: callable: allOf: - $ref: '#/components/schemas/CallableTool' description: The tool that was called arguments: type: object additionalProperties: true description: The arguments passed to the tool memo: type: string description: A memo supplied by the reviewer when denying the tool call statusChangedBy: readOnly: true allOf: - $ref: '#/components/schemas/Profile' description: >- The profile that changed the status of this tool call. Set when the status is changed to APPROVED or DENIED by a user. resolvedSecrets: readOnly: true type: array items: $ref: '#/components/schemas/ResolvedSecret' description: List of resolved secrets used by the tool call ObjectiveToolCallInfo: type: object properties: objective: $ref: '#/components/schemas/OperationMetadata' createdBy: $ref: '#/components/schemas/Profile' tool: $ref: '#/components/schemas/BareMetadata' toolSet: $ref: '#/components/schemas/BareMetadata' CallableTool: oneOf: - $ref: '#/components/schemas/CallableTool_Tool' - $ref: '#/components/schemas/CallableTool_Agent' - $ref: '#/components/schemas/CallableTool_CadenyaProvidedTool' discriminator: propertyName: type mapping: tool: $ref: '#/components/schemas/CallableTool_Tool' agent: $ref: '#/components/schemas/CallableTool_Agent' cadenyaProvidedTool: $ref: '#/components/schemas/CallableTool_CadenyaProvidedTool' description: >- CallableTool is a union that represents a tool that can be called by an agent. In Cadenya, a tool that is used within an agent objective might be a user-defined tool (IE: MCP, HTTP), another Agent (useful to separate context), or a Cadenya Tool (one Cadenya provides). Profile: required: - metadata - spec type: object properties: metadata: $ref: '#/components/schemas/AccountResourceMetadata' spec: $ref: '#/components/schemas/ProfileSpec' description: |- A profile identifies a user or non-human principal (such as an API key) at the account level. Profiles are account-scoped and can be granted access to multiple workspaces. ResolvedSecret: type: object properties: key: type: string source: enum: - RESOLVED_SECRET_SOURCE_UNSPECIFIED - RESOLVED_SECRET_SOURCE_WORKSPACE - RESOLVED_SECRET_SOURCE_TOOLSET - RESOLVED_SECRET_SOURCE_OBJECTIVE type: string format: enum description: >- ResolvedSecret is a resolved secret value from the workspace, toolset, or objective. When a tool is called, it will rely on secrets in the order of: - Objective - Toolset - Workspace BareMetadata: type: object properties: id: readOnly: true type: string name: readOnly: true type: string description: >- Human-readable name of the referenced resource, populated by the server on reads for convenience. Absent on references to resources that do not have a name (e.g., objective tasks). description: |- BareMetadata contains the minimal metadata for a resource: the ID and an optional human-readable name. These are used for reference fields where the full metadata (account scoping, timestamps, labels, external IDs) is not needed — e.g., the tool references inside an agent variation spec or the tools assigned to an objective. Both fields are server-populated; clients provide IDs through sibling fields rather than by constructing a BareMetadata themselves. CallableTool_Tool: type: object required: - type - tool properties: type: type: string enum: - tool tool: $ref: '#/components/schemas/ResourceMetadata' CallableTool_Agent: type: object required: - type - agent properties: type: type: string enum: - agent agent: $ref: '#/components/schemas/ResourceMetadata' CallableTool_CadenyaProvidedTool: type: object required: - type - cadenyaProvidedTool properties: type: type: string enum: - cadenyaProvidedTool cadenyaProvidedTool: $ref: '#/components/schemas/ResourceMetadata' AccountResourceMetadata: required: - id - accountId - name - profileId type: object properties: id: readOnly: true type: string description: >- Unique identifier for the resource (prefixed ULID, e.g., "apikey_01HXK...") accountId: readOnly: true example: account_01HXKD2E5NQM3T9AYWCFTJHJVF type: string description: >- Account this resource belongs to for multi-tenant isolation (prefixed ULID) name: type: string description: >- Human-readable name for the resource (e.g., "Customer Support Agent", "Email Tool") Required for resources that users interact with directly externalId: type: string description: >- External ID for the resource (e.g., a workflow ID from an external system) labels: type: object additionalProperties: type: string description: |- Key-value pairs for categorization and filtering. Values are 0-63 alphanumeric characters with "-", "_", or "." allowed between; keys follow the same shape and additionally accept an optional DNS-subdomain prefix (e.g. "cadenya.com/") of at most 253 characters. Examples: {"environment": "production", "team": "platform", "version": "v2"} profileId: readOnly: true example: profile_01HXKD2E5NQM3T9AYWCFS0AP08 type: string createdAt: readOnly: true type: string format: date-time description: >- AccountResourceMetadata is used to represent a resource that is associated to an account but not to a workspace. ProfileSpec: required: - type type: object properties: email: type: string description: >- Email address of the profile. Required and unique within an account for user profiles. name: type: string description: Display name (e.g., "Bobby Tables"). type: enum: - PROFILE_TYPE_UNSPECIFIED - PROFILE_TYPE_USER - PROFILE_TYPE_API_KEY - PROFILE_TYPE_SYSTEM type: string description: >- Whether this profile represents a human user, an API key, or a system principal. format: enum description: Configuration for a profile. ResourceMetadata: required: - id - accountId - workspaceId - name - profileId - createdAt type: object properties: id: readOnly: true type: string description: >- Unique identifier for the resource (prefixed ULID, e.g., "agent_01HXK...") accountId: readOnly: true example: account_01HXKD2E5NQM3T9AYWCFTJHJVF type: string description: >- Account this resource belongs to for multi-tenant isolation (prefixed ULID) workspaceId: readOnly: true example: workspace_01HXKD2E5NQM3T9AYWCF133E3Q type: string description: >- Workspace this resource belongs to for organizational grouping (prefixed ULID) name: type: string description: >- Human-readable name for the resource (e.g., "Customer Support Agent", "Email Tool") Required for resources that users interact with directly externalId: type: string description: >- External ID for the resource (e.g., a workflow ID from an external system) labels: type: object additionalProperties: type: string description: |- Key-value pairs for categorization and filtering. Values are 0-63 alphanumeric characters with "-", "_", or "." allowed between; keys follow the same shape and additionally accept an optional DNS-subdomain prefix (e.g. "cadenya.com/") of at most 253 characters. Examples: {"environment": "production", "team": "platform", "version": "v2"} profileId: readOnly: true example: profile_01HXKD2E5NQM3T9AYWCFS0AP08 type: string description: ID of the actor (user or service account) that created this resource createdAt: readOnly: true type: string description: Timestamp when this resource was created format: date-time updatedAt: readOnly: true type: string description: Timestamp when this resource was last updated format: date-time description: >- Standard metadata for persistent, named resources (e.g., agents, tools, prompts) securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT ````