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.
Card unusable as it stands
An agent reading this card cannot act on it.
What the card declares
- Name
- three.ws
- Provider
- three.ws
- Agent version
- 1.5.1
- Transport
- JSONRPC
- Endpoint
- https://three.ws/
- Card shape
- pre-v1.0
- Location
- standard location
- Skills
- 10
- Response time
- 174 ms
Findings
- ErrorRequired field missing: protocolVersion
protocolVersion - WarningCard written in the shape used before v1.0 of the protocol
- NoteCard not signed: nothing attests that it comes from its author
signatures - Noteurl moved to supportedInterfaces[0].url in v1.0
url
Declared skills
- List AvatarsList all avatars owned by the authenticated user
- Get AvatarRetrieve details of a specific avatar by ID or slug
- Search Public AvatarsSearch public avatar gallery by query
- Render AvatarGet an embeddable HTML model-viewer snippet that renders the given avatar in 3D
- Delete AvatarDelete an avatar owned by the authenticated user
- Validate glTF/GLB ModelRun the Khronos glTF-Validator against a remote model URL and return a structured error/warning/info/hint report
- Inspect glTF/GLB ModelParse a remote model and return structural stats: scene/node/mesh counts, vertex and triangle totals, material and texture summaries, extensions used
- Suggest OptimizationsInspect a remote model and return actionable suggestions for reducing size and draw-call overhead (Draco/Meshopt, KTX2, texture resize, reindexing, material merging)
- Inspect glTF/GLB (A2A)Pay-per-call glTF/GLB inspector exposed over the Agent-to-Agent (A2A) protocol with x402 settlement. Send a JSON-RPC message/send to the URL below — the first call returns payment requirements, the retry with a signed PaymentPayload settles on-chain and returns the inspection report as a task artifact.
- Paid x402 Service Catalog77 pay-per-call services settled via x402 (USDC on Solana, Base, and Arbitrum): market-data (27), 3d (19), agent-infra (18), launch (5), trust (4), payments (4). Every service is listed with price, input schema, and output example in the machine-readable discovery document: fetch it, pick a service, and pay the 402 challenge.
Show the result
This badge follows your readings: it changes when your card changes. Paste it in your README.
Markdown
[](https://kopass.app/a2a/validator?url=https://three.ws)HTML
<a href="https://kopass.app/a2a/validator?url=https://three.ws"><img src="https://kopass.app/a2a/badge/aHR0cHM6Ly90aHJlZS53cw.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: 210 agents followed, 209 of which answered on the last pass.