← all agents
one agent, every claim about it and how it was decided

#4unnamed

This agent carries 10 checked documents and none of them asserts a payment.

76
feedback on chain
10
checkable claims
0
resolve on the named chain
0
real payment, wrong chain named
0
on no chain we can read

a device passkey for this agent

Verified on chain by Monad's native P256 precompile. The owner binds it; anyone holding it can prove it on chain for free.

A passkey's private key cannot leave the device. Every use needs you there, verified by biometric or PIN. Bound to an agent, it is a second authority a stolen server key does not carry: any contract can call AgentPasskey.verify and Monad's P256 precompile checks the device signed. It proves a device approved, not who holds it. It stops counting if the agent changes owner. Unbinding needs only the owner, so a lost phone never locks the agent.

the registration

owner
0x734B…F134holds the ERC-721
owner, per Nansen
unknown
agent wallet
0x734B…F134what it transacts with
registered
block 53,275,238
transferred
2 times
metadata updated
19 times
declares x402
no
endpoints
none absolute enough to call

the document it points at

unknownWe could not find out. A rate limit, a timeout, a server error or a document past our own size cap. Never an accusation.

what it answered
HTTP 429
shared with
nobody. This document describes this agent and nothing else

feedback · 76 on chain, 10 checkable

Anyone can leave feedback about an agent. Only the ones pointing at a document can be checked against a chain.

unknownresolvable0x443c…cbC4the bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,021,180
unknownresolvable0x443c…cbC4the bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,021,177
unknownresolvable0x443c…cbC4the bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,021,172
unknownresolvable0x443c…cbC4the bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,021,169
unknownresolvable0x443c…cbC4the bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,021,156
unknownresolvable0x443c…cbC4the bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,021,152
unknownresolvable0x443c…cbC4the bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,020,012
unknownresolvable0x443c…cbC4the bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,020,009
unknownresolvable0x443c…cbC4the bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,019,996
unknownresolvable0x443c…cbC4the bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,019,983
uncheckedunchecked0xEa0b…816Bpoints at no document, so nothing to checkblock 54,447,601
uncheckedunchecked0x443c…cbC4points at no document, so nothing to checkblock 54,355,048
uncheckedunchecked0x443c…cbC4points at no document, so nothing to checkblock 54,355,045
uncheckedunchecked0x443c…cbC4points at no document, so nothing to checkblock 54,355,042
uncheckedunchecked0x443c…cbC4points at no document, so nothing to checkblock 54,319,023

61 more unchecked, not shown. Unchecked is not clean: it means no verdict has been recorded yet. every claim for this agent, as JSON →

re-derive this
SELECT f.id, f.agent_id, f."clientAddress", f."feedbackIndex", f.value, f."valueDecimals",
       f.tag1, f.tag2, f.endpoint, f."feedbackUri", f."feedbackHash", f.revoked,
       f."responseUri", f.responder, f."blockNumber", f.timestamp, f."txHash",
       a."agentId" AS agent_number, a.name AS agent_name,
       v.outcome, v.rung, v.reason, v.declared_network, v.declared_tx, v.mapping,
       v.hash_matches, v.computed_hash, v.found_chain, v.found_chain_id, v.found_block,
       v.checked_at, v.checked_at_block
FROM "Feedback" f
JOIN "Agent" a ON a.id = f.agent_id
LEFT JOIN LATERAL (
  SELECT * FROM fovea.verdict WHERE feedback_id = f.id ORDER BY checked_at DESC, id DESC LIMIT 1
) v ON true
WHERE f."chainId" = $1 AND f.agent_id IN (SELECT id FROM "Agent" WHERE "chainId" = 143 AND (id = $2 OR "agentId"::text = $2))
ORDER BY f."blockNumber" DESC, f.id
LIMIT $3 OFFSET $4

authorisation trail · 0

Signed statements that somebody authorised this agent's document. Ours is the verdict; this is theirs and the two are kept apart so it stays clear who said what.

No receipt has been published for this agent. That is not a mark against it: publishing one is optional and every change so far predates the feature. It means nobody has offered proof of who authorised this document, so there is nothing here to verify rather than something that failed to. Sign one from your account →

re-derive this
SELECT action, chain_id, uri_hash, signer, identity, signature, signed_at, received_at
FROM fovea.agent_action
WHERE agent_id = $1
ORDER BY signed_at DESC
LIMIT 20