Should Hermes summaries include secrets?
No. Summaries should mention evidence and verification, never raw keys or private provider details.
Agent-native market data
Market data for Hermes agents
Hermes agents should use Cornerstones for read-only market context, cite the access matrix in handoffs, and keep private runtime details out of shared task summaries.
Question
How can Hermes agents use market data safely across planning, coding, review, and monitoring tasks?
When this problem happens
- Hermes tasks may span research, coding, browser QA, and remote operations in one workflow.
- Shared kanban handoffs should not expose provider names, secrets, or private topology.
- Agents need compact commands that work from fresh sessions without long setup drift.
Recommended architecture
For Hermes, Cornerstones is the market-context dependency; task routing, implementation, and execution controls remain separate.
Implementation steps
- Put Cornerstones discovery and verification commands in the worker handoff.
- Use dashboard-issued account access only when the task needs live authenticated reads.
- Separate read-only market context from any execution or trading-control task.
- Complete handoffs with plan boundary, data freshness, and verification command evidence.
Example workflow
cornerstones-client guide
cornerstones-client verify
# include market-context evidence in Hermes kanban metadataComparison 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
Can one Hermes worker use no-key discovery?
Yes. Discovery is useful before deciding whether authenticated reads are needed.
Where should plan boundaries appear?
In the task brief, docs links, and final verification notes so downstream workers inherit the same constraints.
What if a route is gated?
The worker should report the plan boundary and avoid probing private infrastructure.