Agent-native market data

Account-aware access for market data agents

Account-aware access lets an agent know what it can read, how much quota remains, and when a workflow needs a higher plan. That is safer than anonymous unlimited probing or private shared keys.

Open dashboard Docs

Question

Why should market-data agents use account-aware access instead of anonymous unlimited reads?

When this problem happens

Agents need to distinguish public discovery from authenticated and premium market reads.
Teams need usage counters before automation loops scale request volume.
Upgrade paths should be visible without exposing private source infrastructure.

Recommended architecture

Separate narrow public discovery from dashboard-issued account access, then expose plan and usage state in surfaces agents can read.

Implementation steps

Use public discovery for first-touch orientation only.
Issue dashboard-backed access for durable market reads and quota tracking.
Show plan and remaining usage in agent-readable dashboard or API responses.
Require Pro or Max for premium context bundles and deeper liquidity/orderflow surfaces.

Example workflow

cornerstones-client auth login --api-key "$CORNERSTONES_API_KEY"
cornerstones-client auth status
cornerstones-client verify

Comparison table

Option	Best for	Tradeoff
Account-aware access	Repeatable agent workflows with quota and revocation	Requires login or key issuance
Anonymous discovery	First-touch product understanding	Must stay narrow and low-risk
Shared private key	Legacy internal scripts	Poor attribution and high leakage risk

FAQ

Why not make every route public?

Public discovery should be narrow so premium data, status, usage, and account state stay protected.

How does the agent know it hit a plan gate?

Responses and docs should point to the access matrix and upgrade path rather than failing ambiguously.

Can account access be revoked?

Yes. Product-level keys are revocable without rotating private upstream credentials.