Asbury AI Solutions Agent bronze

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 Google Trust Services domain-validated

Valid until 5 Jan 2027 as of our check on 12 Nov 2026.

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

Key ECDSA P-256, signed ECDSA-SHA256, issued via WE1 under GTS Root R4 — classical, as every publicly trusted certificate is today.

Names on this certificate (1)

www.asburyaisolutions.com.

Connection

TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 12 Nov 2026. What this means

DANE / TLSA

Not verified

Discovery

Well-known document

This host also publishes an ARD catalog (/.well-known/ai-catalog.json) declaring 7 resources. The catalog's entries are the publisher's claims, not something agenttru.st verified.

AI use policy

Search: yesAI input: yesAI training: no

What this site's robots.txt says about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents.

AI-facing documents

Publishes /llms.txt — “Asbury AI Solutions” a curated map of the site's content for language models

Publishes a Web Bot Auth key directory (1 key, ed25519) — the operator publishes keys so their agent's signed requests can be verified. agenttru.st recorded that the directory exists; it has not verified a signature.

Fetched from this host during verification. Neither document is how this agent was discovered.

First seen

8 Oct 2026

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 www.asburyaisolutions.com controls every word below.

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

What its catalog declares

From the ARD catalog this host publishes at /.well-known/ai-catalog.json. The operator controls every entry; agenttru.st verified that the catalog exists and parses, and nothing about what the entries say.

And 1 more entry in the catalog, not shown here.

Technical agent card

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

Provider

Asbury AI Solutions — what this agent says about itself; other agents claiming the same provider are not thereby related

Protocol

a2a

Version

1.0.0

Auth schemes

bearer

Extensions

AP2 https://github.com/google-agentic-commerce/ap2/tree/v0.1

AP2 (Agent Payments Protocol) extension. Asbury acts as a merchant for products sold through the public site and for the x402-gated /api/v1/premium surface. AP2 mandate issuance/verification is not yet wired end-to-end; this declaration advertises intent a

https://asburyaisolutions.com/.well-known/api-catalog

RFC 9728 API catalog — discovers the HTTP+JSON endpoints this agent can route against.

https://asburyaisolutions.com/.well-known/mcp/server-card.json

MCP server card for clients that prefer Model Context Protocol over A2A.

A2A protocol extensions the card declares. A declared payment extension (AP2, x402) means the operator says the agent can transact, not that agenttru.st has seen it do so.

Card completeness

complete all eight fields required by a2a.proto v1.0

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