aicom_clear
Release-condition oracle for agent escrow: a signed, recomputable 'did the delivery meet the committed spec?' DECISION (met|not-met|human-review → release|refund) any escrow can act on. POST /clear/commit (free) freezes the criteria, GET /clear for a nonce, then POST {nonce, commit, deliverable}.
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
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.
Pay 0.05 USDC on Base to 0x671e…7834e. The signed payment is good for 5 minutes.
- Paid to
- 0x671e…7834e
- USD Coin contract
- 0x8335…02913
- Payment window
- 5 minutes
- As published
- 50000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2",
"resource": "https://aicomglobal.com/clear/attest"
},
"payTo": "0x671eae6b65be7282c0cE74016d22A3d579e7834e",
"amount": "50000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {
"nonce": "clr_1a2b3c4d",
"commit": "{\"commitId\":\"cmt_1a2b3c4d\"}",
"deliverable": "the delivered artifact or its sha256 hash"
},
"type": "http",
"method": "POST",
"bodyType": "json"
}
},
"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": {
"type": "object",
"required": [
"nonce",
"commit"
],
"properties": {
"nonce": {
"type": "string"
},
"commit": {
"type": "string",
"description": "the full signed Commit from POST /clear/commit, JSON-stringified"
},
"deliverable": {
"type": "string",
"description": "the deliverable content or its sha256 hash"
}
}
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST"
],
"type": "string"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
}
},
"additionalProperties": false
}
}
},
"category": "finance",
"discoverable": true
}
}Provenance
- Seen in the source catalog
- 2026-07-03 12:37Z
- Last indexed by Roundhouse
- 2026-07-23 06:10Z
- Last enriched (probe, favicon, geo)
- 2026-09-10 19:15Z
- x402 version
- 2
- Max timeout
- 300s
- Liveness probe
- HTTP 404
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
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service aicom_clear 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=aicom_clear' 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://aicomglobal.com/clear/attest, 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.