Company profile · 3 min read
Allowance: Scoped payment authority for AI agents
Allowance lets users approve constrained, one-time payment credentials so agents can complete purchases without exposing a real card number.
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
Published · Updated
Allowance is a spend-control layer for AI agents. It fits products that want agents to buy something on a user’s behalf without handing the agent an unrestricted card.
What it does
Allowance’s YC profile describes a system where users approve purchases from an iPhone with controls for spending limits, merchant restrictions and expiration windows. Once approved, Allowance generates scoped, one-time payment credentials for the transaction.
That is a useful product boundary. The agent can complete a shopping, food-ordering, booking or ticket task, but the human decides how much authority to grant and for how long. This is closer to programmable consent than to a generic virtual card.
Why I’d look closer
The product is aimed at a problem that gets worse as agents become more useful: the agent can find the right thing, but who is allowed to pay? A scoped credential can separate the task from the user’s real card number and create a review point before the purchase.
The founder context is relevant. The YC profile describes Dasmer Singh as a former Head of Product for Cash App Families, with previous roles at Uber, Petal and Venmo. That is public professional history connected to payments and family controls; it is not evidence that Allowance is currently available for every use case.
What could make it the wrong choice
Permission design is the product. A user needs to understand merchant restrictions, spending limits, expiry, refunds, disputes and what happens if an agent retries. A one-time credential reduces exposure, but it does not make a bad purchase decision harmless.
The retained public sources do not provide pricing, supported merchants, geographic availability or a live developer contract. Those omissions matter because payment products have to be judged by the action boundary, not only the authorization story.
My editorial take
I would shortlist Allowance for an agent product that has a clear purchase task and needs constrained user approval. I would not add it as a decorative “agent payments” layer before defining the exact transaction, refund path and user consent. The useful idea is to make authority narrow and visible.
Quick facts
| Field | Sourced detail |
|---|---|
| Product | Scoped payment credentials and approval controls for agents |
| Buyer | Agent builders and users delegating purchases |
| Controls | Limits, merchant restrictions and expiration windows, company-described |
| Founder context | Former Cash App Families product lead, per YC |
| Pricing/availability | Not publicly observed in retained sources |
Sources checked
| Source | Checked |
|---|---|
| YC profile | 2026-09-19 |
| Allowance homepage | 2026-09-19 |
Cohort context
Allowance is listed in Spring 2026. In our 2026-09-18 directory snapshot, 21 of 193 listed companies in that cohort have YC’s primary industry label Fintech (10.9%). This is a current-directory comparison, not an original intake count or a performance ranking. Nine-cohort dataset.
Public website snapshot
Observed 2026-09-19T16:16:02.755Z in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.
| Signal | Homepage observation |
|---|---|
| Product description metadata | Observed |
| Canonical link | Observed |
| H1 or H2 heading | Observed |
| Typed structured data | Observed |
| Docs/developer link | Not observed in this response |
| Pricing link | Not observed in this response |
| llms.txt link | Not observed in this response |
| Markdown alternate | Not observed in this response |
Public observations · Collection method. Missing links here do not establish that a capability or file is absent elsewhere.
About the author
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.
First1000 ↗ · X ↗