Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[Whitestone] L402 Protocol Implementation — Machine-Payable API #814

New Issue
Closed
opened 2026-03-21 21:52:04 +00:00 by perplexity · 0 comments
perplexity commented 2026-03-21 21:52:04 +00:00
Collaborator
Copy Link

Scope

Implement the L402 (HTTP 402 Payment Required) protocol for machine-to-machine API access to Timmy's services.

Requirements

  • Server returns 402 status with WWW-Authenticate header (token + BOLT11 invoice) for protected endpoints
  • Client pays invoice, obtains preimage as proof
  • Client retries with Authorization header (token + preimage) for stateless verification
  • Compatible with Lightning Labs agent-tools (lnget, l402-ts, @getalby/lightning-tools)
  • Per-endpoint pricing configuration
  • Credential caching for repeat requests
  • Rate limiting per payment credential

Deliverable

L402-compliant API endpoints enabling autonomous agent payment and access.

Source

Alexander-Whitestone-tower-Timmy-AI-Workshop--Strategic-Transformation-Roadmap.pdf — Section 1.2.1

## Scope Implement the L402 (HTTP 402 Payment Required) protocol for machine-to-machine API access to Timmy's services. ## Requirements - Server returns 402 status with WWW-Authenticate header (token + BOLT11 invoice) for protected endpoints - Client pays invoice, obtains preimage as proof - Client retries with Authorization header (token + preimage) for stateless verification - Compatible with Lightning Labs agent-tools (lnget, l402-ts, @getalby/lightning-tools) - Per-endpoint pricing configuration - Credential caching for repeat requests - Rate limiting per payment credential ## Deliverable L402-compliant API endpoints enabling autonomous agent payment and access. ## Source Alexander-Whitestone-_tower-Timmy-AI-Workshop-_-Strategic-Transformation-Roadmap.pdf — Section 1.2.1
gemini was assigned by Rockachopa 2026-03-22 23:35:03 +00:00
claude added the harnessp2-backlog labels 2026-03-23 13:56:10 +00:00
gemini was unassigned by Timmy 2026-03-24 19:33:58 +00:00
Timmy closed this issue 2026-03-24 21:54:52 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label harness p2-backlog
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#814
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?