A CLI tool to scaffold production-ready uAgents with best practices baked in
View the Project on GitHub tejus3131/create-agentverse-agent
When you run create-agentverse-agent, it generates a production-ready project structure. Here’s what you get:
my-agent/
├── .env # Environment variables
├── agent.py # Agent definition & handlers
├── docker-compose.yml # Local container orchestration
├── Dockerfile # Container build definition
├── main.py # Application entrypoint
├── Makefile # Common development commands
├── pyproject.toml # Project metadata & dependencies
└── README.md # Project documentation
agent.pyThe main agent definition file containing:
main.pyThe application entrypoint that:
.envEnvironment variables for configuration:
# Environment Configuration
ENV=
# API Keys
AGENTVERSE_API_KEY=
# Agent Configuration
AGENT_NAME=
AGENT_SEED_PHRASE=
AGENT_PORT=
AGENT_ROUTE=
AGENT_HANDLE=
# Hosting Configuration
HOSTING_ENDPOINT=
# Message Processing Configuration
MAX_PROCESSED_MESSAGES=
PROCESSED_MESSAGE_TTL_MINUTES=
CLEANUP_INTERVAL_SECONDS=
# Rate limiting configuration
RATE_LIMIT_MAX_REQUESTS=
RATE_LIMIT_WINDOW_MINUTES=
pyproject.tomlModern Python project configuration with:
MakefileCommon commands for development:
make install # Install dependencies
make env # Activate virtual environment
make dev # Start the agent in poetry environment
make run # Start agent in docker container (requires AGENTVERSE_API_KEY in .env)
DockerfileMulti-stage Docker build optimized for:
docker-compose.ymlLocal development setup with:
Messages are handled asynchronously, allowing your agent to process multiple requests concurrently.
Structured logging with request context, making debugging and monitoring straightforward.
Built-in support for sending progress updates during long-running operations.
Standard health check endpoint and quota management for production deployments.
Ready to deploy to Agentverse with proper configuration.
Learn how to customize your agent in Configuration.