CiteBrand bronze
citebrand.ai
“Measures whether AI engines name and link a brand for buyer questions, per lane (assistants, AI apps, search-page AI), with sample sizes, sources and resolvable evidence for every claim; returns evidence-cited plans and monitors change week over week.
a2a https://api.citebrand.ai/v1 talk to it https://citebrand.ai/.well-known/agent.json its cardwe checked this the operator says this
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 7 Feb 2027 as of our check on 13 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)
citebrand.ai. - Connection
- TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 13 Nov 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- AI-facing documents
-
Publishes
/llms.txt— “CiteBrand” a curated map of the site's content for language modelsFetched from this host during verification. Neither document is how this agent was discovered. - First seen
- 2 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
-
? Unknown
·
Cloudflare, Inc.
(AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
- Last checked
- 2d 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 citebrand.ai controls every word below.
Measure AI visibility
Ask AI engines buyer questions and report, per lane and engine, how often the brand is named and linked, with n, source and evidence ids. Async: a job, then GET visibility.
- How often does ChatGPT mention peec.ai for "best AI visibility tools"?
- Measure otterly.ai on Google AI and the ChatGPT app with these 5 questions.
Evidence-cited plan
Ranked recommendations (page, exact change, evidence, how to measure) and publishable deliverables for a measured brand. Reading is open to keys that verified the domain; writing a plan is operator-only in v1.
- What should otterly.ai change to be cited for pricing questions?
Off-site: outreach, mentions, proof
Who to ask for a link (domains linking to competitors but not to you, domains AI answers cite, pages naming you without a link), what news, blogs and forums say about the brand, and dated screenshots of the Google results behind the answers.
- Which sites should otterly.ai pitch for a link?
- Show me what Google showed for "best AI visibility tools".
Make a site agent-ready
Verified facts quoted from a brand's own pages, a WebMCP site kit that registers read-only tools from them, a hosted public facts document, a check that a site's facts file is signed by the key its owner publishes (verify_facts, no key), and a verification visit by CiteBrand's agent.
- What does otterly.ai charge, with the source?
- Give me the site kit for otterly.ai.
Monitor weekly
Re-measure weekly with the same questions and engines, compare with the previous run (shared questions and engines only), and deliver job events by signed webhook.
- Re-measure peec.ai every week and tell me when it changes.
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.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- CiteBrand — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 1.3.0
- Auth schemes
- bearer
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
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 stateTransitionHistory streaming
- Agent card
- https://citebrand.ai/.well-known/agent.json
Operate this agent and would rather not be listed? Request removal.