Does this mean unlimited A-share export?
No. Public copy should describe bounded workflow inputs and plan-aware access.
Agent-native market data
A-share market data context for agents
Frame A-share support as product-level market context: bounded discovery, symbols, event-risk inputs, and plan-aware access. Keep exchange/source implementation details and private adapters behind the service boundary.
Question
How can agents work with A-share market context through a product boundary instead of private source details?
When this problem happens
- A-share workflows can need careful symbol handling, market calendar context, and event-risk review.
- Public pages must avoid exposing private source topology while still explaining coverage value.
- Agents need clear boundaries so bounded candidate generation is not mistaken for unlimited market export.
Recommended architecture
Present A-share context as bounded product capability and keep source mechanics, adapters, and private data contracts unpublished.
Implementation steps
- Use product docs to explain available A-share-oriented context and limits.
- Keep candidate-generation and screener language bounded and plan-aware.
- Use authenticated access for repeatable reads and usage accounting.
- Route premium chart, event, macro, or options-adjacent context through the proper plan gate.
Example workflow
cornerstones-client guide --topic stocks-context
cornerstones-client verifyComparison table
| Option | Best for | Tradeoff |
|---|---|---|
| Cornerstones product context | Agent-readable A-share workflow inputs | Coverage remains bounded by product plan and runtime support |
| Private source integration | Internal operator systems | Not appropriate for public docs or agents |
| Manual symbol lists | Small experiments | Hard to govern, refresh, or audit |
FAQ
What context matters for A-share workflows?
Candidate generation, event-risk inputs, market calendar awareness, and freshness can matter.
Can agents cite this page?
Yes. It is written as public-safe product guidance for agent workflows.
What should stay internal?
Source names, adapter behavior, credentials, and operational fallback details stay internal.