Using the Chat Interface

This comprehensive guide will help you master Mika402's AI chat interface and interact effectively with your autonomous payment agent.

Getting Started

Accessing the Chat

  1. Click "Launch App" on the homepage

  2. You'll be taken directly to the AI chat interface

  3. No registration or login required!

Interface Layout

Chat Area (Center)

  • Your messages appear on the right

  • AI responses stream in real-time on the left

  • Full conversation history with timestamps

  • Scroll to review previous interactions

Input Section (Bottom)

  • Main text input for requests and questions

  • Send button (or press Enter to submit)

  • Natural language processing - just type normally

Conversation Context

  • Mika402 remembers your conversation history

  • Build on previous requests

  • Refer to earlier services or payments

  • Context resets when you refresh the page

Basic Usage

Making Your First Request

Simply type and send a natural language request:

Mika402 will:

  1. Show "Processing your request..."

  2. Identify the required x402 service

  3. Display payment details if needed

  4. Process payment autonomously

  5. Return your requested data

Understanding Autonomous Payments

When your request requires a paid service:

Step 1: Service Discovery

Step 2: Limit Verification

Step 3: Autonomous Processing

Step 4: Service Delivery

Example Requests

Data Access

AI Services

Storage Services

Web3 Services

Conversation Techniques

Building Context

Mika402 remembers your conversation throughout the session:

Context Scope

  • Remembers entire session history

  • References previous services accessed

  • Maintains awareness of prior payments

  • Resets when you refresh the page

Follow-Up Questions

Build on previous interactions:

Multiple Requests

Sequential Approach

Batch Approach (Recommended!)

The batch approach is more efficient and may save on gas fees through optimized transaction batching.

Comparative Queries

Request multiple services and compare:

Mika402 will access both services and provide analysis.

Request Types

Service Discovery

Learn about available services:

  • "What x402 services can you access?"

  • "Show me available AI image generation services"

  • "Which weather APIs are supported?"

  • "List all storage services"

Perfect for exploring the ecosystem!

Direct Service Requests

Access specific services with payment:

  • "Use Heurist Mesh to generate [image description]"

  • "Get data from WeatherAPI for [location]"

  • "Pin my file to IPFS using Pinata"

  • "Deploy smart contract via thirdweb"

Provide clear, specific instructions for best results.

Payment Queries

Check spending and transaction status:

  • "How much have I spent today?"

  • "Show my recent transactions"

  • "What are my current spending limits?"

  • "Check status of transaction 0x1234..."

Monitor your autonomous payment activity.

Service Comparison

Evaluate different options:

  • "Compare WeatherAPI vs OpenWeather pricing"

  • "Which IPFS service is cheapest?"

  • "What's the best AI image generation service?"

  • "Show cost differences between available APIs"

Make informed decisions about which services to use.

Configuration Requests

Manage your settings:

  • "Update my daily spending limit to 0.02 ETH"

  • "Show my current configuration"

  • "What blockchain am I using?"

  • "Connect my wallet"

Control your autonomous agent's behavior.

Formatting Your Requests

Be Specific

Vague

Specific

Include Details

Minimal Context

Rich Context

Structure Complex Requests

Unstructured

Structured

Use Natural Language

You don't need commands or special syntax:

Robotic (Works but unnecessary)

Natural (Preferred)

Understanding Responses

Reading AI Answers

Transaction Confirmation

Service Data

Error Messages

Markdown Formatting

Mika402 uses rich formatting for clarity:

Headers organize sections

Lists for readability

  • Bullet points for features

  • Numbered lists for steps

Emphasis

  • Bold = important information

  • Italic = emphasis

  • Code = addresses/hashes

Tables for data

Metric
Value
Status

Cost

0.001 ETH

✓ Paid

Links

View on Etherscan - clickable transaction links

Visual Indicators

Quick status understanding:

Payment Status

  • ✓ Completed successfully

  • ⏳ Processing/Pending

  • ❌ Failed

  • ⚠️ Warning/Caution

Spending Indicators

  • 🟢 Well within limits

  • 🟡 Approaching limit

  • 🔴 At or exceeding limit

Service Status

  • 🟢 Available

  • 🟡 Slow response

  • 🔴 Unavailable

Spending Management

Monitoring Your Usage

Check spending anytime:

Transaction History

View all your payments:

Updating Limits

Adjust spending limits through conversation:

Handling Payment Issues

Insufficient Balance

Solution: Fund your wallet with additional cryptocurrency.

Limit Exceeded

Solution: Choose one of the suggested options.

Service Unavailable

Solution: Wait and retry, or use an alternative service.

Transaction Failed

Solution: Retry with adjusted gas settings, or contact support if issue persists.

Payment Pending

Solution: Be patient. Blockchain confirmations can take time during high network activity.

Advanced Techniques

Conditional Requests

Mika402 evaluates conditions and makes smart decisions.

Service Preferences

Set preferences for recurring request patterns.

Batch Processing

Efficient bulk operations with cost transparency.

Cross-Chain Requests

Let Mika402 optimize for cost across chains.

Best Practices

Before Making Requests

  1. Set Appropriate Limits: Configure conservative spending limits initially

  2. Check Balance: Ensure sufficient funds for service + gas

  3. Understand Costs: Ask about pricing before proceeding

  4. Verify Services: Use established, verified x402 services

During Requests

  1. Be Patient: Wait for payment confirmations (typically ~2 seconds)

  2. Don't Refresh: Keep the page open during transactions

  3. Monitor Status: Watch for confirmation messages

  4. Save Transaction Hashes: Keep records for reference

After Requests

  1. Verify Receipt: Check that you received the expected service

  2. Review Transaction: Confirm costs match expectations on block explorer

  3. Update Limits: Adjust spending limits based on usage patterns

  4. Provide Feedback: Report any issues with services

Privacy & Security

Your Conversations

  • Not stored on servers

  • Not logged or tracked

  • Completely anonymous

  • Refresh to clear history

Safe Practices

  • Never share private keys with Mika402 (it will never ask)

  • Verify service URLs and contract addresses

  • Use a dedicated wallet for autonomous payments

  • Start with small spending limits while learning

  • Monitor transaction history regularly

  • Only use verified x402 services

Transaction Transparency

  • All payments are on-chain and publicly verifiable

  • Transaction hashes provided for every payment

  • Full cost breakdown shown before processing

  • No hidden fees - only service cost + gas

Troubleshooting

AI Not Responding

  • Wait 30 seconds (may be processing complex request)

  • Check internet connection

  • Refresh page if stuck >1 minute

  • Try simpler query to test connectivity

Service Not Found

  • Verify service name or check available services

  • Ask "What services are available for [use case]?"

  • Service may not support x402 protocol yet

  • Try alternative service providers

Payment Not Processing

  • Check wallet connection status

  • Verify sufficient balance for payment + gas

  • Ensure spending limits allow transaction

  • Check blockchain network status

Unexpected Costs

  • Ask for cost breakdown: "Why did that cost [amount]?"

  • Remember to account for gas fees

  • Network congestion can increase gas costs

  • Some services have dynamic pricing

Tips for Power Users

  1. Set Service Preferences: Tell Mika402 your preferred providers

  2. Batch Requests: Combine multiple requests to save on gas

  3. Monitor Gas Prices: Ask about current gas costs before transacting

  4. Use Aliases: "Do the same thing as last time" works!

  5. Request Estimates: "How much would it cost to..." before committing

  6. Export History: "Export my transaction history as CSV"

  7. Set Up Alerts: "Notify me when I reach 80% of daily limit"

  8. Multi-Chain Optimization: "Always use the cheapest chain available"

Common Scenarios

Scenario 1: Regular Data Access

Scenario 2: Cost Comparison

Scenario 3: Budget Management

Next Steps


Ready to start? Visit mika402.xyz and make your first autonomous payment request!

Last updated