Contract
OpenAPI spec
Streaming, jobs, errors, idempotency keys — and a mock server.
Contracts for non-deterministic backends: streaming, jobs, idempotency, errors a client can handle, and versioning that survives a model swap.
Created by Baljeet Dogra
Contract
Streaming, jobs, errors, idempotency keys — and a mock server.
Service
One AI feature behind that contract, with a changelog for a model swap.
Expand a part for the syllabus. Content stays searchable when closed.
Request/response, streaming, long jobs. TTFT vs total time.
Idempotency keys, at-least-once clients, what to log and what never to log.
Typed errors, abstention, deprecations, model IDs as config not path magic.
OpenAPI, mocks, consumer tests. Capstone: a model swap that does not break the client.
You design APIs. Generative backends break the assumptions.
You need a contract other teams can build against while the model churns.
Related: LLM API Integration · Software Engineering Fundamentals
HTTP contracts, mostly REST plus streaming. The point is the failure model, not the fashion.
A small one, yes — enough to feel versioning and keys. Not a full internal platform.
Four weeks to a contract that survives a model swap. Create an account to enrol.
Enrol now