01 / PLANNED
A focused change list
Planned comparison rules would highlight removals, required-field changes, and other compatibility questions.
API change review · Early research
Connect an API change to the clients that need attention.
A planned API compatibility review workspace for schema changes, consumer ownership, and migration evidence. Join the early research waitlist.
Get early access ↗In research · Join the waitlist · No payment required
Designed around small API teams maintaining external integrations or several internal client applications.
Concept preview · fictional workflow
| Contract change | Consumer | Next step |
|---|---|---|
| Field becomes required | Mobile client | Test request builder |
| Enum gains a value | Export service | Review parser |
| Endpoint deprecated | Partner integration | Confirm migration |
Illustrative sample data. This is a product concept; these features are not available yet.
MADE FOR THE WORK IN BETWEEN↗
THE FRICTION
A schema diff identifies a changed field, but does not know which client depends on it or whether its owner has tested the replacement. Release planning still happens across tickets and messages.
THE PRODUCT WE’RE EXPLORING
ContractSignal, in three parts.
ContractSignal would link proposed API changes to known consumers and review decisions. The first pilot would focus on OpenAPI specifications and manually declared client ownership.
Three planned capabilities we want to validate with early users.
02 / PLANNED
Consumer impact notes
Proposed records would connect each change to client owners and the assumptions they need to check.
03 / PLANNED
Migration evidence
Planned review states would distinguish a promised update from a tested client migration.
AN INTENDED WORKFLOW
A clearer next step.
Less work around it.
A focused approach for small API teams maintaining external integrations or several internal client applications.
- 01
Compare proposed specifications
Provide authorized, sanitized versions of an API contract in a future pilot.
- 02
Assign affected consumers
Review possible impact with the people responsible for declared clients.
- 03
Record release readiness
Attach test evidence and migration notes before a person approves the release.
HELP SHAPE THE FIRST VERSION
A better workflow starts with your experience.
Join the ContractSignal waitlist for early-access updates and an optional research conversation.
This product is in research. Planned features and integrations are not available yet.
NO PAYMENT · NO COMMITTED LAUNCH DATEYOU’RE ON THE LIST
Thanks for raising your hand.
Your signup has been received for ContractSignal. There is no confirmation email to look out for.
Manage your data ↗GOOD TO KNOW
A few useful answers.
Can I upload specifications now?
No. ContractSignal is a waitlist. Schema comparison, consumer maps, and review workspaces are planned.
Can a schema check prove compatibility?
No. Runtime behavior, undocumented clients, and data semantics can differ from a specification. People and integration tests must still validate changes.
Will it modify APIs or deploy releases?
No automatic deployment is proposed. The first version would provide review evidence for your existing release process.