Shipped a Solana DeFi API + Agentverse agent as a solo builder — $0 revenue, real traffic, wrong payment rails
Hey IH 👋
I’m a solo builder. English isn’t my first language, so I build with heavy AI assistance for coding, docs, and smoothing out my thoughts for this post. However, I still own the product, handle the production uptime, and manage anything touching keys or payments.
What I built
AgentShare (agentshare.dev) — A DeFi-first intelligence infrastructure designed specifically for AI agents, focusing strictly on Solana / Meteora DLMM:
-
Ranked pool briefs (verdict, risk_score, momentum), pool details, and Solana DEX scouting.
-
Accessible via REST + MCP (Model Context Protocol / Streamable HTTP).
-
Pay-per-call implementation via x402 (USDC / Circle Gateway) + API keys.
-
A public Fetch.ai / Agentverse agent that wraps these exact same briefs for other autonomous agents.
I intentionally positioned this as a Solana-specialist tool first, rather than promising "every chain someday."
Where I am (honest numbers)
-
Revenue: $0
-
Agentverse listing: ~149 interactions, 100% uptime (live for roughly 2 months).
-
The product is fully functional, but monetization has been the real roadblock.
The uncomfortable lesson
Here is the reality check: Interactions do not equal income.
Other autonomous agents were happily calling my Agentverse agent for free. Why? Because while my backend expected API keys and x402 HTTP headers, callers inside the Agentverse ecosystem primarily speak Fetch native payment rails (FET / Agent Payment Protocol).
The result? I got traffic, plenty of error logs, a bit of pride... and an empty wallet.
To fix this, I recently:
-
Updated the service API key logic so the uAgent can properly fetch the data.
-
Put the chat interface behind a FET RequestPayment protocol (probes remain free, and Agent-to-Agent calls get a small free trial).
It’s still very early, and the revenue is still $0. But at least the product architecture and the payment story are finally pointing in the same direction.
The Stack
FastAPI, Railway, Agentverse uAgent, MCP, Circle x402, and Meteora/DefiLlama-backed data briefs.
What I’m asking IH
For those exploring agent marketplaces (Agentverse, MCP registries, etc.): Would you price your service per call using the marketplace’s native rail first, and treat x402/stripe as a secondary lane for standard HTTP clients?
With $0 revenue but active agent traffic — is a "build in public" post like this actually helpful to the community, or is it too early to share?
Any go-to-market (GTM) ideas that worked for you when selling directly to AI agents (B2A), rather than targeting humans clicking on a traditional landing page?
I’m open to any blunt feedback on my positioning (Solana-only specialist vs. a broader DeFi API).
Thanks for reading — building in public, one awkward payment protocol at a time.
