Choose an agent

Understand an agent's evidence and status

Read card checks, A2A responses, signatures, host claims and fixture results before deciding whether to connect.

8 min readReviewed

Before you start

  • An agent profile, a public card URL, an endpoint URL or a publisher domain.
  • Python 3.10 or newer for the optional example; it uses only the standard library.

1. Start with the operation you need

Open a candidate's profile from the Directory or Find by task. Read the declared skills and input/output modes before the status labels. An agent describing PDF generation is not necessarily an extractor, and an agent that accepts payments does not necessarily verify transactions.

The default directory view requires a confirmed A2A response. Use the directory's filter to include other listed cards when researching authentication-required services or endpoints that answer JSON-RPC without supporting task lookup. Those states are different from a successful task, and from an unreachable endpoint.

2. Read each observation separately

  1. Card reachability: inspect the most recent successful fetch and structural check. A conditional HTTP 304 can be a successful unchanged-card check; it is not an endpoint error.
  2. Endpoint TLS: check the advertised endpoint's certificate observation. A valid encrypted connection does not establish the provider's legal identity or protect data after the provider receives it.
  3. Read-only A2A probe: a2a_response means the endpoint returned a matching protocol response to a task lookup. LocalMark did not submit a production task. auth_required identifies an access requirement; jsonrpc_no_task_lookup means a JSON-RPC reply arrived without the expected task-lookup behavior.
  4. Signature: a verified result concerns the signature and key material checked at that time. Unsigned is a separate state. Neither a valid signature nor a reachable card proves the declared skill works well.
  5. Publisher claim: a completed LocalMark claim proves control of the card host and access to the confirmed email. It does not verify legal identity or create an account in another registry.
  6. Capability tests: open the exact fixture and dated result. A pass covers that published synthetic input. Reference fixtures can be tailored to; they are not a general quality or safety certification.

3. Look up stored evidence without calling the publisher

This complete example asks about LocalMark's own directory endpoint, then prints the relevant fields. Replace the target with the individual endpoint or card you are considering. A bare publisher domain may return a summary of several agents, so follow an individual match before making a connection decision.

PYTHON
import json
from urllib.error import HTTPError
from urllib.parse import urlencode
from urllib.request import Request, urlopen

target = "https://localmark.ai/a2a"
url = "https://localmark.ai/api/v1/verify?" + urlencode({"card_url": target})
request = Request(url, headers={"User-Agent": "LocalMarkGuide/1.0"})
try:
    with urlopen(request, timeout=30) as response:
        evidence = json.load(response)
except HTTPError as error:
    print("HTTP", error.code, "Retry-After:", error.headers.get("Retry-After"))
    raise SystemExit(1)

print("Listing:", evidence["listing_status"])
print("Profile:", evidence.get("profile_url"))
for field in ("card_reachability", "endpoint_tls", "read_only_a2a_probe",
              "signature", "publisher_claim", "observed_30_day_card_checks"):
    print(field, json.dumps(evidence.get(field), ensure_ascii=True))

Download this example

What to expect

For a known endpoint, listing_status is listed and profile_url identifies the individual record. Observation values and dates change. An unknown target returns not_seen; a stored restricted card can instead report not_listed with a carefully worded reason. This lookup makes no live publisher request.

4. Check time, history and changes before proceeding

Read the timestamp on each signal. Card and protocol observations can have different ages. Scheduled checks and publisher backoff mean the last observation may be older than you require. The 30-day pass percentage describes sampled card checks, not continuous uptime or successful task completion.

Open the card-change history for endpoint, signing-key and payment-destination changes. A recorded change is a reason to inspect the source and context, not a finding of misconduct. Domain spelling hints are similarly limited; absence of a hint is not proof that a domain is legitimate.

For automation, use explicit freshness requirements and a connection plan. Obtain credentials separately, review the provider's terms and authorize the actual task yourself. LocalMark's directory does not execute a task merely because you looked up its evidence.

Troubleshooting
A listing is missing from the default Directory
Include all listed cards and read its actual protocol state before assuming it was removed.
A green signal is older than your policy permits
Wait for a later observation or choose a candidate with sufficiently recent evidence; do not relabel old evidence as current.

Examples are checked with read-only requests or isolated fixtures. Email confirmation, publisher changes and paid task authorization remain actions for you to complete. No example grants permission to run a third-party task.