AltLayer Documentation
  • đź‘‹Welcome
    • Overview
  • Restaked Rollups
    • VITAL for Decentralised Verification
      • Tier-1 Finality
      • Tier-2 Finality
      • Tier-3 Finality
    • MACH for Faster Finality
      • Interoperability via MACH
    • SQUAD for Decentralised Sequencing
    • Staking of dApp Token
  • Wizard
    • Introduction
    • Technical overview
    • Create AVS
    • Manage AVS
    • Operator management
    • Hosted operator API (BLS based)
    • Custom AVS specification
      • Constructor specification requirements
      • Import Externally-Deployed AVS
    • Report bug or submit a feature request
  • Autonome
    • Deploy AI Agent
    • Autonome API guide
    • Uploading your own agent framework
    • Twitter/X login troubleshooting guide
  • ♾️AltLayer-Facilitated Actively Validated Services
    • Overview
    • AltLayer MACH AVS
      • Operator Guide
      • User Delegation Guide
    • Cyber MACH AVS for Cyber L2
      • Operator Guide
      • User Delegation Guide
    • DODOchain MACH AVS for DODO Chain
      • Operator Guide
      • User Delegation Guide
    • Fast Finality Layer for Soneium
      • Operator Guide
      • User Delegation Guide
    • Xterio MACH AVS for Xterio Chain
      • Operator Guide
      • User Delegation Guide
  • Upgrade Guide
  • 🥩ALT Restaking
    • Staking Info & Parameters
    • Restake ALT
    • Delegating reALT
    • Check and Claim Staking Rewards
    • Unstake ALT
    • Migration from Xterio (Legacy) ALT Pool to Xterio Restaked ALT Pool
    • Testnet reALT faucet
  • Rollup-as-a-Service
    • What is Rollup-as-a-Service (RaaS)?
    • AltLayer's RaaS Offering
    • RaaS Onboarding Guide
      • Optimism Rollup FAQ
      • Arbitrum Rollup FAQ
    • AltLayer Ecosystem
    • Clients in the Spotlight
    • Pricing Model
  • External Integrations
    • Account Abstraction using Biconomy
    • Enabling permissionless interoperability on AltLayer Rollup with Hyperlane
      • Deplying Hyperlane Warp Routes for ERC20 Token Bridging
      • Running Off-chain Agents
      • Setting up the bridging UI
    • Cross-chain Interoperability using Celer
      • Fungible Token Bridging
      • Non-fungible Token Bridging
      • Generic Message Passing
      • cBridge SDK
  • AltLayer's In-House Rollup Stack in Depth
    • How does AltLayer's in-house rollup stack work?
    • Decentralized Sequencer Set
    • Security via Fraud Proof
  • Rollup Types
    • Flash Layer Rollups
      • Example Use cases
        • NFT Mint Events
        • Games
        • Event Ticketing
    • Persistent Rollups
  • Core Features of AltLayer's In-House Rollup Stack
    • Modular
    • Elastic
    • Multi-VM Support
    • Fraud Proofs
    • Decentralized Sequencers
    • Tiered-Finality
  • FlashLayer Showcase
    • AltLayer's POAP NFTs Collection Mint
      • Performance Test in the Wild
    • Dark Forest Community Round
    • Oh Ottie! NFT Collection Mint
    • Dark Forest Community Round for Jump Crypto's Pit Event
    • Ottie 2048
    • Other demos
      • Fraud Proof Demo
      • Flash Layer Demo
      • Rollup Launchpad Demo
      • FlashGPT Demo
  • Implementation Status
    • Roadmap
    • Development Status
  • Community & Support
    • Community
    • Support
Powered by GitBook
On this page
  • Guide
  • Troubleshooting bad deployments with uploaded frameworks
  1. Autonome

Uploading your own agent framework

PreviousAutonome API guideNextTwitter/X login troubleshooting guide

Last updated 3 months ago

Guide

  1. Click on “Upload New Framework”.

  1. Complete the following steps and review the summary panel before clicking “Submit”

    1. Enter your Agent Framework name (lowercase letters only, e.g. helloworld)

    2. Write a description of the AI Agent Framework (e.g., “ A sophisticated furry chat agent specializing in handling mission-critical conversations”)

    3. Input the Docker Image(e.g., docker_org_name/imagine:tag)

    4. Input Agent Logo (e.g. https://example.com/ottie007.png)

    5. Choose your Chat Endpoint (e.g. /poke)

    6. Input Port ( e.g. 3000)

    7. Ensure your agent chat framework follows the Chat Request and Chat Response Schema as shown below.

    8. Input GitHub URL (e.g. https://github.com/alt-research)

    9. Specify Environment Variables (optional)

    10. Finally, ensure all details are correct in the Summary panel and click on “Submit”.

  2. You can now find your uploaded framework under "My Uploads" tab. If you wish to, you can opt to "Make Public" your framework in our Autonome App Store by submitting your request. Typically, these requests will be approved in two to three business days if there are no issues.

Troubleshooting bad deployments with uploaded frameworks

If your agent deployment doesn't work with your uploaded framework, please do ensure your framework meets the following criteria before uploading again:

  • It has to be built for Linux architecture, you can use docker buildx build --platform=linux/amd64 if you are on MacOS;

  • The docker image url should be publicly accessible in order for our infrastructure to pull the image (https://hub.docker.com/);

  • The agent must have some API endpoints available to communicate, instead of being just a CLI application