How it works in AgenID
The manifest's ownership group records the operator name, an operator_domain and a contact. The operator generates an operator key at /issue or with the CLI, signs the ManifestProof and registers; the registry never receives the private key. The operator can also publish its public key at https://<operator_domain>/.well-known/agenid/keys.json, giving verifiers a second, independent copy.
Why it matters
Naming an accountable party turns an anonymous agent into one a business can contact, complain about and decide whether to deal with. The onboarding guide walks operators through registration, attestations and domain evidence.
It also puts the operator's own domain on the record. A relying party can compare operator_domain with the business it thought it was dealing with, and the sales outreach scenario shows why that comparison matters when an agent calls on a company's behalf.
What it does not mean
The operator fields are self-declared. At L1_REGISTERED nobody, including AgenID, has checked that the named company exists or controls the domain. Those checks would be L2 and L3, and both require a VerificationAssertion signed by a root authority key, which has not been created yet. Evidence recorded at /verify/domain raises nothing above L1. Being the operator also says nothing about what the agent is allowed to do for any given business.