Skip to content
Skip to APIMaster Workbench
APIMaster

Design, connect and evolve every API and event contract in your estate.

Bring OpenAPI definitions, event contracts, integration scenarios and their dependencies into one workspace, and see what a contract change costs before it reaches a consumer.

Capability boundary

Local-first by default. Networked capabilities require an explicit action or prior configuration; review their prerequisites in the Trust Center.

What the workbench covers

One workspace for the whole integration landscape

Five domains over one estate, sharing its roles, its audit trail and its release evidence — instead of five tools that each keep their own.

  • Integration landscape

    See every API in the estate with its owner, its criticality and who depends on it.

    • APIs
    • Business domains
    • Owners
    • Consumers
  • Scenario design

    Make cross-system behaviour explicit — the steps, participants and data of a flow.

    • Scenarios
    • Flows
    • Participants
    • Validation
  • Definition workspace

    Import, author, validate and version OpenAPI definitions, then publish and document.

    • SwaggerMaster
    • OpenAPI
    • Schemas
    • Versions
  • Contract intelligence

    Catch breaking API changes before they break consumers.

    • Change Intelligence
    • Schema Diff
    • Contract Radar
    • Consumer impact
    Needs AgentOpen →
  • Event & async contracts

    Register, version and compare AsyncAPI event contracts — the declared contract, not a broker connection.

    • AsyncAPI
    • Channels
    • Messages
    • Kafka, AMQP, MQTT
Packaging truth · V2

Local product, scoped assurance, explicit release holds

Availability describes proven delivery only. Pricing copy never enables a capability, creates an account, starts checkout, or grants a production licence.

No automatic entitlement
  • Community

    Individual API designers

    Available browser-local

    Free local workspace

  • Developer

    Engineers comparing release candidates

    Available browser-local

    Free beta evaluation

  • ContractRadar Team Local

    Teams running a supported local release gate

    Evaluation; annual licence proposal

    Annual local licence — quote required

    UNVERIFIED/HOLD: sales@apimaster.dev is the intended APIMaster-domain sales address, but inbound/outbound delivery, ownership and staffing have not been proved. The application does not expose a mailto action or response-time promise.

  • Contract Release Assurance Pilot

    Teams validating 10–50 contracts

    Requestable scoped pilot

    14 days or 2–4 weeks — custom proposal

  • TMF Release Assurance

    Telecom teams reviewing TMF-based contract cascades

    Source-complete; legal release HOLD

    Scoped proposal after legal approval

    UNVERIFIED/HOLD: sales@apimaster.dev is the intended APIMaster-domain sales address, but inbound/outbound delivery, ownership and staffing have not been proved. The application does not expose a mailto action or response-time promise.

  • Enterprise Self-Hosted

    Organizations requiring customer-controlled runtime boundaries

    Architecture preview; fulfilment HOLD

    Custom annual agreement after verification

    UNVERIFIED/HOLD: sales@apimaster.dev is the intended APIMaster-domain sales address, but inbound/outbound delivery, ownership and staffing have not been proved. The application does not expose a mailto action or response-time promise.

Contract intelligence · detect to evidence

Follow release risk through the existing workbench

One domain of the workbench, in six steps. Each deep-links to a current module; this presentation layer does not copy its domain logic.

  1. 01

    Detect

    Surface watched contract changes from the existing change feed.

    Runs locally in this browser.Open →
  2. 02

    Localize

    Compare schema versions and pinpoint the structural delta.

    Runs locally in this browser.Open →
  3. 03

    Classify

    Review the change through the guided ContractRadar workflow.

    Needs AgentOpen →
  4. 04

    Impact

    Inspect readiness findings and delivery risk already derived by the workbench.

  5. 05

    Gate

    Review and export the existing CI/CD gate result.

    Needs CIOpen →
  6. 06

    Evidence

    Keep the local governance trail and open its evidence view.

Trust boundary

Verifiable product behavior, with explicit exceptions

Open Trust Center →
  • Local-first workspace

    Workspace state remains in the current browser-owned persistence boundary.

  • Explicit outbound flows

    Networked capabilities have documented triggers, prerequisites, and local or remote boundaries.

  • Reviewable evidence

    Existing audit and gate views stay linked instead of being reimplemented here.

Pilot scope template

Scope baseline, scan, impact review, release gate, and evidence

The next page documents the proposed scope and current availability limits. This link sends no workspace data and performs no implicit lead capture.

Start release assurance pilot
Workspace · Northwind Integration

Your API estate, and what needs attention

Designed, validated and simulated APIs across order management, logistics and AI document intelligence.

Attention
Workspace attention queue
Evaluating
Evaluating workspace attention

The persisted workspace is still hydrating; no clear state is reported until evaluation completes.

Operational health score
42At riskOpen insights
Pulse · event density · last 24h

Quiet workspace — no events in the last 24h.

24hnow
APIs
31 active
Endpoints
84 environments
Avg. readiness
58%across workspace
Open issues
31 blocking
Readiness
Ship readiness
  • Order Management APIShip with caution64
  • Shipping & Tracking APIShip with caution75
  • Document AI ExtractionShip ready90
Operations
Latest gateway smoke
No smoke runs yet.
Governance
Pending mapping reviews
No pending reviews.
Schedules
Upcoming runs
No active schedules.
Change Intelligence
Change feed1 breaking unacked
  • BreakingShipping & Tracking API spec: 1.11.0 → 1.12.0 · 4 change(s) · 2 breaking1 day ago
  • ChangedOrder Management API spec: 2.4.0 → 2.4.1 · 2 change(s)ack5 days ago
  • ChangedOrder Management API spec: enum value added on Order.status9 days ago
Audit feed
Most recent governance events
  • No audit events.
Recent activity
Last events
  • Imported Shipping & Tracking API v1.12.0
    63 endpoints · 24 schemas
    2 minutes ago
  • Scenario "split shipment delayed" created
    Order Management · POST /orders/{id}/fulfill
    2 minutes ago
  • Execution run · Document AI extract
    200 · 1.8s · mock
    2 minutes ago
  • 3 endpoints missing example payloads
    Order Management
    2 minutes ago
Environments
Endpoint health
  • Productionhttps://api.northwind.co/ordersno runs yet
  • Staginghttps://stg.api.northwind.co/ordersno runs yet
  • Productionhttps://ship.northwind.co/v1no runs yet
  • Productionhttps://ai-gw.northwind.cono runs yet
Endpoints
Recently touched
  • POST/ordersOrder Management API
  • GET/orders/{id}Order Management API
  • PATCH/orders/{id}Order Management API
  • POST/orders/{id}/fulfillOrder Management API
  • POST/shipmentsShipping & Tracking API
  • GET/shipments/{id}Shipping & Tracking API