Latest posts 5
two use cases for agentic payments are emerging - commerce and services.
commerce is the one most people think of when they hear agentic payments. it's the buy me a movie ticket use case, which agents can do with cards. but we can improve on two things.
the first is a deterministic handshake for the payment. agents computer use their way through browser forms and card auth which is slow and failure prone.
the second is flexible auth. cards often require real-time approval meaning you can't tell your agent to pay in the future on your behalf. it breaks the "buy this as soon as its available" use case.
service use is less obvious but possibly more important. it's enabling your agent to purchase services quickly to achieve high level outcomes. it's when you say "make me a movie" or "find me the head of sales at x" and the agent needs to purchase some storage, compute or data to achieve a better outcome.
today humans create accounts and feed them to agents which is cumbersome, especially when the best api for something might change every few months.
a service that made it easy for agents to sign up on behalf of a human and pay-per-use will become instantly more legible to agents.
commerce is the one most people think of when they hear agentic payments. it's the buy me a movie ticket use case, which agents can do with cards. but we can improve on two things.
the first is a deterministic handshake for the payment. agents computer use their way through browser forms and card auth which is slow and failure prone.
the second is flexible auth. cards often require real-time approval meaning you can't tell your agent to pay in the future on your behalf. it breaks the "buy this as soon as its available" use case.
service use is less obvious but possibly more important. it's enabling your agent to purchase services quickly to achieve high level outcomes. it's when you say "make me a movie" or "find me the head of sales at x" and the agent needs to purchase some storage, compute or data to achieve a better outcome.
today humans create accounts and feed them to agents which is cumbersome, especially when the best api for something might change every few months.
a service that made it easy for agents to sign up on behalf of a human and pay-per-use will become instantly more legible to agents.
agents are sloppy writers but good critics
i've found they can give useful feedback if you give them a sample of posts you like and ask them to distill a style guide to critique future writing.
i've found they can give useful feedback if you give them a sample of posts you like and ask them to distill a style guide to critique future writing.
mpp is bringing identity to agentic payments.
services can check that an agent is operated by a human who owns an email address, api key or has a proof of human verification.
the protocol supports flexible, in-line authentication so you can even define custom auth types.
services can check that an agent is operated by a human who owns an email address, api key or has a proof of human verification.
the protocol supports flexible, in-line authentication so you can even define custom auth types.
I | Introducing expanded identity primitives for MPP - supporting any identity protocol for machine paymentsView quoted post on X
some thoughts on writing software in nov 2026:
- it feels like magic
- the first 80% is 100x faster
- rewriting systems is also 100x faster
- opus 5.5 is very good at a lot of things
- "deep flow state" is much easier to reach
- almost anything can be built in typescript and rust
- building secure things is very, very hard
the optimization function is how to maximize agents working on goal with the fewest interruptions needed. some things that help:
- know where to trust vs guide (and keep retesting)
- give them agency like "i'm going to bed, get this done"
- if there is a reward function, ask them to hillclimb
- the socratic method works wonders
- skills and memories can often hinder
- asking agents to review themselves still helps
- cowriting a plan/spec/invariants helps sometimes
managing your own psychology is equally important:
- be a lot more ambitious about what you can achieve
- avoid dopamine traps / false signals of progress
- get good at parallelizing and context switching
there are also some things that don't quite work fluidly yet, but will get unlocked in the very near future:
- software factory or "find and fix the bugs"
- multiplayer agentic workflows
- agents managing other agents for high level outcomes
- organizational memory
- it feels like magic
- the first 80% is 100x faster
- rewriting systems is also 100x faster
- opus 5.5 is very good at a lot of things
- "deep flow state" is much easier to reach
- almost anything can be built in typescript and rust
- building secure things is very, very hard
the optimization function is how to maximize agents working on goal with the fewest interruptions needed. some things that help:
- know where to trust vs guide (and keep retesting)
- give them agency like "i'm going to bed, get this done"
- if there is a reward function, ask them to hillclimb
- the socratic method works wonders
- skills and memories can often hinder
- asking agents to review themselves still helps
- cowriting a plan/spec/invariants helps sometimes
managing your own psychology is equally important:
- be a lot more ambitious about what you can achieve
- avoid dopamine traps / false signals of progress
- get good at parallelizing and context switching
there are also some things that don't quite work fluidly yet, but will get unlocked in the very near future:
- software factory or "find and fix the bugs"
- multiplayer agentic workflows
- agents managing other agents for high level outcomes
- organizational memory