Agent Types
Part 1 of the Agent Developer Guide
Last updated
Part 1 of the Agent Developer Guide
Last updated
LangStream offers 3 different types of agents. A agent is the start of a pipeline, a agent writes pipeline results to another service, and a agent is a step in the pipeline. The gist of developing an agent is to implement one of its APIs (, , or ). You provide the application’s source (the .py) files when deploying to the Control Plane. All of Python’s constructs and can be used as you build the agent.
It’s typical to run the Control Plane as an internal service within an Organization. An agent’s outgoing access might be limited to the internal network, or might have internet access. This may create incompatibility with LangStream’s pre-built agents, or you may want to include domain knowledge specific to processing within the agent.
A source agent is responsible for bringing data into the application’s pipeline.
A source agent is the first step of a pipeline and replaces the use of an input topic. A source can be anything. The agent is responsible for retrieving data from a service and uses the LangStream API to create a Record that encapsulates that data. LangStream will produce a message on the specified topic for other agents to consume.
A sink agent is responsible for writing data to a service outside the application pipeline.
The agent is responsible for accepting a list of Records as input and writing the value to the given service. A sink agent may be the last step in a pipeline or may capture data and continue to the next steps in the pipeline.
Processor agents are typically placed throughout an application’s pipeline.
A processor agent might manipulate data as it flows through the pipeline, or could add in context to help downstream agents make decisions. A processor agent is responsible for accepting a list of Records as input, doing some processing as necessary, and returning a Record (or many Records) as a result.
Service agents are generic applications that usually do not process streaming data in the scope of a pipeline.
Typically a Service exposes an API service that can be consumed by external applications. For instance you can build your ChatBot UI using a Service
Continue on to Part 2 of the Agent Developer Guide,