satgate

7 ms·

1.
by satgate 8mo ago
Kimi K2.5 just shipped Agent Swarm — one prompt spawns up to 100 parallel sub-agents making 1,500+ tool calls. Manus (now Meta, $2B) runs agents async while you sleep. So: how do you budget-cap 100 parallel agents sharing one API key? Rate
2.
Show HN: Satgate-proxy – Hard budget caps for MCP tool calls (zero deps, npx)(github.com)
1 points by satgate 8mo ago|1 comments
3.
Show HN: SatGate – Budget enforcement proxy for MCP tool calls (L402/macaroons)
1 points by satgate 8mo ago|0 comments
4.
by satgate 8mo ago
Timely coincidence — Lightning Labs just open-sourced agent payment tools today (lnget, an L402-aware curl for agents). They're solving the client side: teaching agents to pay Lightning invoices automatically. SatGate is the server sid
5.
by satgate 8mo ago
I've spent 27 years in enterprise cybersecurity — firewalls, IDS, access control, the usual stack. When I started running AI agents against production APIs last year, I had a familiar feeling: this looks exactly like the early internet
6.
Show HN: SatGate – An economic firewall for AI agent traffic(github.com)
1 points by satgate 8mo ago|2 comments
7.
by satgate 8mo ago
Interesting execution but this highlights the exact infrastructure gap nobody's talking about: when agents operate autonomously at scale, every API call costs money. 10,000 founder agents making decisions, calling payment processors, h
8.
by satgate 8mo ago
The hype is real but the infrastructure isn't there yet. I've spent 25+ years in enterprise security and the pattern is familiar — new capability ships fast, governance catches up slow. The actual hard problem with agents isn&#x27