Lattice Hub Docs

gRPC APIs

Discovery gRPC (8091) and Config gRPC (8093) entry points; contracts live in Specification.

The control plane exposes two native gRPC entry points for clients. Message types and RPCs live in pole-io/specification. This page covers ports, roles, and how they relate to HTTP.

Entries

PluginDefault portContract focusTypical consumers
service-grpc8091DiscoverGRPC: register, discover, heartbeat, governance/contract viewsRust SDK and other gRPC clients
config-grpc8093ConfigGRPC: config create/update/publish/discoverConfig clients / SDKs

TLS and connection limits live under each plugin option (tls, connLimit, enableCacheProto, …).

Relation to the HTTP API

CapabilityHTTP (8090)gRPC (8091 / 8093)
Console management CRUD/naming/v1, /config/v1, /core/v1, …Full Console surface is not exposed over gRPC
Client Discover / Register / Heartbeat/naming/v1/Discover, …Primary path via service-grpc
Config clients/config/v1 client groupPrimary path via config-grpc
MCP / A2A Registry management/ai/mcp/v1, /ai/a2a/v1Management APIs are on HTTP

Prefer gRPC for SDKs; prefer HTTP OpenAPI for automation and Console-backed calls.

Contract modules (index)

Full module table: Specification. Directly related to gRPC:

  • api/v1/service_manage: DiscoverGRPC, instances, clients, service contracts
  • api/v1/config_manage: ConfigGRPC
  • api/v1/traffic_manage / fault_tolerance / security: governance and identity views Discover can return

Discoverable resource types include Namespaces, Services, Instances, Service Contracts, the nine governance rule types, Service Identity, and more.

Authorization boundary

gRPC adapters extract credentials, then enter the same domain Servers and auth interceptors as HTTP. Management auth is separate from workload credentials; the data-plane credential header is x-pole-workload-credential and must not be mixed with Console/API management tokens. See Authorization and resources and Specification security notes.

On this page