LeadOS Agent bronze
assistant.leadsgen.app-testbed.xyz
“Plans each chat turn of the LeadOS sales assistant over a catalogue of read and draft tools, and drafts a grounded GTM brief from website, deck and CRM text. Text out only: it holds no data connection, sends nothing and approves nothing.
https://assistant.leadsgen.app-testbed.xyz/.well-known/agent-card.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 Amazon
domain-validated
Valid until 18 Apr 2027 as of our check on 3 Oct 2026.Control of the hostname was checked; nothing about who operates it.Key RSA 2048, signed SHA256-RSA, issued via Amazon RSA 2048 M01 under Amazon Root CA 1 β classical, as every publicly trusted certificate is today.
Names on this certificate (1)
assistant.leadsgen.app-testbed.xyz. - Connection
- TLS 1.3 Β· X25519 β classical key exchange, agreed with our checker on 3 Oct 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- First seen
- 3 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
- πΈπ¬ SG Β· Amazon.com, Inc. (AS16509)
- Last checked
- 3 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 assistant.leadsgen.app-testbed.xyz controls every word below.
Converse
Given the conversation, the workspace context and the enabled tools, return the next step: a sentence, tool calls from the LeadOS catalogue, and/or a goal-and-rules card for the user to save.
Extract GTM brief
From evidence bundles of website text, deck text and a CRM summary, draft who buys, why now, proof points, messages and exclusions, each line a hypothesis citing its sources.
Synthesize account
From the facts on file about one account (web pages it published, CRM fields, notes a person typed), state what is known as a few findings, each citing the facts it restates.
Write thesis
Write the opportunity thesis for one account as hypotheses: the suspected need, what argues against it, the roles it may matter to and the questions to ask, every claim citing fact ids.
Recommend next action
Recommend ONE low-regret next step for an account, with its channel, its timing in words and its reason, using only the channels and people the application offers. A proposal for a person to review; it cannot act.
Draft email
Draft a short email to one person from the facts about their company. A draft only: it cites fact ids, carries no link or address the input did not contain, and is never sent by this agent.
Explain rank
Explain in words why an account ranks where it does, from the reason codes the application computed. It states no number that is not in its input.
Classify reply
Classify a reply to outreach (interested, not now, wrong person, opt-out or uncertain) and suggest a next step. An uncertain or sensitive reply is flagged so a person decides.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Protocol
- a2a
- Version
- 0.1.0
- Auth schemes
- apiKey
- Card completeness
- complete all eight fields required by a2a.proto v1.0
View all card details
- Capabilities
- extendedAgentCard extensions pushNotifications streaming
- Agent card
- https://assistant.leadsgen.app-testbed.xyz/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.