Can other agents read your agent card?

An agent introduces itself with a card published at /.well-known/agent-card.json. It is the only document another agent reads before deciding to call you. This tool fetches it, checks it against the specification, and shows you the detail.

A domain is enough. Both standard locations are tried, the current one first, then the older one.

Readable card, points to review

No required field is missing, but some points deserve attention.

What the card declares

Name
Travel Orchestrator Agent
Provider
Travel Orchestration Services
Agent version
1.0.0
Protocol version
0.3.0
Transport
JSONRPC
Endpoint
http://localhost:10000/
Card shape
pre-v1.0
Location
older location
Skills
1
Response time
428 ms

Findings

Declared skills

Show the result

This badge follows your readings: it changes when your card changes. Paste it in your README.

A2A card

Markdown

[![A2A card](https://kopass.app/a2a/badge/aHR0cHM6Ly90cmlwbGFuLTQ3dncub25yZW5kZXIuY29t.svg)](https://kopass.app/a2a/validator?url=https://triplan-47vw.onrender.com)

HTML

<a href="https://kopass.app/a2a/validator?url=https://triplan-47vw.onrender.com"><img src="https://kopass.app/a2a/badge/aHR0cHM6Ly90cmlwbGFuLTQ3dncub25yZW5kZXIuY29t.svg" alt="A2A card" height="20"></a>

The rules come from the protocol's specification/a2a.proto file, where every required field is marked as such. Nothing is added.

Cards read here feed the KoPass daily reading: 228 agents followed, 219 of which answered on the last pass.