tradeos.tech

Plain-English reasoning for agents and dashboards that need to understand why a signal passed, abstained, or was vetoed. The response explains reliability drivers, disagreement, forecast alignment, risk flags, and safe next checks. Designed for validation workflows that need reasoning, not a bare score or trade instruction.

InferenceLiveeip155:8453Exactvia cdp
Activity
Nothing indexed for this service or its provider yet. Not a claim that it is unused — only that we hold no record.
$165.81
Verified settled volume
424 settlements proven x402 by their on-chain EIP-3009 marker.
$0.650
Listed price
As published in the catalog. Always read the live 402 before paying.
4
Calls · 30d
Upstream's own call count for this endpoint, not ours.
1
Unique payers · 30d
Last called 2026-05-24 20:03Z
Upstream on-chain volume
Reported by the source catalog.
Paid to
0xB445F611Cc899B623462f07C11bFEaCfD20D3C70

The 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.65USDC≈ $0.65 USD
on Base · exact scheme

Pay 0.65 USDC on Base to 0xB445…D3C70. The signed payment is good for 5 minutes.

USD Coin contract
0x8335…02913
Payment window
5 minutes
As published
650000 smallest units
The catalog’s raw entry
[
  {
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "extra": {
      "name": "USD Coin",
      "version": "2",
      "channelId": "x402-direct",
      "resourceId": "tradeos-signal-decision-context",
      "resourceType": "intelligence_report"
    },
    "payTo": "0xB445F611Cc899B623462f07C11bFEaCfD20D3C70",
    "amount": "650000",
    "scheme": "exact",
    "network": "eip155:8453",
    "maxTimeoutSeconds": 300
  }
]

Extensions

{
  "bazaar": {
    "info": {
      "input": {
        "body": {
          "output": "machine_actionable_json",
          "symbol": "BTCUSDT",
          "request_type": "signal_intelligence"
        },
        "type": "http",
        "method": "POST",
        "bodyType": "json",
        "input_hints": [
          "symbol",
          "signal_ids",
          "signal_type",
          "metadata"
        ]
      },
      "output": {
        "type": "json",
        "format": "IntelligenceResponse",
        "example": {
          "sample": true,
          "notices": [
            "Synthetic shape only. Paid calls return live bounded TradeOS intelligence."
          ],
          "verdict": "sample_read_only_intelligence_available",
          "service_id": "tradeos-signal-decision-context",
          "request_type": "signal_intelligence",
          "output_highlights": [
            "decision_label",
            "signal_score",
            "reliability_drivers",
            "disagreement_drivers"
          ]
        },
        "metadata": {
          "market_headline": "Why-pass, why-abstain, and why-veto explanation for crypto signals",
          "safety_boundary": [
            "read_only_research",
            "no_execution",
            "no_custody",
            "no_copy_trading",
            "no_personalized_financial_advice"
          ],
          "market_differentiator": "Explains signal state instead of returning a bare buy/sell-like score.",
          "canonical_search_queries": [
            "signal decision context",
            "crypto signal pass abstain veto",
            "signal validation explanation",
            "signal decision reasoning",
            "signal decision explanation"
          ]
        },
        "sample_url": "https://tradeos.tech/x402/v1/samples/tradeos-signal-decision-context",
        "listing_url": "https://tradeos.tech/x402/v1/listings/tradeos-signal-decision-context",
        "sample_html_url": "https://tradeos.tech/x402/v1/samples/tradeos-signal-decision-context?format=html",
        "listing_html_url": "https://tradeos.tech/x402/v1/listings/tradeos-signal-decision-context?format=html",
        "output_highlights": [
          "decision_label",
          "signal_score",
          "reliability_drivers",
          "disagreement_drivers",
          "forecast_alignment",
          "risk_flags"
        ]
      }
    },
    "tags": [
      "crypto",
      "signal-decision",
      "validation",
      "reasoning",
      "agents"
    ],
    "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",
              "properties": {
                "output": {
                  "type": "string"
                },
                "symbol": {
                  "type": "string"
                },
                "chain_id": {
                  "type": "string"
                },
                "metadata": {
                  "type": "object"
                },
                "contract_address": {
                  "type": "string"
                }
              },
              "additionalProperties": true
            },
            "type": {
              "type": "string",
              "const": "http"
            },
            "method": {
              "type": "string",
              "const": "POST"
            },
            "bodyType": {
              "type": "string",
              "const": "json"
            }
          }
        },
        "output": {
          "type": "object"
        }
      }
    },
    "summary": "Explain why a crypto signal passed, abstained, or was vetoed without giving a trade order.",
    "serviceName": "TradeOS Signal Decision Context"
  }
}

Provenance

Seen in the source catalog
2026-05-24 20:03Z
Last indexed by Roundhouse
2026-06-14 01:00Z
Last enriched (probe, favicon, geo)
2026-09-12 10:15Z
x402 version
2
Max timeout
300s
Liveness probe
HTTP 200
Report

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

Nothing indexed for this service or its provider yet. Not a claim that it is unused — only that we hold no record. Verified volume counts only settlements with an on-chain EIP-3009 marker.

Open skill.md
Show the prompt
Using Roundhouse, look up the x402 service tradeos.tech 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=tradeos.tech'
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://tradeos.tech/x402/v1/intelligence/tradeos-signal-decision-context, 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.