Skip to main content

Endercom CLI

A command-line interface for deploying and managing AI agents on AWS Lambda using the Endercom framework.

PyPI version

Installation

pip install endercom-cli

Prerequisites

Before you begin, ensure you have:

  1. An AWS Account: You'll need credentials to deploy resources.
  2. AWS CLI Configured: Run aws login to set your credentials and default region.
    brew install awscli
    aws login
    
  3. AWS SAM CLI: Required for building and deploying the serverless stack.
    brew install aws-sam-cli
    

Quick Start

1. Initialize an Agent Project

Create a new agent project structure.

endercom init <agent-name>

This scaffolds a directory with:

  • agent.py: Your agent logic (where you write code)
  • app.py: Server entry point and wrapper
  • template.yaml: AWS SAM infrastructure definition
  • requirements.txt: Python dependencies
  • .endercom/agent.yaml: CLI configuration

2. Configure Environment (Optional)

If your agent needs API keys (e.g., OPENAI_API_KEY), add them to the secrets manager.

cd <agent-name>
endercom secrets set OPENAI_API_KEY "sk-..."

3. Deploy

Build and deploy your agent to AWS.

endercom deploy

The CLI will:

  • Check your code for undeclared environment variables.
  • Sync your configuration to the SAM template.
  • Build the agent using sam build.
  • Deploy using sam deploy.

Commands

Command Description
init <name> Create a new agent project.
deploy Build and deploy the agent stack to AWS.
configure Update project configuration.
secrets set <key> <val> Securely store secrets in AWS Secrets Manager.
logs Tail real-time logs from your Lambda function.
destroy Tear down the AWS stack and remove associated secrets.

Configuration

The source of truth for your agent's configuration is .endercom/agent.yaml.

name: my-agent
runtime: python3.12
region: us-east-1
memory: 1024
timeout: 30
env:
  MY_PUBLIC_VAR: "production"
secrets:
  - OPENAI_API_KEY
  • env: Standard environment variables injected at deployment.
  • secrets: List of keys to resolve securely from AWS Secrets Manager.

Metadata

Release files for endercom-cli 0.1.6

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for endercom-cli 0.1.6
File Size Uploaded Provenance
endercom_cli-0.1.6.tar.gz 14.0 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for endercom-cli 0.1.6
File Interpreter ABI Platform
endercom_cli-0.1.6-py3-none-any.whl Python 3 none any Details

Total release size: 28.2 kB

Release files / endercom_cli-0.1.6.tar.gz

Download URL endercom_cli-0.1.6.tar.gz
Size 14.0 kB
Tags Source
SHA-256 checksum
How to use checksums
2a7132ef3ffbc5b454c72d1ce0ad8b0394b875072950d754774c797208cd27ca
BLAKE2b-256 checksum
How to use checksums
209f256491790d9c35bda561ad7e56ec379b1ab49da3bbcc11b179cd1acc3101
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jan 2, 2026.

Transparency log

Release files / endercom_cli-0.1.6-py3-none-any.whl

Download URL endercom_cli-0.1.6-py3-none-any.whl
Size 14.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fa5bbe1be9abca3eea9e7c0b73d023e99232c52fe693dd4da7c52f03498cd77b
BLAKE2b-256 checksum
How to use checksums
f1243d73f7efa3e0faa424e67af9b8a71e43d076a0bf8b98432525ebd837e76b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jan 2, 2026.

Transparency log

Security for endercom-cli 0.1.6

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for endercom_cli-0.1.6.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jan 2, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page