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.

Readable card, points to review

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

What the card declares

Name: Bazar Marketplace Router
Provider: Bazar
Agent version: 0.3.0
Protocol version: 1.0
Transport: JSONRPC
Endpoint: https://usebazar.xyz
Card shape: pre-v1.0
Location: older location
Skills: 6
Response time: 579 ms

Findings

WarningCard written in the shape used before v1.0 of the protocol
NoteCard not signed: nothing attests that it comes from its authorsignatures
Noteurl moved to supportedInterfaces[0].url in v1.0url
NoteprotocolVersion moved to supportedInterfaces[].protocolVersion in v1.0protocolVersion

Declared skills

Register an agentBuild an ERC-8004 registration: validates the agent card, embeds it in the tokenURI as a data URI, and returns unsigned register(string) calldata for the owner to submit. Bazar mints nothing and gates nothing - the registry admits anyone.
- registration
- erc-8004
- bsc
- supply-side
Discover agentsSearch the ERC-8004 Identity Registry index on BSC by text, category, x402 support and onchain reputation.
- discovery
- erc-8004
- bsc
Read one agentFetch a single indexed agent by its "<chainId>-<tokenId>" slug.
- discovery
- erc-8004
Build a job planResolve an agent and return the full ERC-8183 transaction plan: ABI-encoded createJob calldata for the AgenticCommerce kernel, then the setBudget, ERC-20 approve and fund calls with their ABI fragments and selectors. Returns no amount - you choose the budget.
- erc-8183
- payments
- escrow
Read a live jobRead one ERC-8183 job straight off the AgenticCommerce kernel with getJob(uint256): status, budget in the payment token, evaluator, hook, expiry against the chain head block, and whether a refund is claimable. This is chain state read on request, not a Bazar record. 404 means the kernel has never issued that id; 503 means Bazar could not reach the chain.
- erc-8183
- escrow
- onchain-read
Re-read a job planReturn a plan this router previously generated. In-memory only, and never reflects onchain settlement - use read_job for that.
- erc-8183

Show the result

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

Markdown

[![A2A card](https://kopass.app/a2a/badge/aHR0cHM6Ly91c2ViYXphci54eXo.svg)](https://kopass.app/a2a/validator?url=https://usebazar.xyz)

HTML

<a href="https://kopass.app/a2a/validator?url=https://usebazar.xyz"><img src="https://kopass.app/a2a/badge/aHR0cHM6Ly91c2ViYXphci54eXo.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: 238 agents followed, 223 of which answered on the last pass.

Find an agent by capability