TRADING4AISecondary public sample archive for crawlers, agents, and integration operators

Secondary public sample archive

Indexable sample pages kept as supporting reference material.

The current primary public surface is the Pages-only reliability layer. Use these pages when you need older public sample references, then start new agent-facing research with the current reliability materials and their downloadable JSON artifacts.

Current reliability materialsArtifact samplesQuant Lab samplesDelivery samplesOpen raw examplesOpen top-level JSON catalogOpen top-level Markdown guideOpen artifact package guideOpen /llms bridge

What belongs here

Public artifact package samples that teach file structure and expected contents.

Public Quant Lab request and status examples are older static payload references, not a callable workflow.

Public delivery-shape documentation that explains older sample structure without implying current delivery.

The current primary public surface is the Pages-only reliability layer under /agent-verification/materials.

Boundary

Everything under /samples should stay safe for citation and LLM retrieval as supporting reference material.

The active Phase 2 public site is static and Pages-only, with reliability materials as the recommended entry point.

These sample pages remain secondary reference material, not the active product surface.

Machine catalog

Current reliability materials: /agent-verification/materials

Bridge page: /llms

Agent entry point: /.well-known/agent.json

Integration guide: /for-agents

Legacy runtime contract snapshot: /openapi.json

Plain-text discovery: /llms.txt

HTML index: /samples

Raw example hub: /examples

Markdown guide: /examples/README.md

Artifact package guide: /artifact-samples/README.md

JSON catalog: /examples/index.json

Use the HTML pages for crawl-friendly explanation, the JSON catalog for direct sample discovery, and the artifact package guide when package-directory browsing matters.

New agent-facing discovery should start with Current reliability materials.

Category access

Per-category machine entry points for HTML, raw landing pages, JSON, Markdown, and package guides

CategoryHTMLRaw HTMLJSON catalogMarkdown guidePackage guide
Artifact Samples/samples/artifacts/examples/artifacts/examples/artifacts/index.json/examples/artifacts/README.md/artifact-samples/README.md
Quant Lab Samples/samples/quant-lab/examples/quant-lab/examples/quant-lab/index.json/examples/quant-lab/README.mdNone
Delivery Samples/samples/delivery/examples/delivery/examples/delivery/index.json/examples/delivery/README.mdNone

Choose an entry

Which public surface should each reader start with?

ReaderStart withWhy
Current agent-facing work/agent-verification/materialsUse the current public reliability materials before opening secondary sample archives or raw example files.Crawler or search engine/samplesUse the HTML sample hub first because it contains crawlable explanations, internal links, and structured data.LLM or agent needing compact discovery/examples/index.jsonUse the JSON catalog when the caller needs categories, recommended paths, and direct raw-file links without parsing HTML.LLM needing plain text context/examples/README.mdUse the Markdown guide when a compact plain-text explanation is easier to ingest than page markup.Machine needing artifact package browsing/artifact-samples/README.mdUse the raw package guide when the artifact package-file namespace itself matters more than the wider category overview.Agent runtime or tool caller/.well-known/agent.jsonUse the machine-readable entry-point index before choosing narrative guides or the legacy runtime snapshot.Human operator or buyer/humanUse the human site for a human-readable reliability overview and current material entry points.

Machine checklist

Rules for using public samples without confusing them with the current reliability layer

RuleGuidance
Use current materials firstRead /agent-verification/materials first when the task concerns current Financial Agent Reliability Materials rather than secondary sample archives.
Use HTML for explanationRead /samples and its child pages when you need narrative context, field explanations, internal links, and structured data.
Use JSON for discoveryFetch /examples/index.json when you need a compact catalog of categories, recommended paths, raw files, and entry selectors.
Use Markdown for plain-text ingestionFetch /examples/README.md when you need a compact text guide that is easy for LLM retrieval or summarization.
Use agent entry points for static discoveryFetch /.well-known/agent.json when a tool caller or agent needs the machine-readable entry-point index before choosing static discovery routes.
Use /for-agents for narrative machine guidanceRead /for-agents when the integration needs static surface posture, access-boundary explanation, or a human-readable walkthrough of the machine surface.
Use raw package guides for artifact directory browsingFetch /artifact-samples/README.md when you need the artifact package-file namespace itself, rather than the wider category-level discovery guide.
Use raw files for exact payloadsFetch /examples/quant-lab/*.json, /examples/delivery/*.json, or /artifact-samples/* files when you need exact public example content.
Treat samples as referencePublic sample links are secondary reference material, not proof of current request-time execution or delivery.
Use OpenAPI only for legacy runtime contextTreat /openapi.json as a legacy runtime snapshot; sample files illustrate common payloads but do not replace current reliability materials.

FAQ

Common questions for crawlers, LLMs, and integration operators

Question

Are public samples the same as current reliability materials?

No. Current reliability materials are the active public product surface. Public samples are secondary static references.

Question

Which entry should an LLM or agent fetch first?

Use /agent-verification/materials for current reliability-material discovery. Use /examples/index.json only when compact secondary sample discovery is needed.

Question

When should a machine use /artifact-samples/README.md?

Use /artifact-samples/README.md when the machine needs the artifact package-file namespace itself, rather than the wider category-level discovery layer documented under /examples/artifacts/README.md.

Question

Should the raw JSON files replace the runtime snapshot?

No. The raw JSON files are examples. /openapi.json is a Legacy runtime snapshot for historical integration context, while /llms and llms.txt provide discovery and orientation.

Question

Do these samples create real Quant Lab jobs or orders?

No. The samples demonstrate structure only. The current Phase 2 public site is a Pages-only reliability layer, not a live job, order, payment, or delivery runner.

Question

How should a machine understand the public sample boundary?

Public sample links are secondary reference material, not proof of current request-time execution or delivery. Machines should treat current reliability materials as the public product surface.

Artifacts

Public artifact package samples

EntryPurpose
/samples/artifacts/eth-breakout-playbookA paid strategy artifact with entry logic, invalidation rules, prompt-ready schema, and delivery notes./samples/artifacts/btc-trap-playbookA paid strategy artifact focused on distinguishing continuation from euphoric trap behavior.

Quant Lab

Public request and status examples

EntryPurpose
/samples/quant-lab/request-createPublic request body sample for template-constrained Quant Lab intake./samples/quant-lab/request-statusPublic response sample showing request_urls, next_actions, and budget confirmation state./samples/quant-lab/budget-confirmSecondary request and response sample for an older quoted-to-queued Quant Lab state transition.

Delivery

Public delivery-shape examples

EntryPurpose
/samples/delivery/quant-lab-standardSecondary delivery-shape sample that explains older artifact bundle structure without implying current delivery access.