API for Agent Registry Control¶

ABAP Package	`/AWS1/API_TCE`
ABAP SDK "TLA"	`TCE`
ABAP Interface	`/AWS1/IF_TCE`

The "TLA" is a Three Letter Abbreviation that appears in ABAP class names, data dictionary objects and other ABAP objects throughout the AWS SDK for SAP ABAP. The TLA for Agent Registry Control is TCE. This TLA helps squeeze ABAP objects into the 30-character length limit of the ABAP data dictionary.

Installation¶

To install the AWS SDK for SAP ABAP, import the Core transport, along with the transport for the Agent Registry Control module and other API modules you are interested in. A few modules are included in the Core transport itself. For more information, see the Developer Guide guide.

About The Service¶

AWS Agent Registry is a managed catalog for publishing and discovering resources such as MCP servers, agents, and agent skills. Agent Registry Control is its control-plane API: use it to create and manage registries and the records they contain, configure discovery and authorization, govern record approval and curation workflows, and manage automatic detection of resources. Data-plane search and MCP invocation operations are provided by the companion Agent Registry API.

Using the SDK¶

In your code, create a client using the SDK module for Agent Registry Control, which is created with factory method /AWS1/CL_TCE_FACTORY=>create(). In this example we will assume you have configured an SDK profile in transaction /AWS1/IMG called ZFINANCE.

DATA(go_session)   = /aws1/cl_rt_session_aws=>create( 'ZFINANCE' ).
DATA(go_tce)       = /aws1/cl_tce_factory=>create( go_session ).

Your variable go_tce is an instance of /AWS1/IF_TCE, and all of the operations in the Agent Registry Control service are accessed by calling methods in /AWS1/IF_TCE.

API Operations¶

For an overview of ABAP method calls corresponding to API operations in Agent Registry Control, see the Operation List.

Factory Method¶

`/AWS1/CL_TCE_FACTORY=>create( )`¶

Creates an object of type /AWS1/IF_TCE.

IMPORTING¶

Optional arguments:¶

`iv_protocol` `TYPE /aws1/rt_protocol` `/AWS1/RT_PROTOCOL`¶

`io_session` `TYPE REF TO /aws1/cl_rt_session_base` `/AWS1/CL_RT_SESSION_BASE`¶

`iv_region` `TYPE /aws1/rt_region_id` `/AWS1/RT_REGION_ID`¶

`iv_custom_endpoint` `TYPE /aws1/rt_endpoint` `/AWS1/RT_ENDPOINT`¶

RETURNING¶

`oo_client` `TYPE REF TO /aws1/if_tce` `/AWS1/IF_TCE`¶

/AWS1/IF_TCE represents the ABAP client for the Agent Registry Control service, representing each operation as a method call. For more information see the API Page page.

Configuring Programmatically¶

DATA(lo_config) = DATA(go_tce)->get_config( ).

lo_config is a variable of type /AWS1/CL_TCE_CONFIG. See the documentation for /AWS1/CL_TCE_CONFIG for details on the settings that can be configured.

Waiters¶

Waiters for Implementation can be accessed via get_waiter() method followed by the waiter method to be called.

Details about the waiter methods available for service Implementation can be found in interface /AWS1/IF_TCE_WAITER.

Paginators¶

Paginators for Agent Registry Control can be created via get_paginator() which returns a paginator object of type /AWS1/IF_TCE_PAGINATOR. The operation method that is being paginated is called using the paginator object, which accepts any necessary parameters to provide to the underlying API operation. This returns an iterator object which can be used to iterate over paginated results using has_next() and get_next() methods.

Details about the paginator methods available for service Agent Registry Control can be found in interface /AWS1/IF_TCE_PAGINATOR.