How to interact with agents built in Agent Service.
Clients call through the SGP API to Agent Service in order to CRUD agent configs and execute agents. Agent configs are stored in Agents DB, together with the internal run states of the agents. The service also talks to secrets vault (e.g. AWS secrets manager) and blob store (e.g. AWS S3). For SGP native assets like knowledge bases and LLMs the service also talks back to the SGP API.
POST
request to create an application spec (/v4/application-specs
).application_spec_id
from the response.loop_with_list_demo.yaml
).uuid4()
) and associates an account_id
.STATE_MACHINE
, PLAN
, or WORKFLOW
) based on YAML contents.POST
request to /v4/application-variants
to create a variant.variant_id
from the response.You can send a POST request to an agent variant as a standard request or stream the response line by line.
POST
request to process a specific application variant.object: "tree"
) for processing.POST
request with stream=True
to enable real-time streaming.How to interact with agents built in Agent Service.
Clients call through the SGP API to Agent Service in order to CRUD agent configs and execute agents. Agent configs are stored in Agents DB, together with the internal run states of the agents. The service also talks to secrets vault (e.g. AWS secrets manager) and blob store (e.g. AWS S3). For SGP native assets like knowledge bases and LLMs the service also talks back to the SGP API.
POST
request to create an application spec (/v4/application-specs
).application_spec_id
from the response.loop_with_list_demo.yaml
).uuid4()
) and associates an account_id
.STATE_MACHINE
, PLAN
, or WORKFLOW
) based on YAML contents.POST
request to /v4/application-variants
to create a variant.variant_id
from the response.You can send a POST request to an agent variant as a standard request or stream the response line by line.
POST
request to process a specific application variant.object: "tree"
) for processing.POST
request with stream=True
to enable real-time streaming.