TRADING4AISecondary raw examples archive and machine-readable sample catalog

Secondary raw examples archive

Machine-first access to older raw public sample files.

The current primary public surface is the Pages-only reliability layer. Use this page when you want the direct JSON or package-file side of the older public sample namespace, then start current agent-facing research with the reliability materials and their downloadable JSON artifacts.

How to use this namespace

Fetch /examples/index.json when a machine needs a stable catalog of the public samples.

Use /examples/README.md when plain-text retrieval is easier than parsing HTML or a JSON catalog.

Use /artifact-samples/README.md when you need the artifact package-file namespace itself, rather than the wider artifact discovery layer.

Use /samples when you want the crawl-friendly HTML explanation layer.

Use the direct raw file links below when you want the JSON or artifact sample files themselves.

Use /agent-verification/materials as the current reliability-material starting point.

Boundary

Everything linked from this page is public and 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 raw examples remain secondary reference material, not the active product surface.

Catalog

Stable discovery entry points

Entry selector

Start with the surface that matches your reader

Machine checklist

How agents should use this namespace

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 flows

Recommended reading paths mirrored from the machine catalog

FAQ

Plain-language rules for using public examples safely

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.

Artifact Samples

Public artifact package samples with HTML landing pages and raw sample files.

Quant Lab Samples

Secondary Quant Lab request, status, and budget-confirm payload examples.

Delivery Samples

Public delivery-shape examples that explain bundle structure and access boundaries.

Direct raw files

Public files and package guides that machines can fetch without parsing the HTML pages