Contracts earn trust: API-first delivery for teams and for agents
summary
Over 18 months inside a federated finance platform the team turns OpenAPI contracts into executable assets that drive parallel delivery across ~70 engineers and multiple Southeast Asian markets, using Specmatic stubs to run contract tests in CI, Karate end-to-end tests, a registry of GraphQL queries, and a PR-stage impact analysis that blocks breaking changes before merge. Built automation includes an AI-assisted PR reviewer (Mike Bot) and pipelines that force backward-compatibility and keep docs from rotting.
AI-written summary · about
chapters (19)
- 0:00Contract-first API delivery
- 1:10Engineering vs AI tools
- 2:37Integration ownership with contracts
- 4:00Integration structural challenge
- 5:44Domain boundaries for contracts
- 6:48Federated integration service
- 7:50Executable contracts with Specmatic
- 9:34Continuous delivery optimization
- 11:42Impact analysis in pipelines
- 13:07Automating API standards
- 14:54Market interface implementations
- 15:36Trust through collaboration
- 16:19Contracts for agentic systems
- 17:43Queries from contracts
- 18:47Contract-first workflows
- 20:52Discipline with automation
- 22:20Q&A: Security testing
- 24:03Q&A: Agentic ontologies
- 25:29Closing remarks
related talks
50mContract-Driven Development
47mContract-Driven API Development with OpenAPI Specification
26mBuilding APIs for Developers & Machines
20mOpenAPIspec
49mCollaborative Contract Driven Development
32mProject API Forge: Streamlining Dev-First API Lifecycle Management.
19mTrusting Agents With Capital: The Gearbox Playbook
45mAgile API Development, Bringing Testing and Development Together