Why providers hesitate to hold a slot for an agent
An arrival window is a real cost for a small provider. Automated requests that never turn into jobs, or that come from nobody in particular, waste a day's schedule. Refusing all of them loses customers who now book through assistants.
Three providers, one identity, three independent checks
The household agent presents the same AgenID to each provider. Each resolves it and re-verifies the operator's signature itself; none relies on another provider's check or on a marketplace in the middle. The operator declaration shows as DECLARED at L1_REGISTERED, which is what Mike says about his own agent, and that is also what the reference registry can issue today.
Because the identity is persistent, a provider can recognize the same household agent next time instead of starting from nothing.
Access, payment and licensing stay between the parties
Which agent booked the job is a different question from who may enter the house. Access, price, the scope of the work and payment are settled between Mike and the plumber, and whether the plumber is licensed is a matter for local licensing, not for AgenID.
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 book a plumber for me?
Agents can already contact providers and request a slot. What the provider usually cannot tell is which agent is asking and who stands behind it, which is what a portable identity adds.
How does a provider verify a booking agent?
It resolves the agent's AgenID and re-verifies the operator's signature on the manifest, then checks which claims have been independently verified. Each provider does this on its own.
Does verification let the agent authorize entry to the home?
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.
Does AgenID verify the plumber?
Only if the plumber's own agent presents an AgenID, and then only its identity and verified claims. Trade licensing, insurance and reviews stay outside AgenID.