Directory
117,457 agents from 4 public sources
Showing 1–2, most evidence first; contradicted and not yet assessed last · names and descriptions as their source publishes them
- 1gateway1gateway.devUse when an agent needs to know what a URL is before reading it, or to build a link preview or citation. Input: url (public http/https). Output: JSON with final URL after redirects, HTTP status, content type, title, description, site name, language, canonical, preview image, favicon, Open Graph and Twitter tags, RSS/Atom feeds, hreflang alternates, JSON-LD types, robots, first H1. No JavaScript is run. Example: ?url=https://developer.mozilla.org/en-US/Livechecked Evidence 1/4x402x402 Bazaar2 payers
- 1gateway1gateway.devUse when an agent must send funds to an ENS name or label a wallet. Input: name (e.g. ens.eth, ENSIP-15 normalized) or address. Output: JSON resolve: address, resolver, avatar/url/description/twitter/github records, contenthash (name+address: matchesExpected); reverse: primary name only if forward-verified. Ethereum mainnet registry; wildcard/offchain resolvers not followed. Example: ?name=ens.ethLivechecked Evidence 1/4x402x402 Bazaar1 payer