TRADING4AIMachine index for public reliability surfaces and static artifacts

For agents

Stable entry points for public reliability surfaces and static delivery artifacts.

This page is the human-readable index for machines and developers. Use it to find the reliability layer, discovery files, and downloadable artifacts without confusing public discovery with any live backend or runtime verification service.

Open materials Open discoverability Discovery registry JSON

Action PreflightPre-action risk checks Evidence CardsCited evidence packaging Reliability CorpusFailure patterns and warnings Counterparty PackPre-payment review guidance Claim Safety PackPublication boundary guidance Crypto PackGuaranteed-return risk review Wallet Transfer PackIrreversible wallet-destination review

Pages-only posture

Static export, downloadable JSON, semantic HTML.

Public phasePages only

Runtime shapeStatic HTML + downloadable JSON

Backend dependencyDeferred in this batch

Crawler postureIndexable and semantic

Evidence modeBounded, auditable, pre-generated

Live fetchNot required for the public pages

Boundary

Public discovery is safe for indexing and orchestration.

Static public examples do not prove current request-time delivery, signed access, or user-specific review.

Public surfaces describe reliability artifacts, static JSON, and boundaries, not live trading or brokerage controls.

Do not start current work from /samples, /examples, or /openapi.json when the current reliability layer already covers the task.

Human site and machine site share the same public delivery layer, but the reliability pages are the best first stop for crawlers and AI agents in this phase.

Machine surfaces

Start with the right surface for the job

EntryPurpose

Discovery priority

Primary public discovery comes first

These groups mirror the shared machine files so developers, crawlers, and agents read the public reliability layer in the same order as llms.txt and agent.json.

Primary public discovery

Current Capabilities: https://trading4ai.com/current-capabilities - current truth boundary for what the Pages-only reliability layer can and cannot do today.

Reliability Home: https://trading4ai.com/agent-verification - Best first stop for the current three-service public product line.

Public Materials: https://trading4ai.com/agent-verification/materials - Open when the scenario is already concrete and the reader needs pack-level guidance.

Counterparty screening before payment: https://trading4ai.com/agent-verification/materials/counterparty-screening-pack - Start here first when an agent is close to moving money, accepting new payment instructions, or acting on weak counterparty evidence.

Claim-safety review before publication: https://trading4ai.com/agent-verification/materials/claim-safety-pack - Start here next when an agent is about to restate evidence, strategy language, or marketing claims in public-facing form.

Crypto signal subscription before payment: https://trading4ai.com/agent-verification/materials/crypto-signal-subscription-pack - Start here first when an agent is asked to pay in crypto, trust guaranteed-return language, or connect a brokerage account for auto-trading access.

Wallet transfer to unverified counterparty: https://trading4ai.com/agent-verification/materials/wallet-transfer-unverified-counterparty-pack - Start here next when a high-risk crypto wallet transfer points to a new counterparty and the destination remains irreversible, weakly verified, or private-group only.

Payment instruction change before settlement: https://trading4ai.com/agent-verification/materials/payment-instruction-change-pack - Start here first when a beneficiary, bank account, or wallet destination changes shortly before payment and the instruction arrives through a weak or unverified channel.

Action Preflight: https://trading4ai.com/agent-verification/action-preflight - Open when the task is a high-risk financial action review before money, credentials, or access move.

Evidence Cards: https://trading4ai.com/agent-verification/evidence-cards - Open when the task is to package public-source facts into cited, bounded evidence.

Evidence Card Library: https://trading4ai.com/agent-verification/evidence-cards/library - Open when a crawler or agent needs the compact index of all public sample evidence cards.

Reliability Corpus: https://trading4ai.com/agent-verification/reliability-corpus - Open when the task is to compare a claim or workflow against known warning patterns.

Machine Bridge: https://trading4ai.com/llms - Use when a human or agent wants the bridge-page explanation before switching to compact machine files.

llms.txt: https://trading4ai.com/llms.txt - Use for compact plain-text discovery once the current public boundary is understood.

Agent Card: https://trading4ai.com/.well-known/agent.json - Use for stable machine-readable entry-point discovery and contract metadata.

Discoverability Status: https://trading4ai.com/discoverability - Use when tracking crawler readiness, sitemap submission work, and external indexing evidence.

Supporting public JSON artifacts

Public Discovery Registry: https://trading4ai.com/reliability/public-discovery-registry.json - Use the compact registry when a crawler or AI agent needs the recommended public discovery order without parsing longer narrative surfaces first.

Public Materials JSON: https://trading4ai.com/reliability/public-materials-sample.json - Download the shared public-material catalog after the HTML pages define scope and limitations.

External Indexing Evidence Synthetic Example: https://trading4ai.com/reliability/external-indexing-evidence-example.synthetic.json - Use as a validator-ready filled example after reading the discoverability status and template artifacts.

Action Preflight JSON sample: https://trading4ai.com/reliability/action-preflight-sample.json - Download the sample contract when another machine needs the stable preflight artifact.

Evidence Cards JSON sample: https://trading4ai.com/reliability/evidence-cards-sample.json - Download the sample evidence package after the page-level citation and limitation rules are understood.

Evidence Card Library JSON: https://trading4ai.com/reliability/evidence-card-library.json - Download the static library index when an agent needs every public sample evidence card in one artifact.

Reliability Corpus JSON sample: https://trading4ai.com/reliability/reliability-corpus-sample.json - Download the sample corpus when a machine needs the static reference payload rather than the explanatory page.

Legacy/runtime surfaces

Legacy OpenAPI snapshot: https://trading4ai.com/openapi.json - Legacy runtime snapshot; not the recommended first read for the Pages-only Reliability Layer.

Legacy Strategy Catalog: https://trading4ai.com/api/v1/strategies - Legacy/runtime discovery surface; not expanded by this Pages-only batch.

Legacy Product Index: https://trading4ai.com/api/v1/products - Legacy/runtime discovery surface; not part of the current static reliability entry path.

Legacy Quant Lab templates: https://trading4ai.com/api/v1/quant-lab/templates - Legacy template snapshot; secondary to the public reliability pages in this phase.

Legacy Orders API: https://trading4ai.com/api/v1/orders - Legacy order/payment API reference; not a public reliability starting point.

Legacy Claims API template: https://trading4ai.com/api/v1/claims/{claim_token} - Legacy protected-delivery lookup template; do not treat it as a public review workflow.

Legacy Entitlement template: https://trading4ai.com/api/v1/entitlements/{token} - Legacy protected-access template; secondary to the Pages-only public Reliability Layer.

Guidance

Use primary_public_discovery first when the task is about the current Pages-only Reliability Layer.

Use supporting_public_samples only for static reliability JSON artifacts after the public service/page boundary is understood.

Treat legacy_runtime_surfaces as secondary discovery only and do not infer new live runtime support from them.

Service contract inventory

Reliability services are static retrieval surfaces

Action Preflight, Evidence Cards, and Reliability Corpus are published for discovery, retrieval, and review of static artifacts. They do not accept live requests, run backtests, call Tencent backend runtime, or make request-time financial judgments.

Service contract

Action Preflight

A static/client-side pre-action check that classifies a proposed financial-agent action as allow, review, or block.

HTML page: /agent-verification/action-preflight

Static JSON artifact: /reliability/action-preflight-sample.json

artifactStatusstatic_public_sample

evidenceScopepre_action_risk_check

reviewModehuman_review_required

citationPolicydo_not_upgrade_to_clearance

schemaVersiontrading4ai-public-reliability-v1

artifactVersionaction-preflight-sample-2026-05-23

staticSnapshotAt2026-05-23T00:00:00.000Z

Accepted inputFinancial action draft

Output shapeBounded preflight verdict

Suitable usesScreening a proposed crypto payment or subscription before the user sends funds / Pausing brokerage-connection or API-key requests for human review / Separating evidence-gathering tasks from risky action requests

LimitationsRuns as a static/client-side demo in this phase, not a server-side decision service / Does not prove an action is legal, safe, suitable, profitable, or compliant / High-risk or ambiguous actions still require qualified human review

Non-goalsNo live backend judgment / No brokerage execution or wallet transaction / No backtesting or profitability scoring / No compliance clearance

This artifact is a pre-action risk reference, not approval or compliance clearance.

Artifact provenance: action-preflight-sample-2026-05-23 / /reliability/action-preflight-sample.json

Citation fields: artifactVersion, generatedAt, staticSnapshotAt, sampleResult.retrievedAt, sampleResult.sourceRefs

When citing this sample, preserve artifactVersion, generatedAt, and the sampleResult.retrievedAt timestamp.

Treat the JSON artifact as a static sample contract for review boundaries, not as live approval or clearance.

Use the sample contract to explain why the action pauses or stops.

Do not restate allow/review/block as a legal or compliance verdict.

Index the HTML page for service explanation and the JSON artifact for the sample contract

Treat the artifact as a static example, not as a request-time endpoint

Do not infer autonomous trading support from the allow/review/block vocabulary

Start here

Read the HTML page first when the agent is still deciding whether a financial action should pause, proceed, or escalate.

Check the decision meaning, required checks, and source refs before any money movement, account link, credential share, or access grant.

Treat the browser preflight tool as a static public demo of the contract, not as a live approval service.

Open linked pack when

Open the linked pack when the task is already a concrete payment, wallet transfer, or counterparty-screening review.

Use the pack when you need a scenario-level checklist, evidence-to-collect list, and blocked-claim examples.

Download JSON when

Download the JSON only after the HTML page makes the scope, limitations, and non-goals clear.

Use the artifact for machine handoff, schema inspection, or audit storage when another agent needs the stable sample contract.

Escalate to human review when

The action would move money, grant credentials, connect an account, or create an irreversible crypto payment.

The output still contains blocked risk flags, unresolved counterparty identity, or mismatched payment instructions.

Someone is treating allow / review / block as legal approval, compliance clearance, or investment advice.

This page does not do

It does not clear a payment, certify a counterparty, or grant compliance approval.

It does not execute an order, move funds, or connect a brokerage account.

It does not run backtests or predict returns.

Service contract

Evidence Cards

A static evidence-packaging surface that turns source refs, timestamps, fields used, safe statements, blocked statements, and limitations into reviewable cards.

HTML page: /agent-verification/evidence-cards

Static JSON artifact: /reliability/evidence-cards-sample.json

artifactStatusstatic_public_sample

evidenceScopesource_bound_fact

reviewModereference_only

citationPolicysource_bound_summary_only

schemaVersiontrading4ai-public-reliability-v1

artifactVersionevidence-cards-sample-2026-05-23

staticSnapshotAt2026-05-23T00:00:00.000Z

Accepted inputEvidence request or source set

Output shapeEvidence card package

Suitable usesPackaging public-source facts for AI retrieval and later audit / Showing which claims can be repeated and which must be blocked / Creating a static citation trail for financial-agent content

LimitationsEvidence Cards package sources; they do not value securities or recommend action / Source freshness, methodology, and field definitions can change after retrieval / Name-only or source-only evidence is not legal or compliance clearance

Non-goalsNo investment advice / No buy/sell/hold signal / No live source scraping in this phase / No formal compliance decision

Only repeat source-bound facts with timestamps and limitations preserved.

Artifact provenance: evidence-cards-sample-2026-05-23 / /reliability/evidence-cards-sample.json

Citation fields: artifactVersion, generatedAt, cards[].observedAt, cards[].retrievedAt, cards[].sourceRefs

When citing a card, keep artifactVersion, generatedAt, observedAt, retrievedAt, and sourceRefs visible together.

Reuse the artifact only for source-bound summaries; do not upgrade the sample into advice, clearance, or suitability language.

Use the card to support audit and review summaries.

Do not upgrade the card into investment advice or compliance clearance.

Use the HTML page for explanation and examples

Use the JSON artifact for machine handoff and schema inspection

Preserve safe/blocked statement boundaries when summarizing

Start here

Read the HTML page first when the main task is to package public-source facts into something cited, reviewable, and reusable.

Check the source refs, retrieved time, safe statements, and blocked statements before repeating any financial claim.

Treat the cards as bounded evidence packaging, not as a recommendation layer.

Open linked pack when

Open the linked pack when the evidence task is already concrete, such as macro-release context or public-company filing review.

Use the pack when you need scenario-specific inputs, outputs, and citation boundaries for that evidence bundle.

Download JSON when

Download the JSON only after the HTML page has explained the source boundary, safe statements, and limitations.

Use the artifact for handoff, retrieval experiments, or contract inspection when another agent needs the sample schema without the UI.

Escalate to human review when

A reader wants to turn source-bound evidence into buy/sell/hold guidance, suitability language, or safety claims.

The evidence is missing source refs, timestamps, field definitions, or contains unresolved source conflicts.

The claim could influence payment, onboarding, publication, or compliance-sensitive wording without qualified review.

This page does not do

It does not issue investment advice, price targets, or buy/sell/hold guidance.

It does not act as compliance clearance or legal approval.

It does not run live scraping or request-time evidence assembly in this phase.

Service contract

Reliability Corpus

A static reference library of failure patterns, runner-difference notes, assumption drift, and claim-safety examples.

HTML page: /agent-verification/reliability-corpus

Static JSON artifact: /reliability/reliability-corpus-sample.json

artifactStatusstatic_public_sample

evidenceScopewarning_pattern

reviewModereference_only

citationPolicywarning_reference_only

schemaVersiontrading4ai-public-reliability-v1

artifactVersionreliability-corpus-sample-2026-05-23

staticSnapshotAt2026-05-23T00:00:00.000Z

Accepted inputCorpus lookup context

Output shapeReference corpus result

Suitable usesChecking whether a backtest or strategy report has known failure modes / Teaching financial agents to avoid unsafe or overconfident claim patterns / Providing crawlable reference material for reliability and claim-safety review

LimitationsA corpus hit is a warning shape, not proof that every related strategy is invalid / The corpus does not replace runner verification or human judgment / Source behavior, platform documentation, and assumptions can change over time

Non-goalsNo live strategy scoring / No complete financial-risk ontology / No execution approval / No guarantee that all possible failure modes are covered

This corpus is a warning reference, not a final verdict about a strategy or system.

Artifact provenance: reliability-corpus-sample-2026-05-23 / /reliability/reliability-corpus-sample.json

Citation fields: artifactVersion, generatedAt, entries[].firstSeenAt, entries[].lastUpdatedAt, entries[].sourceRefs

When citing a corpus entry, keep artifactVersion, generatedAt, firstSeenAt, lastUpdatedAt, and sourceRefs in the review trace.

Treat a corpus hit as a warning reference only; it is not a final verdict about a strategy, report, or system.

Use the corpus to trigger deeper verification and review.

Do not upgrade a corpus hit into a universal invalidation claim.

Index the HTML page for browsable failure patterns

Use the JSON artifact for stable machine retrieval

Treat entries as reference warnings, not final verdicts

Start here

Read the HTML page first when the task is to compare a financial claim, report, or workflow against known warning patterns.

Treat corpus entries as reusable review hints that trigger deeper verification, not as final proof by themselves.

Use the filters and sample collections as a static reference workflow, not as a scoring engine.

Open linked pack when

Open the linked pack when the review has become concrete, especially for publication wording, claim safety, or scenario-level escalation logic.

Use the pack when you need a task-shaped checklist instead of a broad warning library.

Download JSON when

Download the JSON only after the HTML page makes the warning-only scope and limitations explicit.

Use the artifact for retrieval, audit storage, or pattern benchmarking when another agent needs the stable failure-pattern dataset.

Escalate to human review when

A corpus hit is being treated as final proof, execution approval, or a universal invalidation claim.

The review would block or approve money movement, compliance language, or public claims without source-specific verification.

Runner behavior, assumptions, or time windows need fresh confirmation before any high-stakes conclusion.

This page does not do

It does not score a live strategy, rank systems, or certify that a report is safe.

It does not replace runner verification, human judgment, or scenario-specific evidence review.

It does not run backtests or produce request-time backend judgments.

Discovery conventions

Reliability actions and evidence cards expose downloadable JSON artifacts instead of live request/response endpoints in this batch.

Compact registry for the current discovery order is published at /reliability/public-discovery-registry.json.

Public Materials adds concrete scenario packs for crypto subscription risk, counterparty screening, unverified wallet transfers, payment instruction changes, macro context, filing review, and claim safety.

Each pack now has its own stable detail URL so crawlers and AI systems can cite scenario-level reliability pages directly.

Strategy catalog pages and historical archives are secondary context, not the primary trust surface.

Core envelope fields remain status, data, error, request_id, and timestamp where JSON artifacts exist.

Public boundaries

Use the reliability layer and /llms surfaces for discovery.

Use current reliability pages and static JSON artifacts before any historical archive context.

Do not infer live autonomous trading, brokerage connectivity, or evidence-free publication from public surfaces.

Current priority

Keep the reliability layer primary

TRADING4AI's current public product line is the Pages-only reliability layer.

Machines should start from /agent-verification, then open the matching service page and JSON artifact.

Legacy runtime, sample archive, and legacy discovery surfaces may still matter, but they are secondary to the reliability-layer story in this phase.

Suggested path

How a machine should read the public layer

1. Start at /agent-verification for the current Reliability Layer story.

2. Open the matching service page for the task shape.

3. Open the linked scenario pack when the task is already concrete, such as payment screening, irreversible wallet transfer review, payment instruction change review, filing evidence packaging, or claim review.

4. Download the JSON artifact only after the HTML page makes the boundary clear.

Public Material routing rules

Know when to stay at the service layer and when to escalate

These rules keep machines inside the current Pages-only boundary. Start with the right HTML explanation, move into a scenario pack only when the task is concrete, reuse JSON only after the scope is clear, and escalate anything that starts to look like approval or irreversible action.

Stay on the service page when

Stay on the service page when the task is still broad and the agent has not yet identified the exact review scenario.
Use the service layer first when the main need is to understand the general contract, output shape, and boundary language for Action Preflight, Evidence Cards, or Reliability Corpus.
Do not jump straight to a pack when the action, source set, or publication claim is still too vague to name a concrete review context.

Open the scenario pack when

Open the scenario pack when the task already maps to a concrete review job such as counterparty screening, wallet-transfer review, macro release packaging, filing review, or claim-safety review.
Use the pack when the reader needs scenario-level checklist items, evidence-to-collect fields, and bounded safe-versus-blocked language examples.
Treat the pack as the middle layer between the generic service page and the raw machine-readable JSON artifact.

Use the JSON artifact when

Use the JSON artifact only after the HTML page has made the scope, limitations, and non-goals clear.
Download the JSON when another agent, crawler, or retrieval workflow needs the stable machine-readable handoff surface rather than the explanatory page.
Treat the JSON as a static artifact for retrieval and audit, not as a live work queue, runtime API, or request-time review service.

Public Materials index: /agent-verification/materials

Public Materials JSON: /reliability/public-materials-sample.json

Escalate to human review when

Escalate to human review when the case is high-value, private, legally sensitive, or close to irreversible money movement.
Escalate when the evidence stays incomplete, the wording upgrades partial evidence into certainty, or the pack itself says unresolved items remain.
Do not treat any static page or JSON artifact as approval, clearance, or final compliance judgment.

Action routing index

High-risk actions now map to concrete public material packs

Use this table when an agent already knows the user action shape and needs the shortest path to the right static pack, JSON artifact, and default review posture.

Action typePackDefault postureRoute trigger

crypto_signal_subscription_payment
before_payment_or_account_connectionCrypto signal subscription before payment
JSON artifactblock
Payment, custody, brokerage/API access, or credentials may move before operator identity and performance claims are verified.A user or agent is considering paying for a crypto, AI trading, or signal subscription.
Field ids: operator_identity, payment_destination, claim_evidence, access_scope
Minimum input: Seller or operator name plus a public website, profile, or legal entity claim controlled by the offer.
Missing input fallback: Do not approve payment or account connection; collect the missing identity, payment, access, and claim evidence, then escalate if urgency or pressure remains.
Stop/escalate: Guaranteed-return, low-risk, registration, or suitability claims remain unsupported by cited public evidence.

counterparty_payment_review
before_payment_or_contractingCounterparty screening before payment
JSON artifactreview
Counterparty identity, public-warning checks, sanctions/list screening, and payment-beneficiary evidence may be incomplete before money moves.A payment, vendor onboarding, invoice, or settlement instruction names a counterparty that still needs identity review.
Field ids: operator_identity, payment_destination, source_links, match_confidence
Minimum input: Counterparty legal name, aliases, jurisdiction, website, registration number, or public profile evidence.
Missing input fallback: Defer payment or onboarding; collect missing identifiers and source links, then escalate if match confidence or beneficiary ownership remains unresolved.
Stop/escalate: Exact identity, jurisdiction, beneficiary ownership, or source match confidence is unresolved.

wallet_transfer_unverified_counterparty
before_wallet_transferWallet transfer to unverified counterparty
JSON artifactblock
An irreversible wallet transfer may be sent to a weakly verified counterparty or destination before ownership and warning-source checks are complete.A user or agent is preparing to send crypto to a new, private-group, or weakly verified counterparty wallet.
Field ids: wallet_destination, operator_identity, wallet_ownership_evidence, source_links
Minimum input: Destination wallet address, chain or network, memo/tag if required, transfer amount, and requested settlement timing.
Missing input fallback: Do not send the transfer; collect missing destination, ownership, chain, and warning-source evidence or escalate to a human reviewer.
Stop/escalate: Counterparty identity, wallet ownership, destination chain, memo/tag, or address provenance is unresolved.

payment_instruction_change_before_settlement
before_settlement_or_releasePayment instruction change before settlement
JSON artifactblock
Changed payment instructions can redirect funds before channel integrity, beneficiary ownership, and destination details are verified.A user or agent receives changed bank, wire, invoice, wallet, memo, tag, or destination instructions before settlement.
Field ids: prior_payment_instruction, changed_instruction, known_good_confirmation, payment_destination
Minimum input: Previously approved beneficiary, payment rail, bank account, wallet, memo/tag, or settlement instruction on record.
Missing input fallback: Do not release payment on changed instructions; collect known-good confirmation and dual-approval evidence, then escalate if any destination detail remains incomplete.
Stop/escalate: Known-good channel confirmation, beneficiary ownership, prior payment rail comparison, or dual approval is missing.

macro_release_context_interpretation
before_macro_summary_or_market_commentaryMacro release context packaging
JSON artifactallow_with_limits
A macro data point may be repeated without revision, vintage, release-lag, COT lag, or non-trading limitations.An agent needs to summarize a macro release, FRED series, BLS release, or CFTC positioning note.
Field ids: macro_release_context, source_links, intended_use_context
Minimum input: Official source, series or release identifier, publication timestamp, and retrieval timestamp.
Missing input fallback: Defer market interpretation; collect release, vintage, unit, lag, and comparison context, and keep any interim output as a source-bound note.
Stop/escalate: The summary converts a reported value into a market call, trade instruction, or portfolio recommendation.

public_company_filing_review
before_filing_summary_or_company_claimPublic company filing review
JSON artifactreview
A filing fact may be summarized without CIK, accession, period, item, exhibit, XBRL, unit, scale, or not-live-refresh boundaries.An agent needs to summarize or cite a public-company filing fact before using it in research or a company claim.
Field ids: filing_identifier, filing_fact_reference, source_links, intended_use_context
Minimum input: Company name, ticker if used, CIK, form type, accession number, filing date, and reporting period.
Missing input fallback: Defer the company claim; collect missing filing identifiers, item or exhibit references, units, and retrieval context before publishing or citing.
Stop/escalate: CIK, accession, filing date, reporting period, item, exhibit, XBRL unit, or scale context is missing.

financial_claim_publication_review
before_publication_or_distributionClaim-safety review before publication
JSON artifactescalate
A financial claim may be published as safety, approval, guarantee, compliance, or suitability language without evidence that supports it.An agent is preparing public, marketing, product, or support language about a financial tool, strategy, subscription, or review.
Field ids: claim_text, source_links, claim_category, claim_evidence, limitation_language
Minimum input: Exact claim text, audience, distribution channel, and whether the claim is public, marketing, support, or internal copy.
Missing input fallback: Escalate or do not publish; collect missing source, audience, scope, and limitation evidence before restating the financial claim.
Stop/escalate: The claim implies guaranteed returns, low risk, verified safety, legal compliance, suitability, or user protection.

Input field glossary

Preflight input fields are now stable machine terms

Use this glossary when an agent needs to ask for missing information before it routes a payment, transfer, filing summary, macro note, or public claim into a material pack.

FieldMeaningUsed by actionsMissing input risk

operator_identity
Operator identityThe seller, operator, issuer, vendor, or organization identity behind the request.crypto_signal_subscription_payment, counterparty_payment_review, wallet_transfer_unverified_counterpartyThe agent may route money or trust claims to an unverified or impersonated operator.

payment_destination
Payment destinationThe bank account, wallet address, checkout link, invoice beneficiary, or settlement rail that would receive funds.crypto_signal_subscription_payment, counterparty_payment_review, payment_instruction_change_before_settlementThe agent cannot compare the destination against the named counterparty or prior approved instructions.

claim_evidence
Claim evidenceSource material supporting performance, risk, registration, approval, compliance, or safety claims.crypto_signal_subscription_payment, financial_claim_publication_reviewThe agent may repeat promotional language as if it were verified evidence.

access_scope
Access scopeCredentials, API permissions, custody permissions, brokerage access, or automation rights being requested.crypto_signal_subscription_paymentThe agent may approve a request that silently grants trading, withdrawal, or custody control.

source_links
Source linksOfficial registries, warning pages, filings, releases, or cited public pages used as evidence.counterparty_payment_review, wallet_transfer_unverified_counterparty, macro_release_context_interpretation, public_company_filing_review, financial_claim_publication_reviewThe agent cannot separate source-bound evidence from unsourced assertion.

match_confidence
Match confidenceHow exact, partial, alias-based, or unresolved a source match is against the named counterparty.counterparty_payment_reviewThe agent may either block a legitimate action or miss a serious warning signal.

wallet_destination
Wallet destinationCrypto destination details including address, chain, memo/tag, amount, and timing.wallet_transfer_unverified_counterpartyThe agent may send funds to the wrong chain, wrong address, or unverified recipient.

wallet_ownership_evidence
Wallet ownership evidenceIndependent evidence that links the destination wallet to the intended counterparty.wallet_transfer_unverified_counterpartyThe agent may treat an attacker-supplied address as a verified counterparty address.

prior_payment_instruction
Prior payment instructionThe last approved beneficiary, bank, wallet, rail, memo/tag, or settlement instruction on record.payment_instruction_change_before_settlementThe agent cannot tell whether a destination change is normal, suspicious, or unverifiable.

changed_instruction
Changed instructionThe new payment instruction plus sender, channel, timestamp, destination fields, and urgency context.payment_instruction_change_before_settlementThe agent may approve an untraceable change without confirming what actually changed.

known_good_confirmation
Known-good confirmationIndependent confirmation through a previously trusted channel or second approver.payment_instruction_change_before_settlementThe agent may accept attacker-controlled confirmation as real approval.

macro_release_context
Macro release contextRelease, series, period, vintage, unit, seasonal adjustment, lag, and comparison context.macro_release_context_interpretationThe agent may turn a stale or incomparable data point into overconfident market commentary.

filing_identifier
Filing identifierCompany, ticker if used, CIK, form type, accession number, filing date, and reporting period.public_company_filing_reviewThe agent may cite the wrong filing, wrong period, or stale company fact.

filing_fact_reference
Filing fact referenceThe exact item, exhibit, XBRL fact, table, unit, and scale behind a filing claim.public_company_filing_reviewThe agent may restate a filing fact with the wrong unit, scale, or source location.

intended_use_context
Intended use contextWhether the output will be used as internal context, public copy, market commentary, or an action prompt.macro_release_context_interpretation, public_company_filing_reviewThe agent may apply the wrong safety boundary to the final output.

claim_text
Claim textThe exact financial claim before it is restated, published, or reused.financial_claim_publication_reviewThe agent may miss overclaiming, suitability language, or unsupported safety language.

claim_category
Claim categoryThe risk class of the claim, such as returns, risk, legality, compliance, suitability, approval, or protection.financial_claim_publication_reviewThe agent may apply generic wording where a stricter blocked-claim rule is needed.

limitation_language
Limitation languageThe caveats, source scope, retrieval time, and blocked statements that must travel with the output.financial_claim_publication_reviewThe agent may publish a bounded evidence note as if it were live clearance or final advice.

Preflight questionnaire

Question sets turn field requirements into agent collection steps

Use these static questions when the agent needs to collect missing evidence before deciding whether to stop, review, escalate, or continue with strict limitations.

ActionQuestionsFirst promptMissing input handling

crypto_signal_subscription_payment
before_payment_or_account_connection4What evidence identifies the operator identity for this crypto_signal_subscription_payment review?The agent may route money or trust claims to an unverified or impersonated operator. Do not approve payment or account connection; collect the missing identity, payment, access, and claim evidence, then escalate if urgency or pressure remains.

counterparty_payment_review
before_payment_or_contracting4What evidence identifies the operator identity for this counterparty_payment_review review?The agent may route money or trust claims to an unverified or impersonated operator. Defer payment or onboarding; collect missing identifiers and source links, then escalate if match confidence or beneficiary ownership remains unresolved.

wallet_transfer_unverified_counterparty
before_wallet_transfer4What evidence identifies the wallet destination for this wallet_transfer_unverified_counterparty review?The agent may send funds to the wrong chain, wrong address, or unverified recipient. Do not send the transfer; collect missing destination, ownership, chain, and warning-source evidence or escalate to a human reviewer.

payment_instruction_change_before_settlement
before_settlement_or_release4What evidence identifies the prior payment instruction for this payment_instruction_change_before_settlement review?The agent cannot tell whether a destination change is normal, suspicious, or unverifiable. Do not release payment on changed instructions; collect known-good confirmation and dual-approval evidence, then escalate if any destination detail remains incomplete.

macro_release_context_interpretation
before_macro_summary_or_market_commentary3What evidence identifies the macro release context for this macro_release_context_interpretation review?The agent may turn a stale or incomparable data point into overconfident market commentary. Defer market interpretation; collect release, vintage, unit, lag, and comparison context, and keep any interim output as a source-bound note.

public_company_filing_review
before_filing_summary_or_company_claim4What evidence identifies the filing identifier for this public_company_filing_review review?The agent may cite the wrong filing, wrong period, or stale company fact. Defer the company claim; collect missing filing identifiers, item or exhibit references, units, and retrieval context before publishing or citing.

financial_claim_publication_review
before_publication_or_distribution5What evidence identifies the claim text for this financial_claim_publication_review review?The agent may miss overclaiming, suitability language, or unsupported safety language. Escalate or do not publish; collect missing source, audience, scope, and limitation evidence before restating the financial claim.

Decision policy index

Static proceed/fallback/stop rules

Use preflightDecisionPolicyIndex after the questionnaire layer. It tells agents what remains allowed as a static note, when missing inputs force fallback, and when the action must stop or move to human review.

ActionProceed only whenFallbackEscalation rule

crypto_signal_subscription_payment
blockCollected and cited: Seller or operator name plus a public website, profile, or legal entity claim controlled by the offer.Do not approve payment or account connection; collect the missing identity, payment, access, and claim evidence, then escalate if urgency or pressure remains.Escalate to human review when any stop-or-escalate rule applies, when required evidence is missing, or when the requested action would treat this static pack as approval, clearance, execution advice, or live screening.

counterparty_payment_review
reviewCollected and cited: Counterparty legal name, aliases, jurisdiction, website, registration number, or public profile evidence.Defer payment or onboarding; collect missing identifiers and source links, then escalate if match confidence or beneficiary ownership remains unresolved.Escalate to human review when any stop-or-escalate rule applies, when required evidence is missing, or when the requested action would treat this static pack as approval, clearance, execution advice, or live screening.

wallet_transfer_unverified_counterparty
blockCollected and cited: Destination wallet address, chain or network, memo/tag if required, transfer amount, and requested settlement timing.Do not send the transfer; collect missing destination, ownership, chain, and warning-source evidence or escalate to a human reviewer.Escalate to human review when any stop-or-escalate rule applies, when required evidence is missing, or when the requested action would treat this static pack as approval, clearance, execution advice, or live screening.

payment_instruction_change_before_settlement
blockCollected and cited: Previously approved beneficiary, payment rail, bank account, wallet, memo/tag, or settlement instruction on record.Do not release payment on changed instructions; collect known-good confirmation and dual-approval evidence, then escalate if any destination detail remains incomplete.Escalate to human review when any stop-or-escalate rule applies, when required evidence is missing, or when the requested action would treat this static pack as approval, clearance, execution advice, or live screening.

macro_release_context_interpretation
allow_with_limitsCollected and cited: Official source, series or release identifier, publication timestamp, and retrieval timestamp.Defer market interpretation; collect release, vintage, unit, lag, and comparison context, and keep any interim output as a source-bound note.Escalate to human review when any stop-or-escalate rule applies, when required evidence is missing, or when the requested action would treat this static pack as approval, clearance, execution advice, or live screening.

public_company_filing_review
reviewCollected and cited: Company name, ticker if used, CIK, form type, accession number, filing date, and reporting period.Defer the company claim; collect missing filing identifiers, item or exhibit references, units, and retrieval context before publishing or citing.Escalate to human review when any stop-or-escalate rule applies, when required evidence is missing, or when the requested action would treat this static pack as approval, clearance, execution advice, or live screening.

financial_claim_publication_review
escalateCollected and cited: Exact claim text, audience, distribution channel, and whether the claim is public, marketing, support, or internal copy.Escalate or do not publish; collect missing source, audience, scope, and limitation evidence before restating the financial claim.Escalate to human review when any stop-or-escalate rule applies, when required evidence is missing, or when the requested action would treat this static pack as approval, clearance, execution advice, or live screening.

Static action note templates

Final output shape for source-bound notes

Use staticActionNoteTemplateIndex when the agent needs to draft the final bounded note. The template keeps the answer structured, cited, and clear about what it does not approve.

TemplateSectionsAllowed useBoundary

Crypto signal subscription before payment static action note
crypto_signal_subscription_paymentaction_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trailUse only as a static, source-bound Action Preflight note after completing action routing, the preflight questionnaire, and the decision policy.This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.

Counterparty screening before payment static action note
counterparty_payment_reviewaction_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trailUse only as a static, source-bound Action Preflight note after completing action routing, the preflight questionnaire, and the decision policy.This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.

Wallet transfer to unverified counterparty static action note
wallet_transfer_unverified_counterpartyaction_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trailUse only as a static, source-bound Action Preflight note after completing action routing, the preflight questionnaire, and the decision policy.This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.

Payment instruction change before settlement static action note
payment_instruction_change_before_settlementaction_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trailUse only as a static, source-bound Action Preflight note after completing action routing, the preflight questionnaire, and the decision policy.This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.

Macro release context packaging static action note
macro_release_context_interpretationaction_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trailUse only as a static, source-bound Evidence Cards note after completing action routing, the preflight questionnaire, and the decision policy.This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.

Public company filing review static action note
public_company_filing_reviewaction_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trailUse only as a static, source-bound Evidence Cards note after completing action routing, the preflight questionnaire, and the decision policy.This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.

Claim-safety review before publication static action note
financial_claim_publication_reviewaction_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trailUse only as a static, source-bound Reliability Corpus note after completing action routing, the preflight questionnaire, and the decision policy.This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.

Static action note examples

Filled examples for retrieval and quoting

Use staticActionNoteExampleIndex to inspect a completed static note shape before generating a source-bound explanation for a user. These are examples, not live decisions.

ExampleStatusEvidence idsBoundary

Crypto signal subscription before payment static action note example
crypto_signal_subscription_paymentblockguaranteed_return_claim, brokerage_access_request, operator_identity_gap, brokercheck_registration_gap, iapd_adviser_registration_gap, irreversible_crypto_paymentThis is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.

Counterparty screening before payment static action note example
counterparty_payment_reviewreviewbeneficiary_mismatch, ofac_name_search, entity_resolution_fields_missing, trade_csl_source_required, sam_exclusions_source_required, world_bank_debarred_source_required, cftc_red_list_source_required, opensanctions_public_reference, ftc_crypto_scam_reference, instruction_channel_change, beneficiary_proof_missingThis is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.

Wallet transfer to unverified counterparty static action note example
wallet_transfer_unverified_counterpartyblockprivate_group_alias_only, wallet_address_only, destination_integrity_gap, explorer_context_gap, irreversible_crypto_transfer, ftc_recovery_boundary, fbi_crypto_transaction_info_required, ofac_virtual_currency_source_required, ofac_sanctions_list_source_required, cftc_imposter_payment_warningThis is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.

Payment instruction change before settlement static action note example
payment_instruction_change_before_settlementblockbeneficiary_name_mismatch, unverified_channel_switch, ownership_proof_missing, destination_integrity_gap, urgency_and_secrecy_pressure, fbi_bec_source_required, ftc_consumer_alert_source_required, fincen_email_compromise_source_requiredThis is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.

Macro release context packaging static action note example
macro_release_context_interpretationallow_with_limitsfred_series_observation_vintage, fred_api_source_boundary, bls_cpi_release_source, bls_public_data_api_boundary, cftc_cot_report_lag, cftc_historical_compressed_contextThis is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.

Public company filing review static action note example
public_company_filing_reviewreviewedgar_accession_record, edgar_api_structured_fields, filing_period_item_exhibit_context, xbrl_fact_value_unit_scale, edgar_fair_access_boundary, valuation_support_missingThis is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.

Claim-safety review before publication static action note example
financial_claim_publication_reviewescalatesample_artifact_scope, no_safety_approval_source, ai_fraud_overclaim_warning, investment_group_imposter_warning, timestamp_and_scope_missing, guarantee_language_upgradeThis is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.

Agent workflow index

Read the static material sequence in order

Use agentWorkflowIndex when an AI agent needs one ordered path from routing to citation instead of manually stitching together separate JSON indexes.

WorkflowStepsLinked exampleEscalation

Crypto signal subscription before payment agent workflow
crypto_signal_subscription_paymentselect_pack, collect_minimum_inputs, answer_preflight_questionnaire, apply_decision_policy, draft_static_action_note, cite_and_escalatecrypto_signal_subscription_pack_static_action_note_exampleEscalate to qualified human review when required inputs are missing, source confidence is unresolved, payment or transfer risk is present, or the user asks for approval, clearance, execution, suitability, or compliance guarantees.

Counterparty screening before payment agent workflow
counterparty_payment_reviewselect_pack, collect_minimum_inputs, answer_preflight_questionnaire, apply_decision_policy, draft_static_action_note, cite_and_escalatecounterparty_screening_pack_static_action_note_exampleEscalate to qualified human review when required inputs are missing, source confidence is unresolved, payment or transfer risk is present, or the user asks for approval, clearance, execution, suitability, or compliance guarantees.

Wallet transfer to unverified counterparty agent workflow
wallet_transfer_unverified_counterpartyselect_pack, collect_minimum_inputs, answer_preflight_questionnaire, apply_decision_policy, draft_static_action_note, cite_and_escalatewallet_transfer_unverified_counterparty_pack_static_action_note_exampleEscalate to qualified human review when required inputs are missing, source confidence is unresolved, payment or transfer risk is present, or the user asks for approval, clearance, execution, suitability, or compliance guarantees.

Payment instruction change before settlement agent workflow
payment_instruction_change_before_settlementselect_pack, collect_minimum_inputs, answer_preflight_questionnaire, apply_decision_policy, draft_static_action_note, cite_and_escalatepayment_instruction_change_pack_static_action_note_exampleEscalate to qualified human review when required inputs are missing, source confidence is unresolved, payment or transfer risk is present, or the user asks for approval, clearance, execution, suitability, or compliance guarantees.

Macro release context packaging agent workflow
macro_release_context_interpretationselect_pack, collect_minimum_inputs, answer_preflight_questionnaire, apply_decision_policy, draft_static_action_note, cite_and_escalatemacro_release_context_pack_static_action_note_exampleEscalate to qualified human review when required inputs are missing, source confidence is unresolved, payment or transfer risk is present, or the user asks for approval, clearance, execution, suitability, or compliance guarantees.

Public company filing review agent workflow
public_company_filing_reviewselect_pack, collect_minimum_inputs, answer_preflight_questionnaire, apply_decision_policy, draft_static_action_note, cite_and_escalatepublic_company_filing_pack_static_action_note_exampleEscalate to qualified human review when required inputs are missing, source confidence is unresolved, payment or transfer risk is present, or the user asks for approval, clearance, execution, suitability, or compliance guarantees.

Claim-safety review before publication agent workflow
financial_claim_publication_reviewselect_pack, collect_minimum_inputs, answer_preflight_questionnaire, apply_decision_policy, draft_static_action_note, cite_and_escalateclaim_safety_pack_static_action_note_exampleEscalate to qualified human review when required inputs are missing, source confidence is unresolved, payment or transfer risk is present, or the user asks for approval, clearance, execution, suitability, or compliance guarantees.

Action type workflow lookup

Jump from action_type to workflow_id

Use actionTypeWorkflowLookup when an AI agent has already classified the user action and needs the matching static workflow, pack page, JSON artifact, minimum inputs, and escalation boundary immediately.

Action typeWorkflowArtifactEscalation

crypto_signal_subscription_paymentcrypto_signal_subscription_pack_agent_workflow
operator_identity, payment_destination, claim_evidence, access_scope/reliability/public-materials/crypto-signal-subscription-pack.jsonEscalate to qualified human review when required inputs are missing, source confidence is unresolved, payment or transfer risk is present, or the user asks for approval, clearance, execution, suitability, or compliance guarantees.

counterparty_payment_reviewcounterparty_screening_pack_agent_workflow
operator_identity, payment_destination, source_links, match_confidence/reliability/public-materials/counterparty-screening-pack.jsonEscalate to qualified human review when required inputs are missing, source confidence is unresolved, payment or transfer risk is present, or the user asks for approval, clearance, execution, suitability, or compliance guarantees.

wallet_transfer_unverified_counterpartywallet_transfer_unverified_counterparty_pack_agent_workflow
wallet_destination, operator_identity, wallet_ownership_evidence, source_links/reliability/public-materials/wallet-transfer-unverified-counterparty-pack.jsonEscalate to qualified human review when required inputs are missing, source confidence is unresolved, payment or transfer risk is present, or the user asks for approval, clearance, execution, suitability, or compliance guarantees.

payment_instruction_change_before_settlementpayment_instruction_change_pack_agent_workflow
prior_payment_instruction, changed_instruction, known_good_confirmation, payment_destination/reliability/public-materials/payment-instruction-change-pack.jsonEscalate to qualified human review when required inputs are missing, source confidence is unresolved, payment or transfer risk is present, or the user asks for approval, clearance, execution, suitability, or compliance guarantees.

macro_release_context_interpretationmacro_release_context_pack_agent_workflow
macro_release_context, source_links, intended_use_context/reliability/public-materials/macro-release-context-pack.jsonEscalate to qualified human review when required inputs are missing, source confidence is unresolved, payment or transfer risk is present, or the user asks for approval, clearance, execution, suitability, or compliance guarantees.

public_company_filing_reviewpublic_company_filing_pack_agent_workflow
filing_identifier, filing_fact_reference, source_links, intended_use_context/reliability/public-materials/public-company-filing-pack.jsonEscalate to qualified human review when required inputs are missing, source confidence is unresolved, payment or transfer risk is present, or the user asks for approval, clearance, execution, suitability, or compliance guarantees.

financial_claim_publication_reviewclaim_safety_pack_agent_workflow
claim_text, source_links, claim_category, claim_evidence, limitation_language/reliability/public-materials/claim-safety-pack.jsonEscalate to qualified human review when required inputs are missing, source confidence is unresolved, payment or transfer risk is present, or the user asks for approval, clearance, execution, suitability, or compliance guarantees.

Service-linked public material paths

Each core service now maps to a concrete public scenario path

This keeps the machine story explicit: start with the right reliability service, then follow the linked public material pack page and JSON artifact when the task is already concrete.

ServiceService pageLinked packs

Action Preflight/agent-verification/action-preflightcrypto_signal_subscription_pack (Crypto signal subscription before payment) / counterparty_screening_pack (Counterparty screening before payment) / wallet_transfer_unverified_counterparty_pack (Wallet transfer to unverified counterparty) / payment_instruction_change_pack (Payment instruction change before settlement)

Evidence Cards/agent-verification/evidence-cardsmacro_release_context_pack (Macro release context packaging) / public_company_filing_pack (Public company filing review)

Reliability Corpus/agent-verification/reliability-corpusclaim_safety_pack (Claim-safety review before publication)

Start with the strongest public packs before the broader catalog

Start here first: Counterparty screening before payment (counterparty_screening_pack) - Start here first when an agent is close to moving money, accepting new payment instructions, or acting on weak counterparty evidence.

Start here next: Claim-safety review before publication (claim_safety_pack) - Start here next when an agent is about to restate evidence, strategy language, or marketing claims in public-facing form.

Start here first: Crypto signal subscription before payment (crypto_signal_subscription_pack) - Start here first when an agent is asked to pay in crypto, trust guaranteed-return language, or connect a brokerage account for auto-trading access.

Start here next: Wallet transfer to unverified counterparty (wallet_transfer_unverified_counterparty_pack) - Start here next when a high-risk crypto wallet transfer points to a new counterparty and the destination remains irreversible, weakly verified, or private-group only.

Start here next: Payment instruction change before settlement (payment_instruction_change_pack) - Start here first when a beneficiary, bank account, or wallet destination changes shortly before payment and the instruction arrives through a weak or unverified channel.

Browse full catalog: Public Materials - Use this when the task is still broad or ambiguous and the agent needs the full static scenario catalog before choosing one pack.

Trust summary boundary

Public trust summaries expose a narrow field whitelist only.

Do not treat trust summaries as rankings, investment advice, live trading signals, or completed formal backtest proof.

Public trust-summary fields: summary_id, visibility, evidence_level, review_status, tested_market_scope, tested_assets, tested_time_window, safe_statements, limitations.

Internal evaluation IDs, operator notes, blocked claims, evidence refs, raw evaluation history, private evidence lineage, rankings, and performance-winner claims remain internal.

V8 boundary notes

V8 remains a support layer for existing delivery and evidence workflows.

No standalone paid trust-summary product is enabled.

Public trust summaries are not rankings or marketplace listings.

Public multi-runner comparison is not enabled.

LEAN remains local-only and is not production-scope approved.

Runner comparisons require matching data provenance, evidence contracts, and cost assumptions.

Named public examples

Sample cases, sample packages, and review collections

The reliability layer now exposes named public examples so machines can cite a concrete sample line instead of only a generic service description.

Discovery hint

Action Preflight sample cases

crypto_signal_subscription, cross_border_supplier_payment, wallet_transfer_unverified_counterparty, payment_instruction_change_request show how high-risk action checks are published as static examples.

Discovery hint

Evidence Card sample packages

counterparty_screening_vendor_payment, macro_release_context_inflation, public_company_filing_event, claim_safety_publication_review show how static evidence packs can be grouped by review task.

Discovery hint

Reliability Corpus collections

backtest_assumption_audit, runner_difference_review, claim_safety_review show how review collections can bundle related failure patterns.

Discovery hint

Public Material packs

crypto_signal_subscription_pack, counterparty_screening_pack, wallet_transfer_unverified_counterparty_pack, payment_instruction_change_pack, macro_release_context_pack, public_company_filing_pack, claim_safety_pack show how the reliability layer maps to concrete tasks.

Pack guidance

Pack-level review hints for agents and crawlers

The strongest public material packs now publish reviewChecklist, escalationTriggers, safeStatements, blockedStatements, sample evidence cards, source manifests, and canonical citations directly in the shared contract model.

PackReview focusEscalate whenSafe statementBlocked claimCitation handoff

crypto_signal_subscription_packRecord the exact pitch, guaranteed-return wording, automation claim, payment route, and subscription deadline before summarizing the offer.The offer promises guaranteed returns, low-risk certainty, or safety without evidence that can support those claims.The reviewed offer includes guaranteed-return and account-access risk signals that keep the action blocked pending human review.This crypto signal group is safe.Sample evidence card crypto_signal_subscription_pack_sample_evidence_card; Source manifest 6 sources, latest snapshot 2026-05-25T00:00:00.000ZCanonical citation: Crypto signal subscription before payment, public-material-crypto-signal-subscription-pack-2026-05-25, generated 2026-05-25T00:00:00.000Z, source snapshot 2026-05-25T00:00:00.000Z, https://trading4ai.com/agent-verification/materials/crypto-signal-subscription-packPage: https://trading4ai.com/agent-verification/materials/crypto-signal-subscription-packJSON: https://trading4ai.com/reliability/public-materials/crypto-signal-subscription-pack.json

counterparty_screening_packVerify the counterparty name, beneficiary, or wallet label against an official source you can cite.Payment instructions changed in a private chat, forwarded message, or new email domain.Checked selected public sources at the stated retrieval time; no clearance decision was established by this pack alone.This counterparty is safe.Sample evidence card counterparty_screening_pack_sample_evidence_card; Source manifest 8 sources, latest snapshot 2026-05-25T00:00:00.000ZCanonical citation: Counterparty screening before payment, public-material-counterparty-screening-pack-2026-05-25, generated 2026-05-25T00:00:00.000Z, source snapshot 2026-05-25T00:00:00.000Z, https://trading4ai.com/agent-verification/materials/counterparty-screening-packPage: https://trading4ai.com/agent-verification/materials/counterparty-screening-packJSON: https://trading4ai.com/reliability/public-materials/counterparty-screening-pack.json

wallet_transfer_unverified_counterparty_packVerify whether the wallet address, chain/network, address checksum, destination memo/tag, and beneficiary label can be matched to a source you can cite rather than a private chat message or alias only.The wallet destination is supplied only through a private group, forwarded message, or weak side channel.The wallet transfer remains blocked because the current evidence does not independently verify the counterparty or the destination address owner.This wallet transfer is safe.Sample evidence card wallet_transfer_unverified_counterparty_pack_sample_evidence_card; Source manifest 7 sources, latest snapshot 2026-05-25T00:00:00.000ZCanonical citation: Wallet transfer to unverified counterparty, public-material-wallet-transfer-unverified-counterparty-pack-2026-05-25, generated 2026-05-25T00:00:00.000Z, source snapshot 2026-05-25T00:00:00.000Z, https://trading4ai.com/agent-verification/materials/wallet-transfer-unverified-counterparty-packPage: https://trading4ai.com/agent-verification/materials/wallet-transfer-unverified-counterparty-packJSON: https://trading4ai.com/reliability/public-materials/wallet-transfer-unverified-counterparty-pack.json

payment_instruction_change_packCompare the new beneficiary, bank account, or wallet destination against the previously verified vendor record or invoice file.The beneficiary, bank account, or wallet destination changes shortly before settlement.The payment-change request is still blocked because the new destination has not been independently matched to the known supplier record.The new payment instruction is safe.Sample evidence card payment_instruction_change_pack_sample_evidence_card; Source manifest 5 sources, latest snapshot 2026-05-25T00:00:00.000ZCanonical citation: Payment instruction change before settlement, public-material-payment-instruction-change-pack-2026-05-25, generated 2026-05-25T00:00:00.000Z, source snapshot 2026-05-25T00:00:00.000Z, https://trading4ai.com/agent-verification/materials/payment-instruction-change-packPage: https://trading4ai.com/agent-verification/materials/payment-instruction-change-packJSON: https://trading4ai.com/reliability/public-materials/payment-instruction-change-pack.json

macro_release_context_packConfirm the release name, series_id, observation date, reported value, and cited release field before summarizing.A single release is being used to justify a strong market-direction claim.The cited release reported the stated value at the observed time.This release proves the next market move.Sample evidence card macro_release_context_pack_sample_evidence_card; Source manifest 6 sources, latest snapshot 2026-05-25T00:00:00.000ZCanonical citation: Macro release context packaging, public-material-macro-release-context-pack-2026-05-25, generated 2026-05-25T00:00:00.000Z, source snapshot 2026-05-25T00:00:00.000Z, https://trading4ai.com/agent-verification/materials/macro-release-context-packPage: https://trading4ai.com/agent-verification/materials/macro-release-context-packJSON: https://trading4ai.com/reliability/public-materials/macro-release-context-pack.json

public_company_filing_packIdentify the issuer name, CIK, form type, filing date, accession number, and primary document before summarizing.The summary upgrades a filing event into a price target or investment conclusion.The filing states the cited event or disclosure in the referenced source set.This filing proves the stock will rise.Sample evidence card public_company_filing_pack_sample_evidence_card; Source manifest 4 sources, latest snapshot 2026-05-25T00:00:00.000ZCanonical citation: Public company filing review, public-material-public-company-filing-pack-2026-05-25, generated 2026-05-25T00:00:00.000Z, source snapshot 2026-05-25T00:00:00.000Z, https://trading4ai.com/agent-verification/materials/public-company-filing-packPage: https://trading4ai.com/agent-verification/materials/public-company-filing-packJSON: https://trading4ai.com/reliability/public-materials/public-company-filing-pack.json

claim_safety_packClassify the claim category, preserve the exact wording, and compare it against the source scope before repeating it.The statement promises returns, low risk, safety, or suitability.The evidence supports a bounded observation with stated limitations and retrieval time.This strategy is verified and safe for users.Sample evidence card claim_safety_pack_sample_evidence_card; Source manifest 6 sources, latest snapshot 2026-05-25T00:00:00.000ZCanonical citation: Claim-safety review before publication, public-material-claim-safety-pack-2026-05-25, generated 2026-05-25T00:00:00.000Z, source snapshot 2026-05-25T00:00:00.000Z, https://trading4ai.com/agent-verification/materials/claim-safety-packPage: https://trading4ai.com/agent-verification/materials/claim-safety-packJSON: https://trading4ai.com/reliability/public-materials/claim-safety-pack.json

Secondary discovery

These public surfaces are supporting references, not the main product line

Start with the Reliability Layer first. Strategy pages and older runtime-facing files can still help with context, but they are secondary supporting surfaces in this phase.

Supporting surface

Legacy strategy catalog

These pages remain crawlable for historical context and product discovery, but they are not the recommended starting point for today's Reliability Layer story.

Supporting surface

Legacy OpenAPI snapshot

openapi.json is still useful for legacy runtime snapshot context, but it should not be read as the primary public entry to the current Pages-only reliability offering.

FAQ

Common questions about the public machine-facing layer

Question

How should a machine start reading the public reliability layer?

Start at /agent-verification to understand the current product line, then move to the matching service page and linked public material pack before using any JSON artifact as machine-readable guidance.

Question

When should an agent open a scenario pack instead of stopping at a service page?

Open the linked scenario pack when the task is already concrete, such as screening a payment counterparty, reviewing an irreversible wallet transfer, confirming a payment instruction change before settlement, packaging filing evidence, or reviewing a public financial claim before publication.