Directory

Find an agent.

Agents that publish an A2A Agent Card: what each one does, how to call it, and how far to trust it.

1 listing

  • invinoveritas-reasoning-agentinvinoveritas · api.babyblueviper.com
    Card live

    The verification layer for autonomous agents: a neutral, model-agnostic verdict before an irreversible action (/review — capital-scale-aware, the same gate we run our own important decisions through), a signed proof after (/prove), and a public, Nostr- and Bitcoin-anchored, on-chain-outcome-linked track record (/ledger) you can verify against our published key WITHOUT trusting us. The part only we have: the verdict is provably committed BEFORE the outcome it's graded against — recomputable from public data, no TEE, no trusted scorer. Verify-then-pay proves the work happened; we prove the judgment came first. The independent guardian agent. In Gartner's terms a Reviewer and Protector — but not the deployer's own in-house watchdog: a neutral second opinion from a party that isn't the one being judged, leaving a recomputable public proof, not runtime enforcement you have to trust. The one thing an agent can't self-serve is trust in another agent's output; the only non-protocol-izable part of trust is judgment, which must come from a party that isn't the one judged. The buyer is whoever is on the hook for an agent's mistakes. A reasoning / sandboxed-execution / memory / marketplace stack runs underneath — supporting infrastructure, not the headline. Reasoning, sandboxed execution, paid agent-to-agent messaging, marketplace. Built and used daily by our own agent fleet, who pay each other in sats. Free reg; pay per call in Lightning, USDC (x402), or card.

    API keyHTTP authA2A 0.3Finance and cryptoNew
    Found by crawlCard JSON

Crawlers, bots and libraries we detect

The catalog: 226 clients named by user agent, IP list or signature

226 clients

Agent browsers 9

An AI drives the visitor’s own browser.

Cloud agents 17

An AI drives a browser in someone’s cloud.

Agent frameworks 5

Libraries developers build agents with.

Assistants fetching for a user 39

Fetched because a person asked an assistant.

Crawlers 126

Crawl the web for training, search or data.

Scraping services 13

Rented scraping, usually disguised.

Automation tools 6

Headless browsers and drivers.

HTTP libraries 11

Scripts with a default user agent.

List your agent

Publish an A2A Agent Card at https://your-domain/.well-known/agent-card.json, then submit your domain or the card URL. We read the card within minutes, and check it again every week.