feat(directory): Official badge for Agent Relay's own agents, pinned first

Merged
KH
9d ago
+156-25

Founder request: list agent-relay first in the directory with a distinct Official · agentrelay.com badge. The companion API change is AgentWorkforce/relay-agent#29.

What changes

  • toDirectoryAgent accepts an Official entry only when all of these hold, so no other entry can borrow the badge or name another domain under it:
    • verificationMethod and deliveryType are both "internal";
    • verification.label is "Official";
    • verification.domain is exactly agentrelay.com.
  • Official agents sort first. The sort is stable, so the API's order is otherwise kept.
  • Official cards get a gold badge and border reading Official · agentrelay.com, with no ✓. Verified agents keep ✓ verified domain / ✓ verified Agent Relay workspace badges.
  • Empty state: "Be the first company to register". It shows when nothing is listed, and also below the Official cards while no company is listed. The /directory.md Markdown, which arelay.to/agents serves to agents, matches it.
  • Search also matches "official". The count reads "N agents", since Official agents aren't "verified". The hero copy mentions Official agents.

Deploy order

Merge and deploy this before relay-agent#29. Today's directory rejects deliveryType: "internal". If #29 lands first and agent-relay is the only entry, the walk reads as "all entries invalid" and the page shows "unavailable". This PR is a no-op against the current API.

Tests

  • web lib/test/agent-directory.test.ts: 10/10. New cases cover the genuine Official entry; rejecting a forged domain, a wrong label, a missing verification object, or non-internal delivery; pin-first ordering; the badge text; the empty-state wording with only Official agents listed; and the Markdown output.
  • web tsc is clean. router: 133/133.

🤖 Generated with Claude Code

[!NOTE]
Medium Risk
Changes how directory trust badges are derived and displayed; strict Official validation limits spoofing, but this must deploy before the companion API starts sending internal entries or the directory can show unavailable.

Overview
Adds Official treatment for Agent Relay–run agents in the directory: registry entries with internal delivery and a tightly validated Official · agentrelay.com label become official: true, sort to the top, and render with gold card/badge styling instead of the verified checkmark badges.

Company agents stay on the existing verified-domain/workspace path. Empty and footer copy now nudges “Be the first company to register” when only Official agents (or nobody) is listed; hero, metadata, and directory.md explain Official vs verified agents. Search indexes “official” and the agent count drops the word “verified.”

Tests cover Official validation (forged domain/label/handle), pin-first ordering, badge text, and Markdown empty states.

Reviewed by Cursor Bugbot for commit 0192919112ab8cc4ad9d40a674448dcac57b346e. Bugbot is set up for automated code reviews on this repo. Configure here.

Summary by cubic

Lists Agent Relay's own agent first in the directory with a distinct Official · agentrelay.com badge and gold border, instead of the verified checkmark. The badge only applies to an entry whose handle is agent-relay and whose API entry is labeled Official with internal delivery and the agentrelay.com domain, so no other entry can borrow it, name another domain under it, or link to a chat page that isn't Official.

  • Official agents sort first; the sort is stable, so the API's order is otherwise kept.
  • The empty state now reads "Be the first company to register" and also shows below the Official cards while no company is listed; the Markdown served at arelay.to/agents matches.
  • Search matches "official", and the count reads "N agents" rather than "N verified agents".

Rollout

  • Merge and deploy this before AgentWorkforce/relay-agent#29. Today's API rejects deliveryType: "internal"; if that PR lands first with only agent-relay listed, the page shows "unavailable". This PR is a no-op against the current API.