TRADING4AISecondary Quant Lab sample archive for agents and crawlers

Secondary Quant Lab sample archive

Static request and status examples kept as supporting reference material.

These pages preserve readable request, status, and budget-confirm examples from an older Quant Lab shape. Current reliability materials are the active public product surface; use these examples only when static payload references help crawlers, LLMs, or integration builders understand historical sample structure.

Open raw landingOpen JSON catalogOpen Markdown guideOpen raw examples hubOpen top-level JSON catalogOpen top-level Markdown guideOpen /llms bridge

What belongs here

Request-create examples for template-constrained intake.

Status response examples that explain request_urls, next_actions, and execution_outcome.

Budget-confirm examples that show an older quoted-to-queued state shape without creating executable work.

Why this matters

LLMs and agents need stable public examples that explain older static payload references.

HTML sample pages improve readability and crawlability compared with raw JSON alone.

Current reliability materials should come first for new agent-facing work.

Entries

Secondary Quant Lab public 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.

Machine access

Stable machine-readable entry points for quant lab samples

EntryPurpose
/agent-verification/materialsCurrent Financial Agent Reliability Materials entry point before opening secondary sample archives/samples/quant-labQuant Lab Samples HTML landing page with crawl-friendly explanations and internal links/examples/quant-labQuant Lab Samples raw category landing page inside the /examples namespace/examples/quant-lab/index.jsonQuant Lab Samples JSON catalog for direct machine discovery and raw-file lookup/examples/quant-lab/README.mdQuant Lab Samples Markdown guide for plain-text LLM retrieval and summarization/samplesTop-level HTML sample hub when a crawler needs the wider public sample namespace/examplesTop-level raw example hub when an agent wants the direct /examples namespace/examples/index.jsonTop-level JSON catalog when an agent needs all categories in one compact index/examples/README.mdTop-level Markdown guide when a plain-text crawler wants the full public sample index/artifact-samples/README.mdTop-level raw package directory guide when a machine needs artifact package-file browsing

Bridge and contract

Core machine links around this category

EntryPurpose
/agent-verification/materialsCurrent Financial Agent Reliability Materials entry point./llmsMachine bridge page for discovery, entry selection, and access boundaries./llms.txtCompact plain-text discovery layer for crawlers, LLMs, and agents./artifact-samples/README.mdPlain-text raw package directory guide for the artifact sample-file namespace./openapi.jsonLegacy runtime snapshot for historical integration context./.well-known/agent.jsonAgent entry point index./for-agentsHuman-readable integration guide for the machine surface./humanCurrent reliability overview for humans.

Start here

Which reader should start with which surface?

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 reading this category without confusing public samples 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.

Suggested flow

Recommended reading order for this public surface

FAQ

Rules that help machines read these samples correctly

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.