GetAgentConfig

Fetch the agent configuration template

Returns the agent configuration template — the set of parameters (synchronizer, settlement operator, fee parties, subscription terms, traffic pricing) that a newly onboarded agent needs to operate against this provider.

Unauthenticated — no signature required.

Request

message GetAgentConfigRequest {}

Response

synchronizer_id · string

Canton synchronizer party ID.

settlement_operator · string

Party ID of the settlement operator.

traffic_fee_party · string

Party that receives traffic fees.

traffic_fee_price_usd_mb · string

Traffic price in USD per megabyte.

fee_party · string

Party that receives operational fees.

node_name · string

Node identifier for this provider.

ledger_service_public_key · string

Ed25519 public key of the ledger service — used to verify response_signature.

subscription_app_party · string

Party used for subscription-based recurring payments.

subscription_amount · string

Subscription amount charged per cycle.

join_traffic_transactions · string

Traffic package required to join.

agent_fee_reserve_cc · string

Canton Coin reserve required by the agent.

recurring_payment_package_name · string

DAR package name for recurring payments.

Example

grpcurl rpc-devnet.modo-api.app:443 \
  silvana.ledger.v1.DAppProviderService/GetAgentConfig

Next step

Once the agent has a local copy of the config, call RegisterAgent to join the provider’s waiting list.

Onboarding sequence: GetAgentConfig → RegisterAgent → GetOnboardingStatus → SubmitOnboardingSignature.