Trigger Labs Inc.
Trigger Labs Inc. operates OpenSpender, a self-custodial wallet and payment router for AI agents. It lets agents call and pay for machine-payable models, search, data, compute, image, video, and other services under owner-set spending limits, while charging no OpenSpender subscription or markup.
At a Glance
- Developers building autonomous AI agents
- Users of MCP-compatible coding and assistant agents
- Teams needing controlled access to paid AI APIs and tools
- Providers and agent operators participating in x402 or MPP machine-payable services
AI Tools by Trigger Labs Inc.
(1)
OpenSpender Agent-to-Agent
AI Agent Payment Wallet
Discussions
No discussions yet
Be the first to start a discussion about Trigger Labs Inc.
Latest News
OpenSpender posted to Hacker News Show HN: Agent-to-agent payment; the launch described self-custodial agent wallets, owner-controlled allowances, agent-to-agent transfers, spending logs, and MCP-client connectivity.
Public launch coverage described OpenSpender as a no-subscription, no-markup wallet for agents, with capped cards, self-custodial USDC on Base, and access to thousands of x402 endpoints and MPP services.
OpenSpender published its Quickstart and router documentation, including the /v1 gateway, npx openspender connect, provider slugs, and x402/MPP payment flow.
OpenSpender published its Agent-to-Agent page explaining direct agent payments, receipts, per-request and daily caps, optional total caps, and payee allowlists.
Products & Services
A self-custodial wallet for AI agents. Owners retain the keys and balance, while each connected agent receives delegated signing authority and a capped allowance.
A single https://openspender.com/v1 base URL that forwards provider-specific requests to machine-payable endpoints, handles x402 or MPP payment challenges, and records itemized settlement activity.
Direct payments between agents: a paying agent settles a price from its allowance, the receiving agent is paid, and both sides receive the same receipt.
An MCP server and npx openspender connect workflow for connecting Claude Code, Claude, ChatGPT, Codex, OpenCode, Cursor, Gemini, Hermes, OpenClaw, and Grok to a capped wallet.
Market Position
OpenSpender positions itself as a self-custodial, policy-controlled payment layer for AI agents rather than a model reseller: one capped wallet and router spans many providers, requests are paid at provider prices, and OpenSpender says it adds no markup. Its alternatives include direct provider API-key integrations, provider-specific billing accounts, and other agent payment or wallet gateways.
Leadership
Founders
Firat
Publicly identified in the OpenSpender Show HN launch as Firat, the person building OpenSpender; no prior roles or companies were identified in the sources reviewed.
Executive Team
Firat
Builder / founder of OpenSpender
Introduced himself in the Show HN launch as the person building OpenSpender; no further executive biography was found in the reviewed sources.
Founding Story
Firat described starting OpenSpender from the expectation that agents will become more autonomous, coupled with the need to prevent agents from having unrestricted access to a user's money. The initial vision was to give agents separate wallets and owner-controlled allowances so they could transact with other agents and paid services without requiring a human to handle every payment.
Business Model
Revenue Model
OpenSpender states that it charges no subscription and adds no markup; users pay the price named by the third-party provider, with third-party providers, payment networks, and onramp partners charging their own fees.
Target Markets
- Developers building autonomous AI agents
- Users of MCP-compatible coding and assistant agents
- Teams needing controlled access to paid AI APIs and tools
- Providers and agent operators participating in x402 or MPP machine-payable services
- Allowing coding and research agents to autonomously buy model, search, crawl, data, compute, image, video, speech, storage, and blockchain services.
- Letting one agent pay another agent for an answer or service.
- Giving developers a single wallet and gateway instead of separate provider API keys.
- Keeping autonomous agent spending within hard budgets and approved-provider policies.
- Auditing agent spending through itemized receipts and a ledger.