Frequently Asked Questions
General Questions
What is Mflo?
Mflo is a pay-per-query dataset marketplace built on the x402 HTTP standard and EIP-3009 meta-transactions. It enables AI agents to access structured data without API keys or subscriptions.
How is this different from traditional APIs?
Traditional APIs require API keys, monthly subscriptions, and complex authentication. Mflo uses wallet-based authentication and micro-payments — you only pay for what you query.
Technical Questions
What wallets are supported?
Currently, MetaMask is supported for the web interface. The MCP server supports any wallet that can provide a private key.
What tokens are accepted?
The demo uses mUSDC, a custom ERC20 token with 6 decimals. In production, this could be USDT, USDC or other stablecoins.
How much do queries cost?
Dataset price:
- 0.50 mUSDC
Can I use this in production?
The current implementation is a proof-of-concept for demonstration purposes. The smart contracts include warnings about production use and recommend audited alternatives.
Setup Questions
How do I get test tokens?
- Visit Faucet (opens in a new tab)
- Connect your wallet
- Add the Monad Testnet Network and Token to your wallet
- Mint mUSDC (Testnet Stable Token) for testing transactions
Can I run this without the web interface?
Yes! The MCP server allows AI agents to access datasets directly without the web UI.
MCP Integration
What is MCP?
Model Context Protocol (MCP) is a standard that allows AI agents to access external tools and data sources securely.
Which AI agents support MCP?
- VS Code with Cline extension
- Cursor IDE (built-in)
- Claude Desktop
- Custom agent frameworks
Do I need to clone repositories?
No! The MCP server installs via npx @mfloai/x402-mcp@demo — no repository cloning required.
Payment Questions
Do users pay gas fees?
No! EIP-3009 meta-transactions allow the facilitator (server) to pay gas fees while users only sign messages.
What happens if a payment fails?
Common failures include:
- Insufficient token balance
- Expired authorization (time bounds)
- Already-used nonce (replay protection)
- Invalid signature
Can I get refunds?
Payments are final once processed on-chain. However, failed payments are not executed, so no tokens are transferred.
How are payments verified?
The x402_API server verifies EIP-712 signatures and executes the transferWithAuthorization function on the smart contract.
Security Questions
Is my private key safe?
Private keys are only used locally by the MCP server process. Use dedicated keys with minimal permissions and rotate them regularly.
How are replay attacks prevented?
Each payment authorization includes a unique nonce. Once used, the nonce cannot be reused, preventing replay attacks.
What about time-based attacks?
Authorizations include validAfter and validBefore timestamps, creating time-bound validity windows.
Troubleshooting
Wallet not connecting?
- Ensure Wallet is installed and unlocked
- Check that you're on the correct network (Monad Testnet)
- Try refreshing the page or restarting the browser
Payment signatures failing?
- Verify your wallet has sufficient mUSDC balance
- Check that the contract address is correct in your environment
- Ensure you're on the right network
MCP server not starting?
- Verify Node.js ≥ 20 is installed
- Check that your
PRIVATE_KEYis properly formatted (starts with0x) - Try running the server manually first:
npx -y @mfloai/x402-mcp@demo
402 errors in production?
- Ensure the x402_API server is running and accessible
- Verify payment requirements are being returned correctly
- Check server logs for payment verification errors
Still Have Questions?
Ask us on X (Twitter) - Follow @mfloai (opens in a new tab) for updates and support.