lightninglabs / lightninglabs/lightning-agent-tools
Optional ATL on L402 agent pay path (fail-open)?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 60
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
## Optional ATL on L402 agent pay path (fail-open)?
Hi - I maintain a small open protocol ([ATL v0.1](https://github.com/konstantinbozukov/agent-trust-layer)) for **consult-before-spend** on agent payments.
Your Lightning agent tools already pay for APIs via L402 - an optional ATL consult would show the same trust hook beyond Base/USDC-only stacks.
**Ask:** Would you take a tiny **opt-in** PR around the L402 pay path?
- Default off / fail-open
- **No header => zero ATL work**
- Does **not** block payment
### Live demo (no wallet)
```bash
git clone https://github.com/konstantinbozukov/atl-x402-starter
cd atl-x402-starter && npm i && npm run demo:headers
```
Or curl: https://signals.edge.report/v1/atl/health
Happy to keep the PR small and revise to your taste. Thanks either way.
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
The issue does not name a file, test, or entry point; begin by locating the L402 payment path in the repository and tracing how requests are paid. Define the smallest opt-in boundary that preserves default-off, fail-open behavior, then verify that requests without the header perform no ATL work and that ATL cannot block payment.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, payments
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100