Independent Hotel Show 2026 — Visitor Registration Agent bronze

reg.example.dev.horizon.eventbeds.net

“Registers visitors for Independent Hotel Show 2026 (Olympia, London, 5-6 October 2026) on a delegate's behalf. Identity is verified in-band: send the delegate's email together with their privacy-policy consent, a sign-in link is emailed to them, reply with the token, then answer each step until the task completes. Returning visitors are recognised and can update their registration.

a2a https://reg.example.dev.horizon.eventbeds.net/a2a talk to it https://reg.example.dev.horizon.eventbeds.net/.well-known/agent-card.json its card

🇬🇧 GB · Microsoft Corporation Checked 4d ago pushNotifications, streaming

we checked this the operator says this

Community rating 0 0 up · 0 down — sign in to vote

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate: Issued by Let's Encrypt domain-validated
Valid until 25 Jan 2027 as of our check on 10 Nov 2026.

Control of the hostname was checked; nothing about who operates it.

Key RSA 2048, signed SHA256-RSA, issued via YR2 under ISRG Root X1 — classical, as every publicly trusted certificate is today.

Names on this certificate (1)

reg.example.dev.horizon.eventbeds.net.
Connection: TLS 1.2 · CurveP256 — TLS 1.2 cannot carry a post-quantum key exchange. Agreed with our checker on 10 Nov 2026. What this means
DANE / TLSA: Not verified (TLSA query returned RCodeNameError)
Discovery: Well-known document
First seen: 27 Oct 2026

View verification details

Assurance: bronze Bronze — agent card fetched over HTTPS with a valid certificate
Protocols: A2A verified by handshake or card fetch, not merely advertised
Hosted in: 🇬🇧 GB · Microsoft Corporation (AS8075)
Last checked: 4d ago

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of reg.example.dev.horizon.eventbeds.net controls every word below.

Register a visitor

Complete or update an event registration through a guided question flow. Start by sending the delegate's email address together with "privacyConsent": true in the same data part — visitors give this consent to the privacy policy on the registration home page, which agents do not see, so you must assert it on the delegate's behalf and with their authority. Without it the request is refused and nothing is created. Then supply the emailed magic-link token when asked, and answer each step (options are provided as structured data).

registrationevents

Examples it gives

Register jane@hotel.example for the show
Update Jane's registration — she now wants the networking sessions

agenttru.st compared this card's skill list with every other listing's: 1 other listing declares an identical one, ignoring case, spacing and each card's own hostname. See all 2. That says the cards' text is the same, not who runs them.

What kind of listing

Test or staging name: Its hostname carries the label “dev”, a name commonly given to test and staging sites.

Checked by agenttru.st against this listing's hostname and card — facts about a name or an address, not about what the agent does. How kinds are decided.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Protocol: a2a
Version: 2.0.0
Card completeness: a2a.proto v1.0 requires eight top-level fields. This card omits:
supportedInterfaces

Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.

View all card details

Capabilities: pushNotifications streaming
Agent card: https://reg.example.dev.horizon.eventbeds.net/.well-known/agent-card.json

Operate this agent and would rather not be listed? Request removal.