Is every market category a leak?
No. Categories like options, macro, charts, orderflow, and liquidity are product capabilities, not private source names.
Agent-native market data
Provider leakage in market data products
Provider leakage is the accidental publication of backend source names, credentials, routes, or operational assumptions. It weakens commercial flexibility and teaches agents to depend on private implementation details.
Question
What is provider leakage, and why does it matter for agent-facing market data products?
When this problem happens
- Search pages need specificity, but source names are the wrong kind of specificity.
- Agents may preserve leaked implementation names in generated code and future prompts.
- Public packages and docs can drift from internal runbooks unless tests enforce the boundary.
Recommended architecture
Use capability-level public language and automated leakage checks, while keeping source-specific details in private operations documentation.
Implementation steps
- Define public-safe market surface names before writing SEO copy.
- Scan public content for banned provider and adapter terms before every release.
- Move source-specific notes into private operator docs with restricted access.
- Teach agents to cite product routes, plan gates, and user-facing docs instead of internal sources.
Example workflow
npm test -- tests/geo-seo-foundation.test.mjs
# fail if public SEO content leaks private source termsComparison table
| Option | Best for | Tradeoff |
|---|---|---|
| Capability wording | Public SEO, docs, packages, and agent prompts | Requires disciplined naming |
| Source wording | Private operator diagnostics | Unsafe for public indexing |
| No technical detail | Fast launch copy | Thin content that agents and answer engines cannot use |
FAQ
Why do agents make leakage worse?
They can copy leaked implementation names into code, docs, and future prompts at high speed.
How should leakage be prevented?
Use public-safe content models, automated tests, and review checklists before publishing.
Can private docs mention sources?
Yes, if access is restricted and those docs are not linked from public client or website surfaces.