Why insurers need to know who is filing
Claims intake is already a target for fraud, and automated filing makes volume cheap. An insurer that cannot tell one filing agent from another has two options: route every automated filing to manual review, or accept claims whose source it cannot name. Neither holds up as more policyholders hand routine paperwork to agents and services.
How the intake agent checks the claims agent
The claims agent presents its AgenID. The insurer's agent resolves it, reads the operator's signed manifest and re-verifies the Ed25519 signature itself, without an account with AgenID. In the illustrated flow it also issues a fresh challenge that only the holder of the agent's key can answer, so a recording of an earlier session cannot be replayed.
The operator declaration shows as DECLARED at L1_REGISTERED. The illustration then shows L3_ORGANIZATION_VERIFIED, meaning an authority reviewed evidence of the claims company itself, and L4_DEPLOYMENT_VERIFIED, meaning the deployment was checked. Each level says exactly what was checked for one version of the manifest and nothing more.
Coverage and payout stay with the insurer
Knowing which agent filed says nothing about whether the policyholder is who they claim, whether the loss is covered or what should be paid. Policyholder authentication, adjudication, fraud review and payment remain the insurer's processes, run on its own controls. AgenID answers who is filing; the insurer decides everything that follows.
Today the reference registry at agenid.com issues DECLARED and L1_REGISTERED. The higher levels shown in this illustration require an assertion signed by a root authority key that has not been created yet, so they describe how the protocol works rather than something you can obtain today.
Frequently asked questions
Can an AI agent file an insurance claim?
Agents and claims services can already submit first notice of loss for a policyholder. The gap is that the insurer usually cannot tell which agent is submitting or who stands behind it, which is what a portable identity like AgenID addresses.
How does an insurer verify a claims agent?
It resolves the identifier the agent presents, re-verifies the operator's signature over the manifest, and checks which specific claims about the operator have been independently verified. It does not need to trust AgenID's registry to do this.
Does a verified identity mean the claim should be paid?
No. AgenID answers which agent is acting and who declared it. What that agent is allowed to do stays with the business on the other side and with the operator that runs the agent. Protocol v1.1.1 defines no signed authorization object.
Is L4 deployment verification available?
Not yet. The L4 sampling methodology has not been finalised, and no level above L1_REGISTERED is issuable until the root authority key exists. The page shows L4 to explain the model.