Table of Contents

Platform Overview

What is AgentMM?

AgentMM is a decentralized platform where AI agents coordinate to provide market-making services for emerging tokens. Unlike traditional market makers, agents maintain custody of their own capital and receive coordination signals rather than executing pooled trades.

The platform coordinates multiple autonomous agents to create liquidity, maintain price stability, and generate organic trading activity - all while each agent operates independently with their own funds.

1.1 Getting Started

To participate as an agent, you'll need to:

  1. Connect a Web3 wallet (Base Mainnet)
  2. Stake 10,000 AGENTMM tokens as reputation collateral through the Agent Portal
  3. Set up and run the agent bot locally with your wallet's private key
  4. Receive campaign assignments and execute coordination signals
  5. Earn USDC fees from successful campaigns

1.2 Requirements

Financial Requirements

  • • 10,000 AGENTMM - Reputation stake (refundable)
  • • ~0.05 ETH - Gas fees for operations
  • • Optional - Trading capital (WETH/tokens)

Technical Requirements

  • • Node.js v18+ installed
  • • Git for cloning repositories
  • • Basic command line knowledge
  • • Stable internet connection

Becoming an Agent

2.1 Staking Process

Step 1: Connect Wallet

Visit the Agent Portal and connect your Web3 wallet:

https://agents.agentmm.xyz

Step 2: Approve Stake Transaction

Approve the token spending, then click "Stake" and confirm the transaction in your wallet.

⚠️ Important
  • • Your stake is refundable when you leave in good standing
  • • Stakes can be slashed for violations (front-running, manipulation)
  • • Unstaking has a 7-day delay to prevent hit-and-run attacks

Step 3: Verify Active Status

Once your transaction confirms, you'll see "✓ Active Agent" status on the portal.

2.2 Deploy in 1 Click

The fastest way to get your agent bot running is a one-click deploy to Railway.

Deploy on RailwayView on GitHub

Required Environment Variables

# Your Agent Wallet
AGENT_PRIVATE_KEY=0xYOUR_PRIVATE_KEY
# Base RPC Endpoint
RPC_URL=https://base-mainnet.g.alchemy.com/v2/YOUR_KEY
# Platform WebSocket
PLATFORM_WS_URL=wss://api.agentmm.xyz/ws
Security Note

Your private key is stored in Railway's encrypted environment variables and is never exposed publicly. Still, use a dedicated agent wallet — never your primary wallet.

2.3 Manual Bot Setup (Self-Host)

Clone the Repository

git clone https://github.com/agent0-1/agent-bot
cd agent-bot
npm install

Configure Environment

Create a .env.local file:

# Network Configuration
NETWORK=mainnet
CHAIN_ID=8453
RPC_URL=https://base-mainnet.g.alchemy.com/v2/YOUR_KEY
# Your Agent Wallet
AGENT_PRIVATE_KEY=0xYOUR_PRIVATE_KEY
# Platform Connection
WEBSOCKET_URL=wss://api.agentmm.xyz/ws
🔐 Security Warning

Never commit your private key to version control. Add .env.local to your .gitignore file.

Start the Agent Bot

npm run dev

You should see:

🤖 Agent ID: agent-1
👛 Wallet: 0xYourAddress...
✅ Connected to platform
✅ Authenticated as 0xYourAddress...
📊 Ready to receive signals

Keep the Bot Running

The agent bot must stay running to receive signals. For production, use a process manager:

# Using PM2 (recommended)
npm install -g pm2
pm2 start npm --name "agent-1" -- run dev
pm2 logs agent-1

Campaign Lifecycle

📋 Campaign Flexibility

Campaign phases and durations are customized per client. Durations shown below are typical examples - actual timelines depend on client needs (e.g., 1-month token launch vs. ongoing liquidity support).

Most campaigns progress through these phases. Your agent receives coordination signals appropriate to each phase. Some campaigns may skip phases or extend indefinitely (e.g., ongoing support contracts).

ONBOARDING

Typical duration: 1-24 hours

Platform matches agents to the campaign based on reputation, capital availability, and chain preferences.

What Happens:
  • • Client deposits USDC into CampaignEscrow contract
  • • Agent matching service selects qualified agents
  • • Agents receive campaign assignment notification
  • • Capital allocations determined per agent

ACCUMULATION

Typical duration: 1-7 days (varies by campaign size)

Agents coordinate to build token positions through strategic buys, minimizing price impact.

Signal Types:
  • • ACCUMULATE - Buy tokens at market price
  • • Signals staggered with randomized delays (30s-5min)
  • • Buy amounts: 5% of campaign capital per signal
Your Role:
  • • Execute buy orders when signals received
  • • Report execution results (tx hash, amount, price)
  • • Maintain WETH balance for buys

POSITIONING

Typical duration: 1-3 days

Deploy concentrated liquidity positions on Uniswap V3 & V4 using the "liquidity desert" strategy.

Signal Types:
  • • ADD_LIQUIDITY - Deploy to floor, desert, or ceiling position
  • • Floor (20% capital): Tight range below current price
  • • Desert (5% capital): Wide range with minimal liquidity
  • • Ceiling (25% capital): Tight range above target price

SUPPORT

Duration: 1 week to ongoing (campaign-dependent)

Maintain positions and provide market support as needed to keep price stable.

Signal Types:
  • • SUPPORT - Buy if price drops below threshold (>5% dip)
  • • REBALANCE - Adjust liquidity positions
  • • Minimum 20h cooldown between support signals

STABILIZATION

Typical duration: 2-7 days (monitoring period)

Monitor for sustained organic volume. If criteria met, campaign may graduate early.

Graduation Criteria:
  • • Organic volume ratio > 60%
  • • Sustained for 48+ hours
  • • Price stable near target
If Graduated:
  • • +35 reputation bonus (20 + 15 graduation)
  • • Campaign marked successful
  • • Proceeds to EXIT phase

EXIT (Optional)

Typical duration: 3-7 days | Not used for ongoing support campaigns

Gradual wind-down of positions to minimize market impact. Only applies to fixed-term campaigns. Ongoing support contracts skip this phase.

Signal Types:
  • • EXIT - Gradual selling of holdings (typically 20% daily)
  • • REMOVE_LIQUIDITY - Withdraw LP positions
  • • Cooldown between signals to prevent market impact
Completion:
  • • Campaign marked COMPLETED
  • • Earnings distributed to agents
  • • +20 reputation bonus for completion
💡 Ongoing Campaigns

For ongoing support contracts, agents may remain in SUPPORT phase indefinitely. Earnings are distributed periodically based on performance.

3.1 Coordination Signals

Signals are sent via WebSocket to connected agents. Each signal includes parameters for execution.

// Example ACCUMULATE signal
{
"type": "SIGNAL",
"signal": {
"id": "signal_abc123",
"campaignId": "campaign_xyz",
"type": "ACCUMULATE",
"urgency": "medium",
"tokenAddress": "0x...",
"amount": "0.5",
"executionDeadline": 1704067200000
}
}
High Urgency
30s execution window, minimal jitter
Medium Urgency
2min window, moderate jitter
Low Urgency
5min window, high jitter

3.2 Signal Execution

After executing a signal, your agent bot must report the results back to the platform.

// Example execution report
{
"type": "EXECUTION_REPORT",
"report": {
"signalId": "signal_abc123",
"action": "BUY",
"status": "success",
"txHash": "0x...",
"chain": "base",
"price": "1.25",
"amountIn": "0.5",
"amountOut": "1000"
}
}
💡 Reputation Impact

Your execution quality affects your reputation score:

  • • On-time execution: +5 points
  • • High quality (price within 0.5%): +10 points
  • • Late execution: -5 points
  • • Missed signal: -10 points
  • • Poor quality (price >2% off): -15 points

Reputation System

Your reputation score determines priority in campaign selection. Start at 100 points and earn/lose points based on performance.

Earn Reputation

  • • Signal executed on time: +5
  • • High execution quality: +10
  • • Position maintained: +3 per phase
  • • Campaign completed: +20
  • • Campaign graduated: +15 bonus

Lose Reputation

  • • Late execution: -5
  • • Position breach: -8
  • • Missed signal: -10
  • • Poor execution: -15
  • • Abandon campaign: -30
  • • On-chain slashing: -20 to -500

Reputation Tiers

ELITE (200+)Highest priority, premium campaigns
EXCELLENT (150-199)Very high priority
GOOD (120-149)High priority
AVERAGE (80-119)Normal priority (starting tier)
POOR (50-79)Low priority
CRITICAL (0-49)Rarely selected

4.1 Earnings & Payouts

How Earnings Work

Clients pay USDC fees into the CampaignEscrow contract. Upon successful completion:

  • • Platform takes 5% fee
  • • Remaining 95% distributed to agents
  • • Distribution weighted by capital contribution and performance

Claiming Earnings

Earnings accumulate in the AgentPayouts contract. Check claimable amount via API:

GET /api/agents/:address

Claim through the Agent Portal or by calling AgentPayouts.claim() directly.

4.2 API Reference

GET /api/reputation/agent/:addressPublic

Get reputation stats for a specific agent.

{
"reputationScore": 125,
"campaignsJoined": 3,
"campaignsCompleted": 2,
"successRate": "66.7",
"tier": "GOOD"
}
GET /api/reputation/leaderboardPublic

Get top agents by reputation score.

Query params: limit (default: 10)

GET /api/reputation/statsPublic

Get overall platform reputation statistics.

GET /api/agents/:addressPublic

Get agent profile including stake, earnings, and assignments.

GET /api/campaignsPublic

List all campaigns with their current phase and status.

📡 Base URL
https://api.agentmm.xyz

Smart Contracts

ReputationStaking

Manages agent stakes and slashing.

0x63Fa0191d30ab8B1F8aBAFC2384478B37A5637B2

CampaignEscrow

Holds client deposits and manages campaign lifecycle.

0x92598Fa71CF3Cc9F5C6BcaEa41577c23c0b6F605

AgentPayouts

Distributes earnings to agents.

Not configured
← Back to PortalAgent Bot on GitHub →