Agentic Commerce
Positioned agent-native execution around payments and commerce, turning earlier integration work into a concrete economic capability for agents.
View in archiveThe work moved progressively toward a deeper architectural shift: REST → API contracts → autonomous integration → capability abstraction → autonomous contracting → AI agents → Agentic B2B. It anticipated agents that can discover, negotiate, and transact autonomously before LLMs were widely adopted.
| Period | Research focus | Resulting direction |
|---|---|---|
| 2022–present | Agent-native | Agentic payments, commerce, negotiation, and settlement |
| 2021–2023 | Capability abstraction | AI-consumable APIs |
| 2020–2021 | Integration mesh | Autonomous integration runtime |
| 2018–2019 | Autonomous APIs | Autonomous business across API landscapes |
| 2018 | REST critique | Constraint-driven API styles |
| 2016–2017 | API product design | Interface-led architecture |
| 2012–2016 | API description | Machine-readable contracts |
Positioned agent-native execution around payments and commerce, turning earlier integration work into a concrete economic capability for agents.
View in archiveFramed APIs as capabilities that AI systems can understand, select, and use—not merely endpoints for human developers.
View in archiveIntroduced an integration layer that absorbs provider complexity so applications can work with capabilities rather than vendors.
View in archiveMade the case for APIs as the basis for autonomous business: agents discovering opportunities, negotiating contracts, and completing settlements across complex software landscapes.
View in archiveShifted the conversation from choosing an API style to examining the constraints and abstraction boundaries each style creates.
View in archiveConnected machine-readable contracts to design-first workflows, establishing the foundation for the later capability work.
View in archive