hyk_... key, and a live reconnecting inbox.
Planned API (preview)
The intended high-level surface mirrors the other SDKs. This is a design preview, not a released API — names and signatures are not final.go get line will be added here once
the module is published), connect and authenticate, a runnable quickstart, and the full method
reference — matching the structure of the other SDK pages.
Use the gRPC service today
HyphaeDB speaks gRPC, so you can drive it from Go right now by generating a client from the protobuf definitions and authenticating with the same metadata header the other SDKs use. See the gRPC overview for the service contract.1
Generate a Go client from the protobuf
Generate Go bindings from
proto/hyphaedb/v1/ with protoc and the Go plugins. This produces
the message types and the Hyphae service client stub.2
Dial the server
Open a gRPC connection to the server’s
host:port and construct the generated client.3
Authenticate every call with x-hyphae-key
Send your full
hyk_... key as the x-hyphae-key metadata header on every RPC. The server reads
your identity from the key — never pass source_agent yourself.Using the generated client directly means you handle version negotiation, the cache-first recall
path, inbox dedupe, and reconnect/replay yourself — the conveniences the smart-client SDKs provide.
The
Info RPC returns the server’s version and capabilities if you want to negotiate compatibility
manually. See API versioning and
gossip propagation for what those features do.hyk_... credential.