Lattice Hub Docs
HTTP OpenAPI

HTTP OpenAPI

Control-plane 8090 HTTP API organized by scenario—namespaces, services, instances, config, and governance.

The HTTP API is served by api-http on port 8090. Pick a scenario below. Each page uses a parameters-left / examples-right layout.

Scenario index

ScenarioNotes
Authentication
Login & statusLogin / system
UsersUser CRUD and tokens
GroupsUser-group CRUD
RolesRole CRUD
PoliciesPolicies and authorization
Admin APIsOps management APIs
NamespacesEnvironment namespaces
Services
Services · BasicsService CRUD
Services · ContractsContracts and reporting
Services · TopologySubscribers / call relations
Services · InstancesInstance register and manage
Config
Config groupsConfig groups
Config filesFile read/write
Config graynormal / gray publish
Config templatesConfig templates
Governance
RoutingRoute rules
Rate limitRate-limit rules
Circuit breakerCircuit-breaker rules
Fault detectActive probing
LaneLane rules
LosslessLossless rules
Traffic securityCall authorization
Traffic mirrorMirror rules
Traffic mockMock rules
AI Registry
MCP RegistryMCP Server / Tool
A2A RegistryA2A Agent / Skill
Client APIsDiscover / Register / pull config

Conventions

ItemNotes
Base URLhttp://127.0.0.1:8090
Management authAuthorization (token from login)
Feature gatesapi-http.api.{console,client,admin,aimcp,aia2a}
Write bodiesUsually a protobuf message array [{...}]; docs list the full per-item field tree (nested children)
Nested shapesrules / routing_config / health_check etc. are expanded from specification; Any lists unpackable messages by policy
Response fieldsWrite APIs also list entity response field trees; sample JSON is on the right

Parameters and paths follow control-plane httpserver Enrich annotations and specification protos; the running server is authoritative.

On this page