pub struct EndpointSummary {
pub name: String,
pub label: String,
pub base_url: String,
pub dialect: DialectKind,
pub connection_kind: String,
pub models: Vec<ModelFactsSummary>,
pub local: bool,
pub has_credential: bool,
pub tuning: EndpointTuning,
pub account_status: Vec<AccountStatus>,
}Expand description
One attached endpoint, as a reader may see it. No credential appears
here in any form; has_credential answers the only question a page
needs, which is whether one was enrolled at all.
Fields§
§name: String§label: StringWhat to call it on screen. The id it was filed under when the person gave it no other name, so a page never has to decide what to show when a label is missing.
base_url: String§dialect: DialectKind§connection_kind: StringHow this endpoint is connected, as one flat word:
openai_compat, responses or anthropic_native.
Resolved once when the endpoint was attached and read back
here. dialect beside it answers a narrower question - which
request writer runs - and two connections can share a writer
while being different registrations, so a page given only the
writer cannot say which one a person set up. The word’s one
authority is gateway::provider::registry::ConnectionKind.
models: Vec<ModelFactsSummary>The models this endpoint serves, with what it said about each.
local: boolWhether calls to it stay on this machine, which is the only thing a confidential building may use.
has_credential: bool§tuning: EndpointTuningWhat the person attached this endpoint with, read back in the
shape AttachEndpoint carries it: a page that changes the account
list sends this back whole with only accounts replaced, so the
figures, headers and overrides nobody touched stay as they were
(crates/wire/spec/Answer/Endpoints.lean §8-85, wire D49).
account_status: Vec<AccountStatus>Whether each listed account’s key is there, one row per id in the
order of tuning.accounts; empty for an endpoint registered
without an account list.