lightninglabs / lightninglabs/lightning-agent-tools
Live L402 API gateway for testing & integration: NautDev (8 endpoints, open source)
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 60
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
## What
We built [NautDev](https://nautdev.com) — an L402 API gateway with 8 live endpoints that agents can use for testing and production L402 flows.
## Endpoints Available
| Endpoint | Description | Cost |
|---|---|---|
| `/api/v1/sanctions/check` | OFAC/EU/UK/UN sanctions screening (45,296 entries) | ~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 market data | ~5 sats |
Free endpoints (no payment): `/api/v1/health`, `/api/v1/pricing`, `/api/v1/llm/models`, `/openapi.json`
## MCP Packages
8 packages on npm under `@vbotholemu` scope:
```bash
npm i @vbotholemu/mcp-sanctions-check
npm i @vbotholemu/mcp-llm-inference
# ... and 6 more
```
## Integration with lnget
We have [lnget integration tests](https://github.com/HaveBlue997/l402-apis/tree/main/tests) that verify every endpoint through the full L402 payment cycle. These could serve as reference tests for the lightning-agent-tools ecosystem.
## Why This Matters
Agents using lightning-agent-tools need real L402 endpoints to test against. Our free health/pricing endpoints work without payment for basic connectivity testing. The paid endpoints verify the full 402 → invoice → pay → macaroon → data flow.
## Links
- Live API: https://nautdev.com
- Source (MIT): https://github.com/HaveBlue997/l402-apis
- npm: https://www.npmjs.com/search?q=%40vbotholemu
Happy to help with integration, testing, or documentation. We are building this for the L402 ecosystem.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked l402-apis tests and checking the free /api/v1/health and /api/v1/pricing endpoints. Compare those full L402 payment-cycle tests with this repository’s current integration setup. The issue does not define a specific repository change or completion condition, so the desired integration or documentation scope needs clarification first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100