TRADING4AISecondary public JSON sample for crawlers, agents, and integration operators

Secondary Quant Lab sample archive

Quant Lab Request Create Sample

Public request body sample for template-constrained Quant Lab intake.

Secondary public JSON sample. Current reliability materials live at /agent-verification/materials.

How to use this sample

API path: POST /api/v1/quant-lab/requests

Raw JSON: /examples/quant-lab/request-create.json

This page is a public HTML entry point. The raw file remains linked for direct machine retrieval.

Boundary

This is a public sample for structure discovery and explanation.

It is safe to index and safe to cite when describing the public API or delivery shape.

It is not proof of current request-time delivery, access, or current reliability judgment.

Flow

How this sample fits into the operator journey

StepWhat it means
1. Choose a templateThe caller starts from a known Quant Lab template instead of sending arbitrary execution logic.
2. Describe the strategy goalThe request should explain the market question, target asset, and expected artifact output.
3. Submit the intake requestPOST the JSON body to create a tracked request and receive a token for follow-up actions.

Field glossary

Important fields for machines and integrators

FieldMeaningMachine hint
template_idSelects the constrained Quant Lab workflow to run.Use a value from /api/v1/quant-lab/templates before creating a request.
template_parametersCarries schema-bound parameters such as asset, timeframe, or confirmation zone.Keep this object aligned with the selected template schema.
budget_capDeclares the maximum budget the operator is willing to approve.Expect later status responses to show whether budget confirmation is required.

Machine entry points

Stable discovery links around this sample

These links help a crawler or agent move between the explanation layer, the raw payload, and the compact category-level indexes.

Fetch snippets

Direct retrieval commands for machines and integration tests

Use the raw sample file for an exact public payload example, and use current reliability materials for the active public product surface.

Raw sample

curl -s https://trading4ai.com/examples/quant-lab/request-create.json

Legacy runtime snapshot

curl -s https://trading4ai.com/openapi.json

Sample payload

Machine-readable example

{
  "service_type": "custom_strategy_experiment",
  "market_scope": "crypto",
  "strategy_input_type": "natural_language",
  "delivery_type": "artifact",
  "title": "ETH breakout confirmation with BTC regime filter",
  "strategy_goal": "Evaluate whether ETH can sustain a breakout above the 2385-2400 shelf when BTC is already in a risk_on regime.",
  "input_summary": "Need a template-constrained experiment for 4h ETH breakout continuation with explicit invalidation and delivery-ready artifact output.",
  "template_id": "crypto_breakout_confirmation_v1",
  "budget_cap": 120,
  "notes": "Prefer deterministic classification plus a concise operator-facing explanation.",
  "template_parameters": {
    "primary_asset": "ETH",
    "confirmation_zone": [2385, 2400],
    "supporting_regime_filter": "btc_risk_on",
    "primary_timeframe": "4h"
  }
}

Highlights

Service typecustom_strategy_experiment
Input stylenatural_language
Delivery typeartifact
Templatecrypto_breakout_confirmation_v1

Public boundary

  • This request body is safe to publish because it is a demo intake shape, not a private customer brief.
  • The sample describes the contract and expected fields but does not create a current request-time job.
  • Use /agent-verification/materials for current reliability-material discovery.

Notes

  • This sample mirrors the public Quant Lab intake flow used by the current frontend.
  • template_parameters should stay schema-bound and should not be treated as arbitrary code execution input.
  • The public create route returns a request token that should be preserved for later status and budget actions.

FAQ

Quick rules for machines and operators

Question

Should Quant Lab Request Create Sample replace the runtime snapshot?

No. This page and the linked raw file are public examples. /openapi.json is a Legacy runtime snapshot for historical integration context.

Question

Should a machine read the HTML page, the raw JSON, or the category catalog first for Quant Lab Request Create Sample?

Use the HTML page when explanation and field guidance are useful, use the raw JSON file when exact payload structure is needed, and use the category JSON catalog when a compact machine index is the best starting point.

Question

Does Quant Lab Request Create Sample provide current request-time execution or delivery access?

No. This is a secondary public JSON sample only. It does not perform live work or prove access to any non-public file.