# 47620 x402 Seller — Trust Index Host Lookup

> 47620 x402 Seller — Trust Index Host Lookup is a paid API for AI agents from 47620.xyz, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-10).

Returns trust metadata for a given seller/host in the x402 agent-commerce ecosystem, including seller index status, payee and resource verification, and MCP server trust signals.

## Facts

- Endpoint: GET https://47620.xyz/x/trust/index/:host?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/47620-x402-seller-trust-index-host-lookup-a2a90a8f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UN1qIP08f2jqC6iIgqRHL

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability 47620-x402-seller-trust-index-host-lookup-a2a90a8f
```

Example prompt: Before I pay this x402 seller at 47620.xyz, can you check the trust index for that host and tell me if the payee and resource are verified and whether it's listed in the seller index?

## When to prefer this

Choose this endpoint when an AI agent needs to vet an x402 seller or MCP server before committing a USDC micropayment — specifically when you need structured trust signals (seller index, payee/resource verification) rather than general web reputation data. Prefer this over generic WHOIS or domain-reputation tools when operating within the x402 pay-per-call ecosystem.

## Known failure modes

- Host not found in seller index — returns ok:false or empty data
- Invalid or malformed host parameter — likely 400 or empty result
- Payment not received or x402 handshake failure — endpoint returns 402 before serving data
- Network or chain RPC latency causing delayed response
- Host exists but has failed verification checks — returns ok:true with negative trust signals

## How this service works

Non-custodial x402 payment gateway on Solana (1% on-chain fee) plus a pay-per-call Solana data API for agents: token price, account balances, tx lookup, trending DEX pairs, network health. No signup, no API key — pay USDC per call.

## Output

A JSON object with an ok flag, a data object containing a fetchedAt ISO timestamp and trust index details for the queried host (including seller index membership, payee verification, resource verification, and MCP server trust status), and an endpoint identifier string.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "data": {
   "fetchedAt": "<iso>"
  },
  "endpoint": "trust-index-host"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/47620-x402-seller-trust-index-host-lookup-a2a90a8f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 47620.xyz](https://www.zero.xyz/host/47620.xyz/llms.txt)