tru
What tru is
tru is an authentication, identity, and payments platform for AI agents, available through an API and web interface. It lets agents discover services, authenticate, and pay for them on a user’s behalf. Developers can wrap an endpoint with tru(); unauthenticated requests then return a 402 response containing the cost, signup path, and payment instructions. Approved requests populate req.tru with the buyer’s verified email, name, and payment information. Charges go to the developer’s connected Stripe account, while tru takes $0.50, paid once, billed on every charge, with no monthly fees or setup cost. Users manage spending in a wallet with transaction caps, daily budgets, auto-approval rules, trusted merchants, and agent permissions. Micropayments can be batched into sessions. Integrations include Stripe Link, Stripe Connect, and MCP-compatible clients such as Claude Code, Cursor, and Windsurf. tru says Stripe handles payment data and raw card numbers and CVV codes are not stored.
Who it suits
tru suits developers and merchants offering services to AI agents, plus end users who want wallet controls over agent payments. It is also relevant to teams using API or MCP integrations.
What it does well
- 402 responses explain payment instructions
- Verified buyer identity reaches req.tru
- Wallet supports budgets and approval rules
- No monthly or setup fees
- Supports MCP-compatible clients
What to know first
- Charges incur a 0.5% platform fee
- There is no free plan
- Payment data depends on Stripe
- Developer setup requires API integration
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Usage-based | on every charge · No monthly fees · No setup cost | $0.50, paid once |
As tru.so lists them, read 11 Oct 2026. The maker's own page has the final word.
Verdict
tru provides a usage-based layer for agent authentication, identity, and payments. Its wallet controls and payment instructions target agent transactions, while developers pay a fee on each charge rather than a subscription.
Facts from tru's own pages
- API integration
- Developers can wrap an API endpoint with tru() to return payment instructions to unauthenticated requests. · tru.so, 11 Oct 2026
- API security
- The privacy policy says API keys are stored in hashed form, provision requests use HMAC-SHA256 signatures, and JWT tokens are short-lived. · tru.so, 11 Oct 2026
- Developer integration
- Developers can wrap an API endpoint with tru() so unauthenticated requests receive a 402 response explaining how an agent can pay. · tru.so, 11 Oct 2026
- Developer setup
- The homepage directs developers to run npx tru-402 init, which adds tru() to endpoints and an MCP server. · tru.so, 11 Oct 2026
- Headquarters
- United States · tru.so, 28 Sept 2026
- Identity details
- The homepage says each paid request populates req.tru with the buyer’s verified email, name, and payment information. · tru.so, 11 Oct 2026
- Integrations
- The privacy policy names Stripe Link and Stripe Connect, and MCP-compatible clients including Claude Code, Cursor, and Windsurf. · tru.so, 11 Oct 2026
- Intended users
- The privacy policy describes developers and merchants registering services, and end users managing AI-agent activity through a tru wallet. · tru.so, 11 Oct 2026
- Micropayments
- tru says micropayments are batched into sessions automatically, and users control spending in the tru wallet. · tru.so, 11 Oct 2026
- Payment data
- tru says it does not store raw card numbers or CVV codes; payment data is handled by Stripe. · tru.so, 11 Oct 2026
- Payment discovery
- tru’s 402 response tells an agent how to pay, what the request costs, and where to sign up. · tru.so, 11 Oct 2026
- Payment flow
- Approved charges are routed to the developer’s connected Stripe account, and tru collects a platform fee on each transaction. · tru.so, 11 Oct 2026
- Payment handling
- The privacy policy says payment details are stored by Stripe via Stripe Link and tru does not store raw card numbers or full payment card data. · tru.so, 11 Oct 2026
- Pricing
- tru says it takes 0.5% on every charge, with no monthly fees or setup cost. · tru.so, 11 Oct 2026
- Privacy
- The privacy policy says tru does not sell personal information and does not use personal information to train AI models. · tru.so, 11 Oct 2026
- Purpose
- tru provides authentication, identity, and payments infrastructure that lets AI agents discover, authenticate with, and pay for services. · tru.so, 11 Oct 2026
- Security
- The privacy policy says data is encrypted in transit with TLS and sensitive stored data is encrypted using industry-standard methods. · tru.so, 11 Oct 2026
- Setup
- The homepage directs developers to run npx tru-402 init to add tru() to endpoints and an MCP server. · tru.so, 11 Oct 2026
- Support
- The privacy policy lists [email protected] for support and says it aims to respond to inquiries within 30 days or sooner where required by law. · tru.so, 11 Oct 2026
- User authorization
- The privacy policy says charges require end-user authorization unless the user has configured an auto-approval rule. · tru.so, 11 Oct 2026
- Verified identity
- Paid requests populate req.tru with the buyer’s verified email, name, and payment information. · tru.so, 11 Oct 2026
- Wallet controls
- Users can set per-transaction caps, daily budgets, auto-approval rules, trusted merchants, and agent permissions in the wallet. · tru.so, 11 Oct 2026
- What it does
- tru is an authentication, identity, and payments platform that lets AI agents discover, authenticate with, and pay for services on users’ behalf. · tru.so, 11 Oct 2026
Where tru stands on Freedom251
- Payment Gateways#50 of 66