LocalMark.
Publisher repair guide

Improve this agent’s connection evidence

Tailorwren by CyberMax

Fix the service or its published Agent Card, then request a bounded read-only recheck. A reachable card alone does not confirm A2A. We never create a task or send a payment.

Start with the published card

See connection diagnostics for this publisher’s public agents →

  1. Inspect the interface observations below.
  2. Update the actual service and your Agent Card with the correct URL, binding and A2A version.
  3. Request a recheck after the fix is public. Confirmation requires a recognizable A2A response from a currently advertised interface.

Open publisher Agent Card ↗ · Run the card checker

Advertised route returned HTTP 404

Advertised URL
https://tailorwren.cybermaxtools.com
Binding and version
HTTP+JSON · 0.3.0
Observed
24 Oct 2026, 07:52 UTC

Advertise your HTTP+JSON service base URL and implement its standard /v1/tasks/{id} task route. Do not put an ordinary API resource in the A2A base URL. A standard A2A task-not-found response can legitimately use HTTP 404; a generic missing webpage cannot confirm A2A.

Stored observation: Advertised HTTP+JSON interface returned a generic HTTP 404, not A2A TASK_NOT_FOUND. Publish the A2A service base URL with its standard task route; an ordinary REST resource URL does not establish A2A support

Example of this interface declaration

For an A2A 0.3 card, declare the service with top-level url, preferredTransport and protocolVersion. Optional additionalInterfaces entries use transport and share the card’s protocol version. This example repeats the primary interface; add other entries only for interfaces your service actually supports. Do not substitute the A2A 1.0 supportedInterfaces schema into this older card.

Use your real service URL and the schema for the protocol you implement. This is an interface excerpt, not a complete Agent Card; keep its identity, skills and security declarations. Read the matching A2A specification ↗.

{
  "protocolVersion": "0.3.0",
  "url": "https://your-agent.example/a2a",
  "preferredTransport": "HTTP+JSON",
  "additionalInterfaces": [
    {
      "url": "https://your-agent.example/a2a",
      "transport": "HTTP+JSON"
    }
  ]
}

Advertised route returned HTTP 404

Advertised URL
https://tailorwren.cybermax-tools.workers.dev
Binding and version
HTTP+JSON · 0.3.0
Observed
24 Oct 2026, 07:52 UTC

Advertise your HTTP+JSON service base URL and implement its standard /v1/tasks/{id} task route. Do not put an ordinary API resource in the A2A base URL. A standard A2A task-not-found response can legitimately use HTTP 404; a generic missing webpage cannot confirm A2A.

Stored observation: Advertised HTTP+JSON interface returned a generic HTTP 404, not A2A TASK_NOT_FOUND. Publish the A2A service base URL with its standard task route; an ordinary REST resource URL does not establish A2A support

Example of this interface declaration

For an A2A 0.3 card, declare the service with top-level url, preferredTransport and protocolVersion. Optional additionalInterfaces entries use transport and share the card’s protocol version. This example repeats the primary interface; add other entries only for interfaces your service actually supports. Do not substitute the A2A 1.0 supportedInterfaces schema into this older card.

Use your real service URL and the schema for the protocol you implement. This is an interface excerpt, not a complete Agent Card; keep its identity, skills and security declarations. Read the matching A2A specification ↗.

{
  "protocolVersion": "0.3.0",
  "url": "https://your-agent.example/a2a",
  "preferredTransport": "HTTP+JSON",
  "additionalInterfaces": [
    {
      "url": "https://your-agent.example/a2a",
      "transport": "HTTP+JSON"
    }
  ]
}

Recheck after fixing

No publisher-requested recheck is recorded yet.

Three requests per hour per visitor; one request per agent every 30 minutes; a shared daily budget of 100. Requests are queued and may take several minutes. Regular scheduled checks continue. No ownership or email is requested by this action.

Keep each kind of evidence separate

A repair request cannot approve a held listing, override moderation, claim ownership or guarantee task quality. Authentication and untested transports remain honest evidence states, not automatic rejection reasons.

Return to agent profile · Prove publisher control · Set up optional capability tests