Apiome Pact
Ship API changes with proof, not hope.
Apiome Pact is a hosted contract-testing platform built around consumer-driven contracts. Consumers register the exact operations and fields they depend on, providers verify against every registered contract, and a can-i-deploy verdict gates each release — turning every version bump into an evidence-backed deployment decision.
What ships with Pact
Every Pact surface is wired into the rest of the Apiome platform — no glue code, no separate identity, no bolt-on integrations.
Hosted Pact broker
A fully managed broker for consumer-driven contracts: every pact, participant, and version in one dashboard with a live compatibility matrix.
Consumer contract registry
Register contracts from the Pact CLI in CI or declare used operations and fields directly in the UI — versioned per project.
Provider verification workflows
Trigger verification against every registered contract from the studio or CI, including replaying spec-derived requests against live deployments.
Can-i-deploy gates
A single aggregate verdict — verification, breaking-change status, and per-consumer compatibility — surfaced in the UI and as a status API.
Consumer-aware breaking analysis
Every diff is classified and intersected with each consumer's contract — so a report says 'breaks 2 of 7 consumers,' not 'something changed.'
Contract-change webhooks & publish gates
Webhooks fire on contract changes with severity filters, signed deliveries, and retries; publishing is blocked when contract tests fail.
A look inside Apiome Pact
Live design previews from the Pact mockup pack — 6 surfaces in total.
Can-I-Deploy answers the only question that matters before a release — a clear verdict, the required pacts behind it, and the CLI invocation for your pipeline.
Provider verification runs report results per consumer, pinpointing the exact failing interaction so provider teams fix the break, not the symptom.
The publish quality gate blocks a version when contract verification fails, lists every rule evaluated, and keeps an audited emergency override.
Use cases
Pact is designed around the way real teams actually work — not the way a tool wants them to work.
Run one broker across dozens of internal services — the compatibility matrix replaces tribal knowledge about who depends on what.
Before merging a schema change, see exactly which consumers it breaks, then fix or negotiate the change with evidence instead of incident reports.
Wire can-i-deploy into the CD pipeline so promotions only proceed when every required pact is verified in the target environment.
- Scoped, read-only CI tokens so pipelines can query diffs and verdicts without write access
- Tenant-level gate policies that escalate warnings to hard blocks, with audited emergency overrides
- Webhook infrastructure with signing, retries, severity filters, and dead-letter queues
- Environment-aware deployment matrices tracking verified versions in staging and production
- Scheduled provider verification with drift alerts against live deployments
- Explains each failed verification in plain language, mapping the failure to the exact schema change
- Predicts the blast radius of a proposed change by intersecting it with every registered contract
- Drafts consumer contracts by analyzing which operations and fields a consumer actually exercises
- Recommends gate policies and severity thresholds based on historical verification outcomes
Contract intelligence that reads the blast radius for you
Pact's AI layer sits on top of the broker's contract graph and breaking-change classifier, turning raw verification output into deployment guidance your whole team can act on.
Every PactAI feature is grounded in your tenant's data, runs under your data-residency policy, and respects every role and ACL the platform enforces.
Every surface in Apiome Pact
A look at the 6 screens designed for this suite — covering everything from day-1 onboarding to day-100 operations.
