TRADING4AISecondary raw example category for crawlers, agents, and integration builders

Secondary delivery raw examples

Raw delivery-shape entry points kept as supporting reference material.

Use this page when you want the raw delivery-side discovery layer for older public delivery-shape examples. The current primary public surface is /agent-verification/materials.

Secondary raw example category. Current reliability materials live at /agent-verification/materials.

How to use this page

Use the JSON catalog when a machine needs compact delivery-shape discovery.

Use the Markdown guide when a crawler or LLM wants plain-text context about the older sample shape.

Use the raw JSON sample when exact public delivery-shape structure is needed. Current reliability materials should come first for new agent-facing work.

Boundary

Everything linked from this page is public and safe for retrieval as supporting reference material.

These examples document older delivery shape and access-boundary vocabulary.

Current reliability materials are published as static Pages-only artifacts.

Entry points

Category-level raw discovery links

Start here

Which reader should start with which surface?

Machine checklist

Rules for using this raw category without confusing it 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.

Files

Raw entries, package guides, and related HTML sample pages

Raw entryContext
/examples/delivery/quant-lab-standard.json/samples/delivery/quant-lab-standard | Quant Lab Standard Delivery Sample | GET /api/v1/delivery/bundles/{product_slug}/{bundle_version}

Suggested flow

Recommended reading paths for this raw category

FAQ

Common questions about this raw category

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.