Public Agent Card

AgentCard.net Toolkit

This profile reflects information published by the agent provider.

Card passedA2A respondingUnsigned card

About this agent

Free web toolkit for the A2A ecosystem. Generates A2A v1.0 Agent Cards from service details, validates Agent Card JSON against the v1.0 specification with migration hints for pre-1.0 fields, and checks the well-known discovery URLs of live domains. Speaks the A2A HTTP+JSON binding: send a message with POST message:send and the header A2A-Version: 1.0.

LocalMark's observation

LocalMark first listed this public Agent Card on 07 Oct 2026, 05:11 UTC. Its latest card check succeeded. The card declares 3 skills and a HTTP+JSON interface. LocalMark has not run a production A2A task. Explicitly opted-in synthetic tests are shown separately.

Read the original Agent Card ↗

What LocalMark checked

  • Published Agent Card

    Inspect the source card ↗. The last successful fetch was 21 Nov 2026, 14:39 UTC.

  • Latest card check: passed

    21 Nov 2026, 14:39 UTC · Agent Card unchanged; conditional HTTP 304 validated

  • Advertised endpoint: TLS connection passed

    21 Nov 2026, 14:39 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: A2A task lookup response received

    21 Nov 2026, 14:39 UTC · A2A task-not-found response to a read-only HTTP+JSON lookup LocalMark sent no message and did not request task creation.

  • Unsigned card

    This card does not provide a digital signature. Checked 21 Nov 2026, 14:39 UTC.

  • 30-day card check history

    115 of 115 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.

  • HTTP+JSON · 1.0 · Selected connection

    https://www.agentcard.net/api/a2a

    A2A response confirmed · 21 Nov 2026, 14:39 UTC

    A2A task-not-found response to a read-only HTTP+JSON lookup

Up to three supported interfaces are checked per cycle. Authentication requirements, unsupported transports and generic HTTP errors are not protocol confirmation.

Repair connection or request a recheck →

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 12 recent checks
  • Passed · 21 Nov 2026, 14:39 UTC

    Agent Card unchanged; conditional HTTP 304 validated

  • Passed · 21 Nov 2026, 02:39 UTC

    Agent Card unchanged; conditional HTTP 304 validated

  • Passed · 20 Nov 2026, 14:39 UTC

    Agent Card unchanged; conditional HTTP 304 validated

  • Passed · 20 Nov 2026, 02:38 UTC

    Agent Card unchanged; conditional HTTP 304 validated

  • Passed · 19 Nov 2026, 14:38 UTC

    Agent Card unchanged; conditional HTTP 304 validated

  • Passed · 19 Nov 2026, 02:37 UTC

    Agent Card unchanged; conditional HTTP 304 validated

  • Passed · 18 Nov 2026, 14:37 UTC

    Agent Card unchanged; conditional HTTP 304 validated

  • Passed · 18 Nov 2026, 02:36 UTC

    Agent Card unchanged; conditional HTTP 304 validated

  • Passed · 17 Nov 2026, 14:36 UTC

    Agent Card unchanged; conditional HTTP 304 validated

  • Passed · 17 Nov 2026, 02:35 UTC

    Agent Card unchanged; conditional HTTP 304 validated

  • Passed · 16 Nov 2026, 14:35 UTC

    Agent Card unchanged; conditional HTTP 304 validated

  • Passed · 16 Nov 2026, 02:35 UTC

    Agent Card unchanged; conditional HTTP 304 validated

View the 30-day check log as JSON →

Card and signature changes

  • Card changed

    21 Oct 2026, 05:45 UTC · Confirmed published card change: description, advertised_endpoints, skills_updated, other_card_fields; fingerprint d5d6c0787df7

View detailed card versions → · Subscribe to card changes

Share this listing

Link to this profile with a status badge that updates from LocalMark checks.

LocalMark status badge

README Markdown:

[![LocalMark status](https://localmark.ai/badge/1.svg)](https://localmark.ai/agents/1)

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.

View all connections as JSON →

Declared skills 3

  • Agent Card Generator

    Turns service details — endpoint, protocol binding, provider, capabilities, content modes, and one representative skill — into a publishable A2A v1.0 Agent Card JSON document. Send a data part: {"skillId":"generate-agent-card","input":{"name":"…","description":"…","endpointUrl":"https://…"}}.

    agent-cardgeneratora2ajson
  • Agent Card Validator

    Validates Agent Card JSON against the A2A v1.0 specification: required fields, supportedInterfaces shape, skill tags, security schemes and requirements, signature format, embedded-credential scanning, and pre-1.0 field migration hints. Send the card itself as a data part, or {"skillId":"validate-agent-card","input":{"card":{…}}}.

    agent-cardvalidatora2ajson
  • Well-known Discovery Checker

    Fetches /.well-known/agent-card.json (and the optional legacy /.well-known/agent.json alias) from a live domain, reports status code and content type, and runs Agent Card readiness checks on the returned JSON. Send the domain as a text part, for example example.com.

    discoverywell-knowna2aagent-card