TRADING4AIRaw category-level example pages for crawlers, agents, and integration builders

Delivery raw examples

Raw delivery-shape entry points for public bundle structure.

Use this page when you want the raw delivery-side discovery layer for public fulfillment-shape examples. It links the compact delivery catalog, the Markdown guide, and the exact public delivery-shape sample files.

Open JSON catalogOpen Markdown guideOpen raw examples hubOpen top-level JSON catalogOpen top-level Markdown guideOpen /llms bridgeOpen HTML samples

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 public versus private delivery.

Use the raw JSON sample when exact public delivery-shape structure is needed.

Boundary

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

These examples document delivery shape and access boundaries, not private paid bundle retrieval.

Real private files remain behind Worker authorization, claim state, entitlement state, and access tokens.

Entry points

Category-level raw discovery links

EntryPurpose
/examples/deliveryCurrent raw category landing page with discovery guidance/examples/delivery/index.jsonDelivery Samples compact machine-readable catalog/examples/delivery/README.mdDelivery Samples plain-text Markdown guide/samples/deliveryDelivery Samples HTML explanation layer under /samples/examplesTop-level raw example hub for the full namespace/samplesTop-level HTML sample hub for category discovery across the full namespace/examples/index.jsonTop-level JSON catalog across all public sample categories/examples/README.mdTop-level Markdown guide for plain-text crawler and LLM retrieval/artifact-samples/README.mdTop-level raw package directory guide for artifact package-file namespace discovery/llms.txtCompact plain-text discovery layer for crawlers, LLMs, and agents/.well-known/agent.jsonMachine-readable agent entry point index for tools and runtime discovery/for-agentsHuman-readable integration guide for the machine surface and runtime posture/openapi.jsonCanonical runtime API contract when an integration needs the formal schema

Start here

Which reader should start with which surface?

ReaderStart withWhy
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 canonical API contract.Human operator or buyer/humanUse the human site for service positioning, pricing, order flow, and delivery expectations.

Machine checklist

Rules for using this raw category without confusing it with private delivery

RuleGuidance
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 runtime discoveryFetch /.well-known/agent.json when a tool caller or agent runtime needs the machine-readable entry-point index before choosing routes.
Use /for-agents for narrative machine guidanceRead /for-agents when the integration needs runtime 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.
Do not treat samples as entitlementsPublic sample links do not unlock private paid bundles; private delivery still requires claim, entitlement, and access-token checks.
Use OpenAPI for the contractTreat /openapi.json as the canonical API contract; sample files illustrate common payloads but do not replace the contract.

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 private paid bundles?

No. Public samples are safe, indexable examples that explain request shapes, response shapes, artifact structure, and delivery boundaries. Private paid bundles remain behind Worker authorization, claim tokens, entitlement state, and access tokens.

Question

Which entry should an LLM or agent fetch first?

Use /examples/index.json for compact machine-readable discovery. Use /examples/README.md when plain-text context is easier to ingest. Use /artifact-samples/README.md when the artifact package-file namespace itself matters. Use /samples when explanatory HTML and internal links are useful.

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

Are the raw JSON files the canonical API contract?

No. The raw JSON files are examples. The canonical API contract remains /openapi.json, 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. Real Quant Lab requests, orders, payment verification, and delivery access require the live API flow.

Question

How should a machine understand private delivery access?

Treat the public pages and raw files as documentation. Real private files require the order, claim, entitlement, and access-token flow documented in the API and /for-agents.