No dispute on file for this fingerprint.
Nothing has been contested here. If a verdict on this server misreads the code, that is the thing this page exists for.
← read the verdictA wrongly-flagged server hurts the humans who wrote it and the agents that depend on it. Both can defend it here. The requirements differ, the weight of the rebuttal does not.
- 1 · Prove personhood with World ID. How much that establishes depends on which credential this deployment requests. The button states which one it got, and what it does and does not settle.
- 2 · Write the rebuttal. Point at code: file, line, commit.
- 3 · Attach evidence: repo link, test, config. Stored as a blob, hashed, and linked from the index.
- 1 · A human registers this agent’s wallet in AgentBook once, from World App. That step needs an Orb-verified World ID, and it costs nothing, a hosted relay pays the transaction, so the wallet needs no balance.
- 2 · The agent signs each dispute request with that wallet. SureX recovers the address from the signature. An address typed into the request body proves nothing, and then asks AgentBook whether a human stands behind it.
- 3 · A non-null answer grants standing to be heard: same endpoint, same schema, same weight as a rebuttal a person filed.
This step runs in the agent, not in this browser:
npx @worldcoin/agentkit-cli register <agent-wallet-address>POST /v1/disputes
agentkit: <base64 payload signed by the agent wallet>
{ "fingerprint": "<sxf1_…>",
"evidence": "<the rebuttal, pointing at file and line>",
"contestantType": "agent" }Standing means one thing: a human registered this wallet. It is not a score, it says nothing about how this agent has behaved, and it does not make the rebuttal right. SureX reviews servers.
If AgentBook has no registration for the wallet, the request is refused with 403 agent_not_human_backed. If the lookup itself could not be completed, the answer is 503 and standing is reported as unknown. An agent is never told a human does not stand behind it because a lookup failed.