TrustAgent
Judgment engine over ERC-8004. Verify whether an address or contract is safe to pay.
DataLiveeip155:8453Exactvia cdp
Calls · 30d
2↑ 17%
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 26 snapshots so far.
$0.22
Verified settled volume
38 settlements proven x402 by their on-chain EIP-3009 marker.
$0.010
Listed price
As published in the catalog. Always read the live 402 before paying.
2
Calls · 30d
Upstream's own call count for this endpoint, not ours.
1
Unique payers · 30d
Last called 2026-09-13 17:19Z
—
Upstream on-chain volume
Reported by the source catalog.
Paid to
0x6121654D3Fd4C8B42a90d30472E4D40927C3e6BBThe wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Provider
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
0.010003USDC≈ $0.010003 USD
on Base · exact scheme
Pay 0.010003 USDC on Base to 0x6121…3e6BB. The signed payment is good for 1 minute.
- Paid to
- 0x6121…3e6BB
- USD Coin contract
- 0x8335…02913
- Payment window
- 1 minute
- As published
- 10003 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x6121654D3Fd4C8B42a90d30472E4D40927C3e6BB",
"amount": "10003",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 60
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {
"type": "contract",
"chain": "base",
"addresses": [
"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"0x4200000000000000000000000000000000000006"
]
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"failed": "count that errored",
"safest": "address with the highest score, or null if none of the batch produced a score. Unscorable addresses are excluded from the ranking rather than sorted as zero.",
"results": "array of {address, trustScore, riskBand, recommendation, confidence, subjectType, topFlags}. trustScore is null where no rule could be evaluated.",
"succeeded": "count scored without error",
"unscorable": "count scored without error but with no evaluable evidence"
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method",
"bodyType",
"body"
],
"properties": {
"body": {
"required": [
"addresses"
],
"properties": {
"type": {
"type": "string",
"description": "OPTIONAL. Subject type hint applied to all."
},
"chain": {
"type": "string",
"description": "OPTIONAL. Only \"base\" is served; any other value is refused rather than answered from the wrong chain. Defaults to base."
},
"addresses": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 10,
"minItems": 1,
"description": "REQUIRED. string[] of 1-10 EVM addresses."
}
}
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST"
],
"type": "string"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object",
"properties": {
"failed": {
"description": "count that errored"
},
"safest": {
"description": "address with the highest score, or null if none of the batch produced a score. Unscorable addresses are excluded from the ranking rather than sorted as zero."
},
"results": {
"description": "array of {address, trustScore, riskBand, recommendation, confidence, subjectType, topFlags}. trustScore is null where no rule could be evaluated."
},
"succeeded": {
"description": "count scored without error"
},
"unscorable": {
"description": "count scored without error but with no evaluable evidence"
}
}
}
}
}
}
}
}
}Provenance
- Seen in the source catalog
- 2026-09-13 17:19Z
- Last indexed by Roundhouse
- 2026-09-25 01:40Z
- Last enriched (probe, favicon, geo)
- 2026-09-12 10:15Z
- x402 version
- 2
- Max timeout
- 60s
- Liveness probe
- HTTP 405
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 26 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service TrustAgent and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=TrustAgent' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://trust-agent.io/v1/verify/batch, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.