Can public copy mention market categories?
Yes. Market categories and product surfaces are useful; private source names and adapter details are not.
Agent-native market data
How to prevent provider leakage in public market data clients
Write public pages around customer capabilities, not infrastructure sources. Use neutral terms like charts, orderflow, options, macro, event risk, and liquidity context while keeping provider names server-side.
Question
How can a public market-data client describe powerful coverage without exposing private provider names?
When this problem happens
- Public docs can accidentally reveal backend source names and negotiation strategy.
- Client examples may teach agents to depend on implementation details that should change freely.
- Search pages need concrete market value without becoming a vendor map.
Recommended architecture
Maintain separate public product content and private operator documentation, with tests preventing banned infrastructure terms from crossing the boundary.
Implementation steps
- Create banned-term tests across public content, docs, use-case pages, and client README surfaces.
- Name data products by outcome: context, charts, options, macro, orderflow, liquidity, and event risk.
- Keep source, credential, and adapter discussions in internal operator docs only.
- Review every SEO page for public-safe language before deployment.
Example workflow
npm test -- tests/geo-seo-foundation.test.mjs
# provider-safe content must stay green before public deployComparison table
| Option | Best for | Tradeoff |
|---|---|---|
| Product-level copy | Public website, docs, and package pages | Requires careful capability wording |
| Provider-level copy | Internal operator runbooks | Leaks vendor dependency and sourcing detail if published |
| Vague copy | Avoiding leaks quickly | Too thin for search, answer engines, and agent onboarding |
FAQ
Should examples use fake provider names?
No. Examples should show Cornerstones commands and product concepts, not invented upstream integrations.
How do tests help?
They catch accidental provider terms before public pages, package docs, or sitemap-generated routes ship.
Where should source details live?
Use internal operator docs and private runbooks, not public website or client package content.