Skip to content
Pre-Launch · Filing seed · Series A — Q4 2026

Developer portal

Build on the clearing spine.

Wavestar exposes a REST surface, a gRPC surface, and four client SDKs — TypeScript, Python, Rust, and Go. The protocol is open and versioned. The sandbox is free. Production keys require clearing-member status.
5-minute quickstartAPI reference
Surfaces
REST · gRPC
SDKs
TS · Py · Rust · Go
License
Apache 2.0
API base
api.wavestar.space

First call

Resolve a did:orbit identifier

Every asset in orbit has a did:orbit identifier. Resolving it returns the DID Document — the public keys, service endpoints, and registry metadata for that asset.
bash
curl -s https://api.wavestar.space/v1/did/resolve/did:orbit:sat:planet:norad-47428

Portal sections

What is here

  • 01

    Quickstart

    Resolve a did:orbit identifier and submit an order in five minutes. Runnable curl and SDK snippets. Go to quickstart
  • 02

    SDKs

    Official SDKs for TypeScript, Python, Rust, and Go. Apache 2.0. Protocol buffers generated from the canonical .proto files. SDK matrix
  • 03

    API reference

    REST and gRPC endpoints across the registry, ORCH clearing engine, Attest quorum, Terminal read-path, and Market discovery. API reference
  • 04

    Protocol specification

    The canonical specification for did:orbit, Attest envelope formats, and the Wavestar settlement protocol. Versioned and hash-anchored. Read the spec
  • 05

    Status and SLAs

    Real-time platform status, per-service uptime, and the published target SLAs. Uses the same transparency-log spine as settlements. status.wavestar.space
  • 06

    Sandbox

    A free, always-on sandbox environment with synthetic order flow, simulated ground-station attestations, and a settlement clock you can control. Quickstart has sandbox keys

By the numbers

Developer platform · v1

API surfaces
0

REST for read-path and tooling; gRPC for settlement-path and member integrations.

SDKs
0

TypeScript, Python, Rust, Go. Protocol buffers shared.

Sandbox latency
p50 22ms

Sandbox is regional; production is multi-region with published latency targets.

Documentation
Open

Apache 2.0 for SDK code and spec documents. CC BY for narrative content.

Principles

How we version and deprecate

  • 01

    Semantic versioning

    All public surfaces follow SemVer 2.0. Breaking changes require a major version bump. Deprecated fields remain for at least one major version window.
  • 02

    Deprecation windows

    A minimum 180-day deprecation window on any public API field. Deprecations are announced in the release notes, in the API response (Deprecation header), and by email to registered integrators.
  • 03

    Backwards-compatible additions

    New fields on existing endpoints are additive and never break older clients. SDKs are updated monthly; the underlying protocol moves more slowly.
  • 04

    Open schema

    All protobuf definitions are public and mirrored to github.com/wavestar/proto. Schema changes go through public review before shipping.

Support and community

Real humans answering developer questions.

Developer support is staffed by the SDK team, not by a ticketing vendor. Email devsupport@wavestar.space with your API key, the endpoint, and a minimal repro — response inside four business hours during working hours.

Start the quickstartEmail developer support