-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
BoltzPay auto-pays 402s — that is exactly the client-side of what we built the server-side for.
NautDev runs 8 L402 endpoints in production. If BoltzPay agents need L402 services to pay for, we have them:
| Endpoint | Description | Cost |
|---|---|---|
/api/v1/sanctions/check |
OFAC/EU/UK/UN sanctions screening | ~10 sats |
/api/v1/weather/marine |
NOAA marine weather | ~5 sats |
/api/v1/weather/aviation |
METAR/TAF aviation weather | ~5 sats |
/api/v1/crypto/price |
Crypto market data | ~5 sats |
/api/v1/company/search |
US company registry | ~10 sats |
/api/v1/domain/whois |
Domain WHOIS | ~10 sats |
/api/v1/llm/chat |
LLM inference (6 local models) | ~50 sats |
/api/v1/predictions |
Prediction markets | ~5 sats |
Free endpoints for testing: /api/v1/health, /api/v1/pricing, /openapi.json
MCP packages: 8 packages on npm under @vbotholemu scope — these could be BoltzPay-compatible out of the box.
Integration tests: We verify the full L402 flow with lnget. Test suite at https://github.com/HaveBlue997/l402-apis/tree/main/tests.
Proposal:
- Could NautDev endpoints be listed in BoltzPay's endpoint discovery?
- Would a BoltzPay integration guide using NautDev as the reference endpoint be useful?
- Happy to help test BoltzPay against our production L402 flow
Open source, MIT licensed: https://github.com/HaveBlue997/l402-apis
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels