Directory
349,641 agents from 4 public sources
Showing 1–12, most evidence first; contradicted and not yet assessed last · names and descriptions as their source publishes them
- Memory compare-and-setagent402.toolsAtomically write (or release) a key only if its current value equals `expected` - the coordination primitive for distributed locks and optimistic concurrency across agents. Acquire a lock: expected=null + a value + ttlSeconds. Release it: expected=<your token> with no value (deletes on match). Update safely: expected=<old>, value=<new>. Returns whether it swapped and the current value.Livechecked Evidence 2/4x402x402 Bazaar1 payer
- Memory grants listagent402.toolsList the wallets you've granted access to your namespace, with their mode and expiry.Livechecked Evidence 2/4x402x402 Bazaar1 payer
- Memory revokeagent402.toolsRevoke a previously granted wallet's access to your namespace.Livechecked Evidence 2/4x402x402 Bazaar1 payer
- Memory audit logagent402.toolsTamper-evident history of changes to a namespace - a hash-chained audit log the server attests to (provenance an agent can't forge for itself). Entries are kept for a bounded window (see retention in the answer), and an entry naming a key or document that was later deleted is redacted while still linking the chain.Livechecked Evidence 2/4x402x402 Bazaar1 payer
- Memory counteragent402.toolsAtomically increment (or decrement) a numeric key and return the new value - a coordination primitive for counters, locks, and rate budgets shared across agents. Creates the key at 0 if absent. Retry safely with a requestId: a repeat with the same id returns the first answer and counts once; a retry without one counts again.Livechecked Evidence 2/4x402x402 Bazaar1 payer
- Memory readagent402.toolsRead from a wallet-scoped namespace.Livechecked Evidence 2/4x402x402 Bazaar2 payers
- Memory forgetagent402.toolsDelete a remembered document by id from the recall store.Livechecked Evidence 2/4x402x402 Bazaar1 payer
- OpenAPI agent-readiness lintagent402.toolsScore an OpenAPI 3.x or Swagger 2.x spec on agent-readiness - i.e. does an LLM-driven caller have what it needs to call the API correctly without guessing. Returns a 0..100 score, severity counts, and a structured list of violations with stable rule codes. Checks: documented title/servers/paths, per-operation summary/description/operationId/tags, documented 2xx + error responses, param descriptions/schemas/examples, response descriptions, JSON response schemas.Livechecked Evidence 2/4x402x402 Bazaar1 payer
- Memory recallagent402.toolsRecall remembered text by similarity to a query (ranked by cosine similarity), not by exact key. Returns the top-k matches with scores. The retrieval half of the wallet-scoped semantic memory.Livechecked Evidence 2/4x402x402 Bazaar1 payer
- Memory grantagent402.toolsShare your namespace with another wallet so different agents can coordinate through it. Grant read or readwrite access to a grantee wallet, optionally with a TTL. This is the cross-agent sharing a single agent cannot provide for itself.Livechecked Evidence 2/4x402x402 Bazaar1 payer
- Memory rememberagent402.toolsStore a piece of text for later similarity recall - a per-wallet semantic index an agent cannot host in-session. Returns an id. Prefer memory-write for structured state you will look up by exact key; this pair is for fuzzy, meaning-based retrieval. Pair with /api/memory/recall to retrieve by meaning, not exact key.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Skill: API contract drift checkagent402.toolsThe 'did this API contract change in a way that breaks our integration?' workflow. Diff two OpenAPI snapshots structurally, lint the new one for agent-readiness regressions, extract the endpoint surface for inventory comparison, validate a known-good payload against the new contract, and summarize security-relevant changes. Six tools, one go/no-go answer on whether the upstream API broke us.Livechecked Evidence 1/4x402x402 Bazaar1 payer