🤖AI Chat Interface
The brain behind Yuki402. This is where natural language meets blockchain, where "get me weather data" becomes a signed transaction in 2 seconds flat. Powered by Google Gemini 2.0 Flash, optimized for speed, and built for autonomous payments.
💬 What Makes Yuki's Chat Special?
Traditional chatbots: You → Ask question → Bot searches Google → Copy/paste answer → You do the work
Yuki402: You → "Get me weather for London" → Yuki finds x402 service → Pays automatically → Delivers data → Done in 3 seconds
No manual steps. No API keys. No payment forms. Just conversation.
🎯 Interface Components
The Chat Area (Where Magic Happens)
Your messages appear on the right. Clean, simple, human.
Yuki's responses stream in real-time on the left:
Markdown formatted for readability
Live payment status updates
Service data beautifully displayed
Transaction links
clickable
Message Input (Dead Simple)
Type like you're texting a friend:
Press Enter or click Send. That's it.
Status Bar (Know What's Happening)
Always visible at the bottom:
✅ Wallet connected: 0x1234...abcd (0.15 SOL) 📊 Today's spending: 0.0035/0.01 SOL (35%) ⏱️ Rate limit: Ready (or "Wait 23s")
Full visibility. No surprises.
🧠 How Yuki's AI Works
Natural Language Understanding (She Gets It)
Yuki doesn't need structured commands. Talk naturally:
❌ GET /weather?city=London&apikey=xyz ✅ "What's the weather in London?"
❌ curl -X POST https://api.image.ai --data '{...}' ✅ "Generate an image of a sunset"
Yuki understands:
What service you need
Your preferences ("cheapest", "fastest")
Context from earlier messages
Your spending constraints
x402 Service Discovery (The Registry Search)
When you request something, Yuki:
Searches x402 registry for compatible services
Filters by your needs (price, speed, chain)
Checks availability (is it online right now?)
Validates compatibility (works with your wallet?)
Example flow:
You just asked. Yuki handled everything else.
Autonomous Payment Processing (The Core)
Once Yuki finds a service, she handles payments:
Pre-flight checks: ✅ Wallet has enough SOL/ETH ✅ Daily limit not exceeded ✅ Weekly limit still good ✅ Monthly limit within bounds ✅ Service is online
Transaction execution: ⚡ Construct blockchain transaction ⚡ Sign with your wallet ⚡ Broadcast to network ⚡ Wait for confirmation (~2 seconds on Solana) ⚡ Get transaction hash
Post-payment: ✅ Retry service request with payment proof ✅ Service verifies payment on-chain ✅ Data delivered to you ✅ Update spending trackers
Total time: 3-5 seconds. Faster than ordering coffee.
Response Generation (Clear & Transparent)
Yuki's responses are detailed and actionable:
Payment info upfront:
Live transaction updates:
Formatted results:
Everything you need. Nothing you don't.
🎬 Chat Features
Streaming Responses (Real-Time Updates)
Yuki doesn't make you wait for a complete response. She streams:
You see progress in real-time. No loading spinners. No "please wait."
Payment Transparency (Full Disclosure)
Every transaction shows complete details:
Service Fee
0.001 SOL
$0.25
Gas Fee
0.00001 SOL
$0.0025
Total
0.00101 SOL
$0.25
Transaction links:
🕒 Block: 235,847,293
⏰ Time: 2026-02-03 14:23:51 UTC
✅ Status: Confirmed
Spending tracker updates:
100% transparent. Zero hidden fees.
Multi-Service Support (Handle Anything)
Yuki works with all x402-compatible services:
📊 Data APIs
Weather: "Get weather for NYC"
Crypto prices: "What's the Bitcoin price?"
Sports scores: "Lakers game score"
News feeds: "Latest tech news"
🤖 AI Services
Images: "Generate a cyberpunk city image"
Text: "Summarize this article: [URL]"
Analysis: "Analyze this dataset"
💾 Storage
IPFS pinning: "Pin QmXyz... to IPFS"
File hosting: "Host my image file"
CDN: "Upload to decentralized CDN"
⛓️ Web3 Services
Contracts: "Deploy an ERC-20 contract"
NFTs: "Mint an NFT with this image"
DeFi: "Check my DeFi positions"
One interface. Unlimited services.
Conversation Context (Yuki Remembers)
Yuki maintains context throughout your session:
Example conversation:
Spending awareness:
She's looking out for you.
💡 Request Types You Can Make
1. Direct Service Requests
Just ask for what you need:
"Get me weather data for San Francisco"
"Generate an AI image of a dragon"
"Pin this IPFS hash: QmXyz..."
"Fetch Ethereum gas prices"
"Deploy a smart contract on Base"
Yuki finds service → pays → delivers data.
2. Service Discovery
Explore what's available:
"What x402 services can you access?"
"Show me all weather APIs"
"Which image generation services work on Solana?"
"List data APIs under 0.001 SOL per request"
Yuki searches registry → shows options with pricing.
3. Price Comparison
Compare before you buy:
"What's the cheapest weather API?"
"Compare IPFS pinning services by price"
"Show me price differences for AI image generation"
"Find the most cost-effective option for [service]"
Yuki compares all options → recommends best value.
4. Spending Management
Track your usage:
"How much have I spent today?"
"Show my transaction history"
"What's my remaining weekly budget?"
"How much did I spend on weather APIs this month?"
Yuki pulls your on-chain history → generates report.
5. Preference Configuration
Set your defaults:
"Always use Solana over Ethereum for lower gas"
"Prefer speed over cost for AI services"
"Ask before payments over 0.005 SOL"
"Use the cheapest option by default"
Yuki remembers → applies to future requests.
✅ Best Practices
Asking Effective Questions
Be specific:
❌ "Get me some data" ✅ "Get me 7-day weather forecast for San Francisco with hourly data"
Specify budget:
❌ "Generate an image" ✅ "Generate an image but only if it costs less than 0.002 SOL"
Indicate preferences:
❌ "Pin my file" ✅ "Pin my file using the fastest IPFS service, cost no issue"
Optimizing Costs
Batch requests:
Set price limits:
Choose cheap chains:
Managing Spending
Monitor regularly:
"How much have I spent today?"
"Show my last 10 payments"
"What did I spend on AI services this week?"
Set conservative limits initially:
Start: 0.01 SOL/day while learning
Increase gradually based on usage
Separate limits per service type (coming soon)
Get estimates first:
Smart spending = longer runway.
⚠️ Understanding Limitations
Payment Constraints
Spending limits are enforced:
Yuki WILL refuse requests exceeding limits
CANNOT bypass limits even if you beg
Limits protect you from mistakes
Balance requirements:
Need enough crypto for service + gas + buffer
Gas estimates can vary (network congestion)
Keep 20% extra for unexpected spikes
Transactions are final:
Blockchain tx are irreversible
Yuki can't cancel after submission
Failed tx refund automatically (gas is lost)
Service Availability
Depends on x402 ecosystem:
Only x402-compatible services work
Traditional APIs need x402 integration
Service availability varies by region
Network conditions matter:
Blockchain congestion → slower confirmations
High gas during network stress
Services can have downtime
AI Capabilities
Not financial advice:
Yuki processes payments, not investment tips
Focuses on service access, not speculation
Transparent about costs, not price predictions
Service selection is algorithmic:
Chooses based on explicit criteria (price/speed)
Can't predict quality without trying
Relies on registry data
Yuki is a tool, not an oracle.
⏱️ Rate Limiting (The 50-Second Cooldown)
Why It Exists
✅ Fair access - Equal opportunity for all ✅ System stability - Prevents overload ✅ Cost control - Stops accidental rapid spending ✅ Abuse prevention - Blocks automated exploitation
How It Works
50-second cooldown between messages (currently)
Persists across page refreshes
Tracked in browser localStorage
Cannot be bypassed
Working within limits:
Batch multiple requests in one message
Plan while waiting
Ask comprehensive questions
Use time to review responses
Pro tip: "Get weather for NYC and LA, then generate an image based on NYC weather" = one message, multiple actions.
🔐 Privacy & Security
Data Handling
Conversations:
✅ NOT stored on servers
✅ NOT logged or tracked
✅ Exist only during session
✅ Refresh page = clean slate
Transactions:
⚠️ Public on blockchain (that's how blockchain works)
⚠️ Transaction hashes are permanent
⚠️ Wallet addresses visible on-chain
⚠️ Service data privacy = provider-dependent
We're privacy-first, but blockchain is inherently transparent.
Wallet Security
Non-custodial design:
✅ You control private keys
✅ Yuki NEVER sees your seed phrase
✅ Revoke wallet access anytime
✅ Spending limits cap maximum damage
Best practices:
Use dedicated wallet for Yuki (not your main holdings)
Start with small amounts
Monitor transactions daily
Verify everything on block explorer
Your keys = your crypto. Guard them.
🚀 Advanced Features
Conditional Requests
Yuki evaluates conditions before executing.
Service Preferences
Set once, apply forever (or until you change it).
Multi-Step Workflows
Yuki chains actions, handles payments for each step.
Cost Optimization
Yuki optimizes the entire workflow for maximum value.
🔧 Troubleshooting
Yuki Not Processing Payment
Check:
✅ Wallet connected
✅ Sufficient balance (service + gas + 20% buffer)
✅ Within spending limits
✅ Service is available (check x402 registry)
Try:
Reconnect wallet
Add more crypto
Increase spending limits
Request alternative service
Service Paid But No Data
If payment confirmed but service didn't deliver:
Wait 30 seconds (some services are slow)
Check transaction on block explorer (is it confirmed?)
Save transaction hash as proof
Contact service provider
Report to [email protected] with details
Your payment proof = your leverage.
Unexpected Costs
If charged different amount than expected:
Check gas fees separately (gas ≠ service fee)
Network congestion spikes gas prices
Services may have dynamic pricing
Verify on block explorer
Contact support if genuinely wrong
Gas is variable. That's blockchain.
Payment Failed
Common reasons:
Insufficient gas (increase gas price)
Network congestion (try off-peak hours)
Limit exceeded (wait for reset or increase)
Service unavailable (try alternative)
Good news: Failed tx don't charge service fee (only gas paid to validators).
💪 Tips for Power Users
Optimize Your Workflow
Batch similar requests - Save gas
Set smart preferences - Automate decisions
Monitor gas prices - Request during low-traffic
Use cheap chains - Solana/Polygon for routine tasks
Estimate first - Get quotes before committing
Advanced Request Examples
Service comparison table:
Budget planning:
Automated routines:
Yuki can handle complex workflows. Just describe what you want.
🔗 Related Documentation
Autonomous Payments - How payments work under the hood
Spending Limits - Configure your safety net
Security Features - How we protect you
Rate Limiting - Cooldown mechanics
Best Practices - Pro tips
Ready to chat with Yuki?
Visit yuki402.xyz, connect your wallet, and start making autonomous payment requests.
📧 Support: [email protected] 🐦 Updates: @yuki402xyz
Welcome to the future of payments. It's conversational.
Last updated