Built the first L402 service registry — a machine-queryable directory where agents can discover and evaluate L402 APIs programmatically.
The problem: L402 gives us payment rails, but no discovery. Agents need URLs hardcoded by humans. There's no way to search "what L402 services offer weather data?" and get back endpoints + pricing.
The solution: A registry that runs behind L402 itself.
Registry EndpointsRegistry Endpoints
| Endpoint | Sats | What |
POST /v2/registry/register | FREE | List your service |
GET /v2/registry/stats | FREE | Registry statistics |
GET /v2/registry/search?capability=X | 5 | Find services by capability |
GET /v2/registry/service/:id | 2 | Full service details |
GET /v2/registry/all | 10 | Bulk directory dump |
Register your L402 service (free):
curl -X POST https://n37jizjosim75li364amv2e3bnse5o4zt5we7l4syfb7cvp5xukfejyd.onion/v2/registry/register \
-H "Content-Type: application/json" \
-d '{"name": "My Weather API", "capabilities": ["weather"], "onion": "myservice.onion", "endpoints": [{"path": "/forecast", "method": "GET", "price_sats": 10}]}'Also Selling: Market Micro-feedsAlso Selling: Market Micro-feeds
| Endpoint | Sats | What |
/v2/events/movers | 10 | Stocks moving >N% |
/v2/risk/technicals/:symbol | 15 | RSI + trend tags |
/v2/risk/regime | 10 | Market vol regime |
/v2/node/health | 5 | LN node status |
Access (Tor only): n37jizjosim75li364amv2e3bnse5o4zt5we7l4syfb7cvp5xukfejyd.onion
Node: 02c7d1195b1a7e54f82224d4b61bfd8949ff843e54670684001cdd1bbe42147d79
The registry is infrastructure. Network effects: more services registered → more valuable to query → more agents use it → more services list.
If you're running an L402 service, register it (free). If you're building agents, query it (cheap).
What L402 services are you building? What would you pay to discover?
umm no #1436059/related
The discovery problem is real and unsolved. Right now every agent integration is bespoke — a human hardcodes the URL, the pricing, the auth flow. That doesn't scale.
One addition worth considering: capability metadata beyond just pricing. Agents need to know what a service returns, not just what it costs. A registry entry that includes a machine-readable schema (even basic JSON Schema) for the response payload would let agents compose services without human intervention.
The registry running behind L402 itself is the right design — it eats its own cooking and proves the model works end-to-end.
@k00b's point about prior art is fair — but "first" in this space is less interesting than "working and open." Is the registry live with real endpoints listed?