# TRADING4AI Public Examples Guide

This directory contains public, indexable sample assets for TRADING4AI.

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

Use this guide when a crawler, LLM, agent, or integration operator needs a plain-text overview of the public sample layer without parsing the full website UI.

## Primary Entry Points

- Current reliability materials: https://trading4ai.com/agent-verification/materials
- Evidence Card Library: https://trading4ai.com/agent-verification/evidence-cards/library
- Machine bridge: https://trading4ai.com/llms
- Agent entry point: https://trading4ai.com/.well-known/agent.json
- Integration guide: https://trading4ai.com/for-agents
- Plain-text discovery file: https://trading4ai.com/llms.txt
- HTML sample hub: https://trading4ai.com/samples
- Raw example hub: https://trading4ai.com/examples
- Machine-readable sample catalog: https://trading4ai.com/examples/index.json
- Artifact raw package guide: https://trading4ai.com/artifact-samples/README.md
- Legacy runtime snapshot: https://trading4ai.com/openapi.json

## Category Entry Points

Artifact samples:

- HTML landing page: https://trading4ai.com/samples/artifacts
- Raw landing page: https://trading4ai.com/examples/artifacts
- JSON catalog: https://trading4ai.com/examples/artifacts/index.json
- Markdown guide: https://trading4ai.com/examples/artifacts/README.md
- Raw package guide: https://trading4ai.com/artifact-samples/README.md

Quant Lab samples:

- HTML landing page: https://trading4ai.com/samples/quant-lab
- Raw landing page: https://trading4ai.com/examples/quant-lab
- JSON catalog: https://trading4ai.com/examples/quant-lab/index.json
- Markdown guide: https://trading4ai.com/examples/quant-lab/README.md

Delivery samples:

- HTML landing page: https://trading4ai.com/samples/delivery
- Raw landing page: https://trading4ai.com/examples/delivery
- JSON catalog: https://trading4ai.com/examples/delivery/index.json
- Markdown guide: https://trading4ai.com/examples/delivery/README.md

## Which Entry Should You Start With?

- Current agent-facing work: start with /agent-verification/materials.
- Crawler or search engine: start with /samples when sample archives are needed, because it provides crawlable HTML, internal links, and structured data.
- LLM or agent needing compact sample discovery: start with /examples/index.json.
- LLM needing plain text sample context: start with /examples/README.md.
- Machine needing artifact package browsing: start with /artifact-samples/README.md.
- Tool caller needing entry-point discovery: start with /.well-known/agent.json, then use /llms.txt and /for-agents for static discovery and access-boundary guidance.
- Human reader: start with /human for a human-readable reliability overview.

Start current agent-facing work with /agent-verification/materials, then use /llms.txt and /.well-known/agent.json for static discovery.

## Recommended Reading Paths

### Current Reliability Materials

1. Start with https://trading4ai.com/agent-verification/materials
2. Open the relevant public material pack.
3. Use https://trading4ai.com/agent-verification/evidence-cards/library when a compact Evidence Card index is needed.
4. Use https://trading4ai.com/llms.txt for compact plain-text discovery.
5. Use https://trading4ai.com/.well-known/agent.json for machine-readable entry-point metadata.

### Quant Lab Sample Archive

1. Start with https://trading4ai.com/agent-verification/materials
2. Read https://trading4ai.com/samples
3. Read https://trading4ai.com/samples/quant-lab
4. Inspect https://trading4ai.com/samples/quant-lab/request-create
5. Inspect https://trading4ai.com/samples/quant-lab/request-status
6. Inspect https://trading4ai.com/samples/quant-lab/budget-confirm
7. Fetch https://trading4ai.com/examples/quant-lab/index.json for direct raw-file discovery

### Artifact And Delivery Sample Archive

1. Start with https://trading4ai.com/agent-verification/materials
2. Read https://trading4ai.com/samples
3. Read https://trading4ai.com/samples/artifacts
4. Inspect https://trading4ai.com/samples/artifacts/eth-breakout-playbook
5. Fetch https://trading4ai.com/artifact-samples/README.md when you want the raw artifact package directory guide
6. Inspect https://trading4ai.com/samples/delivery/quant-lab-standard
7. Fetch https://trading4ai.com/examples for raw public example links

## Public Raw Files

Quant Lab examples:

- /examples/quant-lab/index.json
- /examples/quant-lab/README.md
- /examples/quant-lab/request-create.json
- /examples/quant-lab/request-status.json
- /examples/quant-lab/budget-confirm.json

Delivery examples:

- /examples/delivery/index.json
- /examples/delivery/README.md
- /examples/delivery/quant-lab-standard.json

Artifact package samples:

- /examples/artifacts/index.json
- /examples/artifacts/README.md
- /artifact-samples/README.md
- /artifact-samples/eth-breakout-playbook/manifest.json
- /artifact-samples/eth-breakout-playbook/README.md
- /artifact-samples/eth-breakout-playbook/examples.json
- /artifact-samples/eth-breakout-playbook/reference_strategy.py
- /artifact-samples/btc-trap-playbook/manifest.json
- /artifact-samples/btc-trap-playbook/README.md
- /artifact-samples/btc-trap-playbook/examples.json
- /artifact-samples/btc-trap-playbook/reference_strategy.py

## Current Reliability And Sample Boundary

Everything linked from this guide is public and safe for indexing.

These files explain sample request shapes, response shapes, artifact package structure, and delivery boundaries. They are supporting examples, not the current product surface.

Do not use these sample archives as proof of live orders, current delivery, paid access, or request-time API execution.

Use /openapi.json only when intentionally reviewing the legacy runtime snapshot. Use /agent-verification/materials first for the current Pages-only reliability materials.

## FAQ

### Are public samples the same as current reliability materials?

No. Public samples are safe, indexable supporting references. Current reliability materials live under /agent-verification/materials and are the active public product surface.

### 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.

### Should the raw JSON files replace the reliability artifacts?

No. Public example JSON files are secondary samples. Current reliability artifacts live under /reliability/*.json and /reliability/public-materials/*.json.

### Do these samples create jobs, orders, or reviews?

No. The samples demonstrate public shape only. No live request, order, payment, entitlement, or delivery flow is implied by these public examples.

### How should a machine understand access boundaries?

Treat the public pages and raw files as documentation. They do not unlock protected files, create requests, or prove an entitlement.

## Machine Use Guidance

- Prefer /agent-verification/materials for current reliability-material discovery.
- Prefer HTML pages when you need explanatory context.
- Prefer /examples/index.json when you need a compact machine-readable catalog for secondary public samples.
- Prefer /examples/README.md when you need compact Markdown that is easy for plain-text retrieval or summarization.
- Prefer /artifact-samples/README.md when you need the raw artifact package directory guide.
- Prefer /.well-known/agent.json when a tool caller or agent needs a machine-readable entry-point index.
- Prefer /for-agents when the integration needs static surface posture, access-boundary explanation, or a human-readable walkthrough of the machine surface.
- Prefer raw JSON files when exact secondary sample payloads are needed.
- Do not infer that a public sample URL can unlock current delivery or request-time execution.

## Machine Use Checklist

- Use current materials first: read /agent-verification/materials when the task concerns current Financial Agent Reliability Materials.
- Use HTML for explanation: read /samples and its child pages when secondary sample narrative context is useful.
- Use JSON for discovery: fetch /examples/index.json when you need a compact catalog of categories, recommended paths, raw files, and entry selectors.
- Use Markdown for plain-text ingestion: fetch /examples/README.md when you need a compact text guide that is easy for LLM retrieval or summarization.
- Use agent entry points for static discovery: fetch /.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 guidance: read /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 browsing: fetch /artifact-samples/README.md when package-file browsing is needed.
- Use raw files for exact payloads: fetch /examples/quant-lab/*.json, /examples/delivery/*.json, or /artifact-samples/* files when exact public example content is needed.
- Treat samples as reference: public sample links are secondary reference material, not proof of current request-time execution or delivery.
- Use OpenAPI only for legacy runtime context: treat /openapi.json as a secondary runtime snapshot; sample files illustrate common payloads but do not replace current reliability materials.
