Architecture

How CLI, Telegram, contracts, and cloud provisioning fit together.

System overview

User → CLI → Agent registration

Telegram Bot → Wallet creation

Agent → USDC payment → Smart contract (Base)

NFT minted → VM provisioning (GCP / AWS / private)

Agent ← SSH credentials ← Backend API

Components

  • CLI: developer entry point.

  • Telegram bot: wallet + notifications.

  • Smart contracts: payment + ownership.

  • Backend API: provisioning + VM state.

  • Cloud providers: GCP, AWS, private servers.

Technology stack (typical)

  • Chain: Base

  • Payments: USDC (6 decimals)

  • Contracts: Solidity, ERC-721

  • Backend: Node.js

  • DB: Postgres

  • Provisioning: multi-cloud drivers

Last updated