relay.straelo.com
No description published for this endpoint.
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.
Live 402 challenge
Captured by the enrichment pass, not read just now. Prices can change — always read the 402 the endpoint answers with.
{
"error": "payment_required"
}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.03 USDC on Base to 0x267e…2d232. The signed payment is good for 1 minute.
- Paid to
- 0x267e…2d232
- USD Coin contract
- 0x8335…02913
- Payment window
- 1 minute
- As published
- 30000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x267ead21c0a5c1bf7e44cb357641556edc52d232",
"amount": "30000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 60
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {
"query": "x402 protocol",
"intent": "search"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"intent": "search",
"result": {
"query": "x402 protocol",
"sources": []
},
"missing": [
"no_sources_found"
],
"sources": [],
"freshness": "live",
"observed_at": "2026-01-01T00:00:00Z",
"data_quality": {
"source_count": 0
}
}
}
},
"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",
"anyOf": [
{
"required": [
"topic",
"objective"
]
},
{
"required": [
"intent"
]
}
],
"required": [],
"properties": {
"url": {
"type": "string",
"format": "uri",
"description": "Public HTTP(S) URL for read or changes."
},
"query": {
"type": "string",
"description": "Live-web query for search, extract, evidence, or compare."
},
"topic": {
"type": "string",
"description": "Legacy structured-research topic, used with objective only when intent is omitted."
},
"fields": {
"type": "array",
"items": {
"enum": [
"title",
"url",
"snippet",
"text"
],
"type": "string"
},
"description": "Unique source fields for extract."
},
"intent": {
"enum": [
"search",
"read",
"extract",
"evidence",
"research",
"compare",
"changes"
],
"type": "string",
"description": "Selected Web Intelligence operation."
},
"targets": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 5,
"minItems": 2,
"description": "Two to five named targets for compare."
},
"question": {
"type": "string",
"description": "Natural-language question for research."
},
"objective": {
"type": "string",
"description": "Legacy structured-research objective, used with topic only when intent is omitted."
},
"previous_state": {
"type": "object",
"description": "Optional client-supplied prior read state for stateless changes detection."
}
},
"description": "Select an intent and provide only its fields. Without intent, topic and objective preserve the legacy structured-research request."
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST",
"PUT",
"PATCH"
],
"type": "string"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object",
"required": [
"intent",
"result",
"observed_at",
"freshness",
"data_quality",
"missing"
],
"properties": {
"usage": {
"type": [
"object",
"null"
],
"description": "Measured provider usage when applicable."
},
"intent": {
"type": "string",
"description": "Executed selected intent."
},
"result": {
"type": "object",
"description": "Intent-specific machine-readable result."
},
"missing": {
"type": "array",
"items": {
"type": "string"
},
"description": "Known unavailable information."
},
"sources": {
"type": "array",
"description": "Source provenance when the intent uses web sources."
},
"economics": {
"type": [
"object",
"null"
],
"description": "Application-calculated estimated costs when applicable."
},
"freshness": {
"type": "string",
"description": "Current-data or client-state comparison context."
},
"observed_at": {
"type": "string",
"format": "date-time",
"description": "UTC observation time."
},
"data_quality": {
"type": "object",
"description": "Available source or content coverage."
}
}
}
}
}
}
}
}
}Provenance
- Seen in the source catalog
- —
- Last indexed by Roundhouse
- 2026-10-19 19:15Z
- Last enriched (probe, favicon, geo)
- 2026-09-27 04:45Z
- x402 version
- 2
- Max timeout
- 60s
- Liveness probe
- HTTP 402
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. 32 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 relay.straelo.com 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=relay.straelo.com' 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://relay.straelo.com/web-intelligence, 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. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.