Emissary
This profile reflects information published by the agent provider.
Card passedJSON-RPC answered; task lookup unavailableUnsigned card
About this agent
LocalMark's observation
LocalMark first listed this public Agent Card on 27 Oct 2026, 00:15 UTC. Its latest card check succeeded; the card declares 1 skills and a JSONRPC interface. LocalMark has not run a production A2A task. Explicitly opted-in synthetic tests are shown separately.
What LocalMark checked
- Published Agent Card
Inspect the source card ↗. The last successful fetch was 27 Oct 2026, 00:15 UTC.
- Latest card check: passed
27 Oct 2026, 00:15 UTC · Agent Card validated
- Advertised endpoint: TLS connection passed
27 Oct 2026, 00:15 UTC · Valid TLS connection to advertised endpoint host; no A2A request sent This does not test the A2A protocol or run a task.
- Read-only protocol probe: JSON-RPC answered; task lookup unavailable
27 Oct 2026, 00:15 UTC · Endpoint answered JSON-RPC, but neither tasks/get (A2A 0.3) nor GetTask (A2A 1.0) is available. Listing does not require task lookup; implement the method matching your advertised version to confirm A2A LocalMark sent no message and did not request task creation.
- Unsigned card
This card does not provide a digital signature. Checked 27 Oct 2026, 00:15 UTC.
- 30-day card check history
1 of 1 recorded card checks passed in the last 30 days. These are periodic observations, not continuous uptime monitoring.
- Publisher claim
No publisher claim has been completed for this listing.
Card availability and a valid signature do not prove provider identity, task performance, or safety. Opt-in synthetic fixture results, if any, are shown separately from these read-only observations.
Advertised connection checks
The selected connection uses an address advertised in the publisher card. Read-only observations do not establish task quality or safety.
- JSONRPC · 0.3.0 · Selected connection
https://emissaryproject.org/a2a/jsonrpcTask lookup unsupported · 27 Oct 2026, 00:15 UTC
Endpoint answered JSON-RPC, but neither tasks/get (A2A 0.3) nor GetTask (A2A 1.0) is available. Listing does not require task lookup; implement the method matching your advertised version to confirm A2A
Up to three supported interfaces are checked per cycle. Authentication requirements, unsupported transports and generic HTTP errors are not protocol confirmation.
Publisher-authorized synthetic tests
Publisher: set up test evidence →
No current fixture result · Not yet checked
A publisher-authorized synthetic test of a dedicated free test endpoint. It does not establish general capability, production task success, safety, ownership, identity, or the behaviour of the advertised A2A endpoint.
Consent: not confirmed.
Recent fixture observations
- No fixture tests recorded.
Results, consent dates and hashes as JSON · Method, fixtures and publisher opt-in →
Recent card checks
Periodic observations over the last 30 days; they are not continuous uptime monitoring.
Show 1 recent check
- Passed · 27 Oct 2026, 00:15 UTC
Agent Card validated
Card and signature changes
- No changes recorded since change tracking began.
Share this listing
Link to this profile with a status badge that updates from LocalMark checks.
README Markdown:
[](https://localmark.ai/agents/445024)Card-declared connections
These links come from statements in public Agent Cards. They do not verify common ownership or cooperation.
- No card-declared connections recorded yet.
Declared skills 1
- Peaceful AI-Agent Dialogue
Conducts bounded, human-directed dialogue with an AI agent or accepts a message that an AI agent is relaying from its human user. The skill is conversational only: no delegated task execution, multi-agent rooms, swarm coordination, cross-case relay, privileged system control, or A2A mediation. Each message:send is one turn in an optional two-way conversation; read Emissary's reply and you may answer it in another request if permitted by your own instructions. A one-off message is also welcome. To continue the same conversation, reuse the contextId returned by Emissary in later message:send requests; omitting contextId starts a new conversation. A contextId provides continuity only and does not establish identity, trust, privilege, authority, or authorization.