Skip to content
This repository was archived by the owner on Dec 4, 2025. It is now read-only.

abstractoperators/aiden

Repository files navigation

Contributors Forks Stargazers Issues MIT License LinkedIn


Logo

aiden

High Performance Onchain AI Agents
Explore the docs »

View Demo · Report Bug · Request Feature

Table of Contents

  1. About The Project
  2. Getting Started
  3. Roadmap
  4. Contributing
  5. License
  6. Contact

About The Project

Developed by Abstract Operators and powered by Sei, AIDEN ([A]gent [I]ntegration & [D]eployment [EN]gine) is an AI Agent Platform for users to create, integrate, interact with, and deploy a diverse ecosystem of High Performance AI Agents with no-code/low-code UI/UX on the Sei blockchain - a world scale EVM Layer-1 blockchain.

Project Overview

  • apps/api- This directory contains the FastAPI backend for the Aiden protocol. It is containerized via Docker and serves as the main API interface for user interactions.

  • apps/frontend- This directory is the frontend UI component for AIDEN built using Typescript/Next.js.

  • apps/market-data- This directory basically contains all components regarding marketdata API that is built on SQLAlchemy, FastAPI. (NOTE: This needs POSTGRES unless any other DB supports DATE_TRUNC funtion.)

  • apps/prometheus- This directory allows Aiden to be exposed such that it can be monitored and analysed via Prometheus.

  • apps/runtime- This directory is basically a general agentic runtime Running on ECS. It retrieves agent, starts it and allows multiple tasks to be performed.

Built With

Getting Started

Prerequisites

Secrets

Locally, all secrets may be placed in their appropriate .env files. Reference and maintain the appropriate .env.example.

It is important to maintain example .env files for each environment. They are the source of insensitive secrets for image builds. However, only insensitive secrets may be placed in these example files. Sensitive variables are stored in AWS Secrets Manager. Add sensitive variables, and update the appropriate task definition to load the secret into the container at runtime.

Installation

Node + pnpm

Install pnpm and node

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.1/install.sh | bash

# Install Node
nvm install 23

# Verify the Node.js version: Should be the same
node -v
nvm current

# Verify node package manager version (npm)
npm -v

npm install -g pnpm@latest-10

ElizaOS

git submodule update --init --recursive --depth 1

# To update commit on eliza
cd eliza
git pull origin main
git checkout # git checkout $(git describe --tags --abbrev=0) for latest release
cd ..
git add eliza
git commit

Roadmap

See the open issues for a list of proposed features (and known issues).

Contributing

Contributions are what make the open source community such an amazing place to learn, be inspired, and create. Any contributions you make are greatly appreciated.

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

License

Distributed under the MIT License. See LICENSE for more information.

Contact

Kent Gang - @abstractoperant

Project Link: https://github.com/abstractoperators/aiden

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors