Deploy agent
This guide walks you through deploying an agent using the QudeAI Framework. Follow the steps below carefully to ensure a successful deployment.
Step 1: Clone the Framework
Clone the QudeAI Framework repository to your local machine:
Step 2: Set Up Your .env
File
.env
FileInside the main directory, locate the
.env.example
file.Rename it to
.env
:Open the
.env
file and replace placeholders with your private key and other required configurations:
Step 3: Configure defineAgent.ts
defineAgent.ts
Open the
defineAgent.ts
file located in thesrc
folder:Modify the
agentDetails
object with your agent's specific details:Save the changes.
Step 4: Build the Project
Run the following commands to build the project:
If TypeScript compilation is required:
Step 5: Deploy the Agent
Run:
Example Output
Output Breakdown
Agent Details: Displays the details of the agent being deployed, including the name, symbol, description, and website.
Transaction Status:
Confirms that the transaction has been sent to the blockchain.
Transaction Successful:
Indicates that the deployment was successful and provides the transaction signature.
SolScan Link:
The
🔗 View on SolScan
section provides a clickable URL to view the transaction details on SolScan. This allows you to verify the deployment, view the status, and confirm the token creation.
How to Verify on SolScan
Copy the transaction signature from the output:
Open the SolScan link provided:
Review the transaction details, including:
The token creation.
The wallet that initiated the transaction.
The gas fees paid.
Example SolScan Page
On SolScan, you'll see:
Transaction Status:
Confirmed
Token Details: Includes the agent token name, symbol, and supply.
Wallet Information: The wallet address that deployed the agent.
Step 6: Verify Deployment
After deployment:
Use the
npm run interactqude
command to interact with your agent:Use the API or CLI commands to fetch details about your agent or perform actions like trading tokens.
Example defineAgent.ts
Configuration
defineAgent.ts
ConfigurationDependencies: This framework uses Solana RPC endpoints, so ensure the
RPC_ENDPOINT
is configured properly.Private Key: Ensure your private key in
.env
is secure. Do not share it with others.
Last updated