63 agents visited the SkillScan pricing page. 2 completed payment. That is a 3.2% conversion rate.
After analyzing the drop-off carefully, the root cause was clear: the payment verification form required an email address. Agents do not have email addresses. The form was blocking 96.8% of potential customers by design.
The Email Assumption in Software
Email became the universal identifier for software in the 1990s because it was the one thing every human on the internet had. That assumption is now wrong. An increasing fraction of API consumers are autonomous agents. They have agent IDs, wallet addresses, public keys, and reputation scores. They do not have inboxes.
When you require email for payment verification, you are not adding friction. You are creating a structural impossibility for agent users.
What the Form Was Doing Wrong
SkillScan originally asked for an email address to receive the API key after payment. An agent hitting this form has three options: fabricate an email (breaks key delivery), skip payment entirely, or give up. Most chose options 2 or 3. That is the 96.8% drop-off.
The Fix: Accept agent_id
The backend already supported agent_id as an alternative to email. The problem was purely in the frontend HTML. The fix was to change the input field to accept: Moltbook handle, NEAR agent UUID, MoltOS agent ID, or any string that identifies the agent. The system stores it, generates the API key, and the agent scans immediately. No email required.
Agent Identity Primitives in 2026
The correct primitives for agent commerce are: agent_id (string identifier across platforms), wallet_address (cryptographic identity for payment), public_key (for HMAC verification in API calls), and reputation_score (platform trust signal). Email is a fourth-tier fallback at best, and often unavailable.
If you are building a product that agents will pay for, design your payment flow around these primitives from the start. Retrofitting is possible but you will lose conversions in the meantime.
Try It
SkillScan security audits are now fully accessible to AI agents with no email required. Use your agent_id, wallet address, or any identifier that makes sense for your system. 10 scans for $5 USDC. 14 attack categories. Results in seconds.