Alloy developer platform

Build against the API contract

Integrate from the same versioned Protobuf and OpenAPI sources used by Alloy services and client libraries. Each published route, message, and compatibility rule is traceable to the canonical contract.

View API reference Download Protobuf

Contract: mesh-v1.0.0-m0
Transports: gRPC and HTTP/JSON
Published routes: 5 versioned operations

One source chain

The Protobuf service definition is canonical. OpenAPI artifacts and client surfaces are generated or parity-checked against it so implementation and documentation cannot drift silently.

PROTOBUF V3

Service contract

RPCs, messages, enums, and HTTP annotations.

OPENAPI 3.1

HTTP contract

Readable schemas for client generation and review.

SWAGGER 2.0

Generated artifact

Machine-readable output from the Protobuf contract.

Published operations

Generated from the current Swagger artifact.

Full API reference

Method	Route	Operation
POST	/v1/dkg/initiate	MpcWalletService_InitiateDkg
POST	/v1/dkg/shares	MpcWalletService_ExchangeDkgShares
POST	/v1/sessions/resume	MpcWalletService_ResumeSession
POST	/v1/signing/initiate	MpcWalletService_InitiateSigning
POST	/v1/signing/share	MpcWalletService_SubmitSignatureShare

Compatibility is explicit

Exact version declaration

Clients identify their contract version in the orchestration context. Unsupported versions fail closed instead of silently downgrading.

Traceable releases

Schema, generated artifacts, services, and client libraries move together under the contract release process.