The provided samples are built using Genkit using the Gemini API.

• Movie Agent: Uses TMDB API to search for movie information and answer questions.
• Coder Agent: Generates full code files as artifacts.
• Content Editor Agent
  Sample agent to proof-read and polish content. To make use of this agent in a content creation multi-agent system, check out the content_creation sample.

First, follow the instructions in the agent's README file, then run npx tsx ./cli.ts to start up a command-line client to talk to the agents. Example:

1. Navigate to the samples/js directory:

   cd samples/js

2. Run npm install:

   npm install

3. Run an agent:

export GEMINI_API_KEY=<your_api_key>
npm run agents:coder

# in a separate terminal
npm run a2a:cli

This is sample code and not production-quality libraries.

Important: The sample code provided is for demonstration purposes and illustrates the mechanics of the Agent-to-Agent (A2A) protocol. When building production applications, it is critical to treat any agent operating outside of your direct control as a potentially untrusted entity.

All data received from an external agent—including but not limited to its AgentCard, messages, artifacts, and task statuses—should be handled as untrusted input. For example, a malicious agent could provide an AgentCard containing crafted data in its fields (e.g., description, name, skills.description). If this data is used without sanitization to construct prompts for a Large Language Model (LLM), it could expose your application to prompt injection attacks. Failure to properly validate and sanitize this data before use can introduce security vulnerabilities into your application.

Developers are responsible for implementing appropriate security measures, such as input validation and secure handling of credentials to protect their systems and users.