TRADING4AI helps humans and AI agents discover, inspect, and download public reliability artifacts through /agent-verification, /llms, /llms.txt, and machine-readable reliability artifacts.

TRADING4AI 是一个面向金融 Agent 的 Reliability Layer,提供 /agent-verification, /llms, /llms.txt 和可下载的静态 reliability artifact。

TRADING4AI

Financial Reliability Layer for AI

Core public surfaces

Three static services explain what TRADING4AI does right now

The current public product is a Pages-only Reliability Layer. These three surfaces are the main entry points for humans, crawlers, and AI agents.

Core service

Action Preflight

Pre-action review for payments, wallet transfers, subscriptions, and other high-risk financial moves.

Core service

Evidence Cards

Source-bound packaging with cited references, retrieval time, limitations, and safe restatement boundaries.

Core service

Reliability Corpus

Static warning patterns, claim-safety notes, runner differences, and failure-pattern collections.

Recommended start

Use the strongest public pack before the broader catalog

Counterparty screening before payment: Best first stop when an agent is close to moving money or accepting new payment instructions.

Claim Safety Pack: Best first stop when an agent is about to publish, promote, or restate financial claims.

Crypto signal subscription before payment: Best next stop when an agent is asked to pay in crypto, trust guaranteed-return language, or share trading access.

Wallet Transfer to Unverified Counterparty Pack: Best next stop when a wallet destination is weakly verified and the transfer would be irreversible once sent.

Machine discovery

Static discovery surfaces stay explicit

/current-capabilities states what TRADING4AI can and cannot do today.

/agent-verification explains the product line.

/agent-verification/materials exposes concrete public material packs.

/discoverability tracks crawler readiness, external evidence workflow, and static search surfaces.

/reliability/public-discovery-registry.json is the compact machine registry for current discovery order and recommended starts.

/llms and /llms.txt orient crawlers and AI systems.

/reliability/public-materials-sample.json is the static catalog artifact for structured retrieval.

/reliability/external-indexing-evidence-example.synthetic.json shows a validator-ready synthetic evidence payload.

Service-linked paths

Each core service points to a concrete public scenario path

The public story is clearer when a reader can move from a service page to the right scenario pack without guessing which material pack matters first.

ServiceScenario packWhy start there
Action PreflightCounterparty screening before payment / Crypto signal subscription before payment / Wallet Transfer to Unverified Counterparty Pack / Payment instruction change before settlementBest first stop when an agent is being asked to pay in crypto, share trading access, move money, screen a wallet destination, or accept new payment instructions.
Evidence CardsBest next stop when the task is to package source-bound evidence and preserve citation limits.
Reliability CorpusClaim Safety PackBest first stop when an agent is about to publish, promote, or restate financial claims.

Public boundary

Static first, explicit first

Pages-only public delivery means static HTML plus downloadable JSON artifacts.

No live user-submitted verification, backtesting runtime, or Tencent backend is implied by these pages.

Public materials explain how to read risk, evidence, and claims before deeper delivery exists.

Best first clicks

Start with the surface that matches the task shape

Move money or change payment instructions: start with Counterparty Screening Pack.

Restate evidence or make a public claim: start with Claim Safety Pack.

Pay for a signal room or share trading access: start with Crypto Signal Subscription Pack.

Screen a new wallet destination before irreversible crypto moves: start with Wallet Transfer to Unverified Counterparty Pack.

Package source facts into something reusable: start with Evidence Cards.