waiTransport · Developer tools

Tools to build with WAI, starting free.

The WAI command-line tools, conformance suites and verifiers are open and run anywhere. waiTransport will add hosted tools on top of them: conformance runs, packaging previews and receipt inspection, with a free tier for building and testing.

Roadmap Not yet operating. Each open component below is labelled with where it stands on the WAI status page.

The three labels

In the standard
The open component is in the main branch of the WAI open standard. Its link goes to its row on the dated WAI status page, and its notes are that row's.
Building
The open component is in active development, as the WAI status page lists it.
Roadmap
Planned: a WAI roadmap item, or a waiTransport service. Every waiTransport service is on the roadmap; none is operating yet.

Attested, in WAI, means signed by the party that did the work and measured it: a reader can check the signature, not re-measure the figure. It is not hardware attestation.

01 · The service

What waiTransport will host for developers.

  • Hosted conformance runs: the carriage test and each capability class's check, with a pass or fail per capability and the failing envelope bytes attached.
  • Packaging previews: a source packed under your policy, showing the stage index, the floor and each piece's representation.
  • A receipt inspector that verifies receipt chains, stage claims and session claims and names each failure.
  • Libraries for embedding WAI in players and services, over the reference implementation's C interface.
  • Help preparing a capability for the WAI capability registry: its payload format, its vectors and its conformance check.

A free tier

waiTransport's developer tools will include a free tier, and its terms will be published before the service opens. The open tools are free without limits, under Apache-2.0.

02 · Builds on

Open components, each with its WAI label.

  • In the standard

    The wai command-line tool lists the capability registry and writes its machine-readable export, which CI checks through it.

  • In the standard

    A command-line tool for staged delivery, with the residual refinement payload and a corpus with an independent verifier.

  • In the standard

    Encoders.

    Notes Classical encoding in the command-line tool. The learned and integer encoders are offline tools.

  • In the standard

    A package verifier that refuses, never panics.

  • In the standard

    Conformance corpora, run in CI.

  • In the standard

    Measurement and the session claim in the browser, giving the native tool's figures byte for byte.

  • In the standard

    A C interface over the reference implementation (libwai).

    Notes Built by the ffi feature, which a default build turns on. Without the codec libraries, CI builds it with --no-default-features --features ffi and runs its envelope tests.

03 · Roadmap

Planned, in the standard and in the service.

  • Roadmap· waiTransport

    Hosted conformance runs, packaging previews, a receipt inspector and embedding libraries.

04 · Limits

What this page does not claim.

  • Registering a capability string in the WAI capability registry follows WAI's published procedure, which waiTransport does not gate: how the standard is stewarded.
  • A hosted conformance run reports results; it is not a certification.
05 · Read next

The text behind this page.