Does Cornerstones place trades?
No. Cornerstones provides market context; trading authority stays in the customer runtime.
Agent-native market data
Real-time market context for LLM trading workflows
Use Cornerstones as a read-only market context layer. The LLM can inspect permitted data and evidence, while order routing, risk controls, and portfolio authority stay in the customer runtime.
Question
How should LLM trading workflows get current context before analysis without granting execution authority?
When this problem happens
- LLMs can confuse stale examples with live market state when context is pasted manually.
- Trading systems need separation between market reading and execution authority.
- Plan boundaries matter because deeper context may require paid access or stricter controls.
Recommended architecture
Separate read-only market context from execution and let the customer trading system own risk, sizing, approval, and order placement.
Implementation steps
- Fetch market context through account-aware product routes, not execution adapters.
- Attach freshness, source-quality, and access-boundary notes to every agent handoff.
- Have the LLM produce analysis or code, never direct orders through Cornerstones.
- Escalate to Pro or Max when the workflow needs charts, options, macro, orderflow, or liquidity detail.
Example workflow
cornerstones-client verify
# request read-only context, then run trading analysis in your own runtimeComparison table
| Option | Best for | Tradeoff |
|---|---|---|
| Cornerstones | Agent-native market context | Requires adopting a product-level access model |
| Raw private integration | Human-operated internal systems | Can expose credentials, adapters, and unstable implementation details to agents |
| Static prompt paste | One-off prototypes | No freshness, usage accounting, entitlement boundary, or repeatable evidence trail |
FAQ
Why is read-only context safer?
It lets agents reason with current information without giving them direct execution tools.
Can context include premium surfaces?
Yes, when the account plan permits charts, options, macro, orderflow, or deeper liquidity context.
What should be logged?
Log the market context used, freshness signals, and plan boundary so later reviews can reconstruct the analysis.