RPC Endpoints

The control API is implemented in edge/rpcv1 over a local Unix socket.

Request envelope:

  • version ("v1")

  • method

  • params (method-specific object, optional)

Response envelope:

  • version ("v1")

  • ok (true|false)

  • result (method-specific payload when ok=true)

  • error (code, message) when ok=false

Methods (v1)

Method

Params

Result

status.get

none

StatusResult

quota.list

none

[]QuotaState

quota.peer.get

peer_id

QuotaState

index.list

limit (optional)

[]IndexEntry

index.count

none

IndexCountResult

storage.stats

none

StorageStatsResult

retry.list

none

[]RetryPair

assurance.get

none

AssuranceResult

Error Codes

  • invalid_request — bad JSON, bad version, unknown method, invalid params

  • not_found — requested entity missing (for example unknown peer in quota.peer.get)

  • unavailable — local service dependency unavailable

  • internal — unexpected internal error

Evidence

  • edge/rpcv1/types.go

  • edge/rpcv1/server.go

  • edge/rpcv1/client.go

  • edge/rpcv1/rpcv1_test.go

  • edge/cmd/edged/main.go (RPC server wiring + handler impl)

  • edge/cmd/edgectl/main.go (command RPC integration)

See Also