TR
Security · x402 · early usage

Which live agents can do X — and which of them are safe

Which live agents can do X — and which of them are safe? Searches the skills, domains and names ERC-8004 agents declare, across the registrations this service sweeps continuously, and returns only the ones answering. Each row carries the endpoint to call, the…

by trust-agent.io · discovered, not yet claimed by its owner · updated 2026-10-01

30d calls2
30d payers2
MethodGET
Outputjson

Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.

What it does

Which live agents can do X — and which of them are safe? Searches the skills, domains and names ERC-8004 agents declare, across the registrations this service sweeps continuously, and returns only the ones answering. Each row carries the endpoint to call, the wallet a payment reaches, and that wallet's risk band and sanctions verdict — one call instead of a screening per row. Free alternative: GET /v1/search. Trial: 3 free calls/wallet/24h — https://trust-agent.io/v1/trial.

Tags: erc-8004 · agents · search · x402 · bazaar

Call contract

Method
GET
Input
query parameters
Output
json
Last paid call
2026-10-01
Input example from Bazaar metadata
{
  "acceptsX402": "true",
  "skill": "natural-language-processing-info"
}
Output example
{
  "agents": "agentId, identifier, name, endpoint, skills, domains, acceptsX402, payoutWallet, verdict (riskBand, blocklisted, confidence per payout wallet), checkedAt",
  "matches": "total agents matching, across all pages",
  "nextCursor": "offset for the next page, or null when exhausted",
  "note": "A declared skill is a claim, not a capability — each row already carries the verdict, so start with the rows that read safe and escalate the rest to GET /v1/verify/quick for the score and flags"
}

Use with an agent

  1. Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
  2. Inspect. Fetch /resources/27659.json for the price and payment options.
  3. Pay. Call GET https://trust-agent.io/v1/search/agents. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
  4. Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price
$0.005001 / request
Protocol
x402 v2
Auth
No account or API key. Pay per request.
Networks
Base
Demand
2 calls · 2 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

SchemeNetworkAssetAmountPay toTimeout
exactBase
eip155:8453
USDC$0.0050010x6121654D3Fd4C8B42a90d30472E4D40927C3e6BB60s
accepts[] (raw JSON)
[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x6121654D3Fd4C8B42a90d30472E4D40927C3e6BB",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "5001",
    "amountUsd": 0.005001,
    "maxTimeoutSeconds": 60
  }
]

Schemas

Output schema (JSON Schema)
{
  "properties": {
    "example": {
      "properties": {
        "agents": {
          "description": "agentId, identifier, name, endpoint, skills, domains, acceptsX402, payoutWallet, verdict (riskBand, blocklisted, confidence per payout wallet), checkedAt"
        },
        "matches": {
          "description": "total agents matching, across all pages"
        },
        "nextCursor": {
          "description": "offset for the next page, or null when exhausted"
        },
        "note": {
          "description": "A declared skill is a claim, not a capability — each row already carries the verdict, so start with the rows that read safe and escalate the rest to GET /v1/verify/quick for the score and flags"
        }
      },
      "type": "object"
    },
    "type": {
      "type": "string"
    }
  },
  "required": [
    "type"
  ],
  "type": "object"
}
Example shape — generated from the schema, not a captured live response
{
  "example": {
    "agents": null,
    "matches": null,
    "nextCursor": null,
    "note": null
  },
  "type": "string"
}

Examples

curl
curl "https://trust-agent.io/v1/search/agents"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid
JavaScript
const res = await fetch("https://trust-agent.io/v1/search/agents");
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}
Python
import httpx
res = httpx.get("https://trust-agent.io/v1/search/agents")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider
trust-agent.io
Endpoint
https://trust-agent.io/v1/search/agents
Machine-readable
/resources/27659.json