Configuration

This guide covers wallet configuration, spending limits, RPC endpoints, and advanced settings for your Miko402 deployment.

Configuration Overview

What you'll configure:

• Environment variables and API keys

• Wallet connections and RPC endpoints

• Spending limits and safety controls

• AI model settings

• Advanced payment options

Time required: 10–15 minutes

Environment Variables

All configuration lives in .env.local. This file is gitignored—never commit API keys to version control.

Create Your Config File

cp .env.example .env.local

Required Variables

# OpenRouter API Key (REQUIRED)
# Get yours at: https://openrouter.ai/
OPENROUTER_API_KEY=sk-or-v1-your_actual_key_here

# Solana RPC Endpoint (REQUIRED for production)
# Use devnet for testing, mainnet for production
NEXT_PUBLIC_SOLANA_RPC_ENDPOINT=https://api.mainnet-beta.solana.com

Important: No quotes around values. No spaces before or after =.

Optional Variables

# Custom Miko System Prompt (OPTIONAL)
MIKO_SYSTEM_PROMPT="Custom instructions for Miko..."

# Additional chain RPC endpoints (OPTIONAL)
NEXT_PUBLIC_ETHEREUM_RPC=https://eth-mainnet.g.alchemy.com/v2/YOUR_KEY
NEXT_PUBLIC_POLYGON_RPC=https://polygon-mainnet.g.alchemy.com/v2/YOUR_KEY

RPC Endpoint Configuration

Your RPC endpoint determines which blockchain network Miko uses and how quickly transactions process.

Free Public RPCs

Solana Devnet (Testing):

NEXT_PUBLIC_SOLANA_RPC_ENDPOINT=https://api.devnet.solana.com

• Free and suitable for testing

• Get free devnet SOL from faucet

• Not recommended for production

Solana Mainnet (Production):

NEXT_PUBLIC_SOLANA_RPC_ENDPOINT=https://api.mainnet-beta.solana.com

• Free but rate-limited

• May experience slowdowns during peak usage

Premium RPC Providers

For production workloads, premium RPCs deliver better reliability and performance.

Helius (Recommended for Solana)

NEXT_PUBLIC_SOLANA_RPC_ENDPOINT=https://mainnet.helius-rpc.com/?api-key=YOUR_KEY

Fastest Solana RPC with 99.9% uptime SLA, built-in analytics, and a generous free tier. Get a Helius API key →

QuickNode

NEXT_PUBLIC_SOLANA_RPC_ENDPOINT=https://your-endpoint.quiknode.pro/your-key/

Global infrastructure with high rate limits and enterprise-grade reliability. Get a QuickNode endpoint →

Alchemy

NEXT_PUBLIC_SOLANA_RPC_ENDPOINT=https://solana-mainnet.g.alchemy.com/v2/YOUR_KEY

Excellent documentation, webhook support, and a generous free tier. Get an Alchemy key →

Multi-Chain Setup

Configure multiple chains for flexibility:

# Solana (Primary)
NEXT_PUBLIC_SOLANA_RPC_ENDPOINT=https://mainnet.helius-rpc.com/?api-key=YOUR_KEY

# Ethereum (Fallback)
NEXT_PUBLIC_ETHEREUM_RPC_ENDPOINT=https://eth-mainnet.g.alchemy.com/v2/YOUR_KEY

# Polygon (Low-cost option)
NEXT_PUBLIC_POLYGON_RPC_ENDPOINT=https://polygon-mainnet.g.alchemy.com/v2/YOUR_KEY

Miko automatically selects the optimal chain based on service requirements and cost.

Spending Limits

Spending limits are critical for safety. Configure them before making any payments.

Recommended Starter Limits

Tier	Daily	Weekly	Monthly	Use Case
Conservative	0.01 SOL (~$2.50)	0.05 SOL (~$12.50)	0.2 SOL (~$50)	Testing and learning
Moderate	0.1 SOL (~$25)	0.5 SOL (~$125)	2 SOL (~$500)	Regular use
Power User	1 SOL (~$250)	5 SOL (~$1,250)	20 SOL (~$5,000)	Production workloads

Start conservative, scale up gradually.

How Limits Work

Your Request → Miko Checks Limits → Within Limits? → Process Payment
                                  → Exceeded? → Reject & Notify You

Limits reset automatically on a rolling basis—daily every 24 hours, weekly every 7 days, monthly every 30 days.

Configuring Limits

Limits are configured per-wallet through smart contracts:

DAILY_SPENDING_LIMIT=0.01
WEEKLY_SPENDING_LIMIT=0.05
MONTHLY_SPENDING_LIMIT=0.2

These limits are enforced on-chain for maximum security—they cannot be bypassed programmatically.

AI Model Configuration

Model Selection

Miko402 uses Google Gemini 2.0 Flash for optimal speed and cost:

// Configured in app/api/chat/route.js
model: google('gemini-2.0-flash-exp')

Why Gemini 2.0 Flash:

• Fastest response times in its class

• Cost-effective for high-frequency payment processing

• Sufficient reasoning capability for service discovery and payment logic

• Built-in web search capabilities

Custom System Prompt

Override Miko's default behavior with a custom prompt in .env.local:

MIKO_SYSTEM_PROMPT="You are Miko402, focused on enterprise use cases.
Prioritize security and detailed transaction reporting.
Always request explicit confirmation before payments over 0.1 SOL."

Applications for custom prompts:

• Enterprise compliance requirements

• Industry-specific service focus

• Additional safety checks

• Adjusted interaction style

Temperature & Token Settings

Control response creativity and length:

// In app/api/chat/route.js
temperature: 0.7,      // 0.0 = deterministic, 1.0 = creative
maxTokens: 4000,       // Maximum response length

• Payment-focused applications: Lower temperature (0.3–0.5) for consistency

• Exploratory use cases: Higher temperature (0.7–0.9) for variety

Wallet Configuration

Supported Wallets

Browser Extensions:

• Phantom (Solana native, recommended)

• MetaMask (most widely used)

• Coinbase Wallet

• Brave Wallet

Mobile Wallets:

• Phantom Mobile

• MetaMask Mobile

• Trust Wallet

• Coinbase Wallet Mobile

Hardware Wallets:

• Ledger (via Phantom/MetaMask)

• Trezor (via MetaMask)

Multi-Wallet Strategy

Consider separating wallets by purpose:

1. Testing Wallet — Small amounts, devnet testing

2. Operational Wallet — Regular autonomous payments

3. Cold Storage — Large holdings, no Miko access

Wallet Security

Do:

• Use hardware wallets for significant amounts

• Enable biometric/password locks

• Store seed phrases offline

• Use a dedicated wallet for autonomous payments

Don't:

• Store seed phrases digitally

• Share screen with seed phrase visible

• Use the same wallet for everything

• Keep large amounts in hot wallets

Advanced Configuration

Custom Gas Settings

// Fast confirmation (higher gas)
gasPrice: 'high',
maxPriorityFeePerGas: 2_000_000_000

// Standard (balanced)
gasPrice: 'medium',
maxPriorityFeePerGas: 1_000_000_000

// Economy (slower)
gasPrice: 'low',
maxPriorityFeePerGas: 500_000_000

Rate Limiting

Adjust the cooldown between requests:

// In app/app/page.js
const COOLDOWN_SECONDS = 50;  // Default: 50 seconds

Timeout Configuration

// In app/api/chat/route.js
export const maxDuration = 50;  // seconds

Vercel platform limits:

• Hobby: 10 seconds

• Pro: 60 seconds

• Enterprise: 900 seconds

Multi-Chain Routing

Configure automatic chain selection priority:

// By cost
chainPriority: ['solana', 'polygon', 'ethereum']

// By speed
chainPriority: ['solana', 'ethereum', 'polygon']

// By reliability
chainPriority: ['ethereum', 'solana', 'polygon']

Testing Your Configuration

1. Environment Check

npm run dev
# Verify console output confirms:
# ✓ OpenRouter API key loaded
# ✓ Solana RPC connected
# ✓ Configuration validated

2. Wallet Connection Test

1. Open the application

2. Click "Connect Wallet"

3. Approve the connection

4. Verify your wallet address appears

3. RPC Endpoint Test

curl https://api.mainnet-beta.solana.com -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"getHealth"}'
# Expected: {"jsonrpc":"2.0","result":"ok","id":1}

4. Payment Test

1. Connect a devnet wallet

2. Get devnet SOL from the faucet

3. Request a small service (0.001 SOL)

4. Verify payment completes

5. Check transaction on the block explorer

Configuration Checklist

Before going live:

• .env.local created with all required variables

• OpenRouter API key is valid

• RPC endpoint is reachable

• Spending limits are configured

• Wallet is connected and funded

• Test payment completed successfully

• Transaction appears on block explorer

• No errors in browser console

• Rate limiting works as expected

Common Configuration Issues

Environment Variables Not Loading

1. Restart the dev server (Ctrl+C, then npm run dev)

2. Clear the .next cache: rm -rf .next

3. Verify the file is named .env.local (not .env)

Invalid API Key

1. Verify the key in your OpenRouter dashboard

2. Check for typos in .env.local

3. Ensure no quotes around the key value

4. Regenerate the key if necessary

RPC Connection Failed

1. Test the endpoint with curl (see above)

2. Check that your firewall isn't blocking the connection

3. Verify the API key is correct (for premium RPCs)

4. Fall back to the public RPC temporarily

Spending Limits Not Enforced

1. Verify the smart contract deployment

2. Check that your wallet has approved the contract

3. Confirm limits are set on-chain

4. Re-deploy contracts if needed

Need Help?

• Troubleshooting Guide

• FAQ

• GitHub Issues

• Email: [email protected]

• 𝕏: @miko402xyz

---

Configuration complete? Move on to Making Your First Payment →