# Alt data demand signal

Use public demand proxies, search, social, app, review, traffic, news, and price reaction to monitor demand shifts.

## Agent Install Policy

Agents must get explicit user confirmation before installing a skill, writing configuration, or changing the local environment.

1. Read this guide and the manifest: https://qveris.ai/skills/qveris-alt-data-demand-signal/manifest.json
2. Explain to the user what will be installed and which QVeris API actions may be used.
3. Ask for explicit approval before running an install command or changing local configuration.
4. After approval, install the skill and run one starter prompt.

## Official GitHub Source

- Repository: https://github.com/QVerisAI/open-qveris-skills
- Skill path: qveris-alt-data-demand-signal
- Skill source: https://github.com/QVerisAI/open-qveris-skills/tree/main/qveris-alt-data-demand-signal
- Clone and inspect: `git clone https://github.com/QVerisAI/open-qveris-skills.git && cd open-qveris-skills/qveris-alt-data-demand-signal`

## Install Commands

- OpenClaw: `openclaw skills install qveris-alt-data-demand-signal`

## Starter Prompts

### Alt data demand signal
Run the alt data demand signal workflow with QVeris data.

```text
Use QVeris to find alternative data demand signals for consumer AI apps. Include data sources discovered, capabilities inspected, paid Calls used, estimated credits, evidence gaps, and risks.
```

### Watchlist scan
Run the workflow across a bounded ticker list.

```text
Use QVeris to run alt data demand signal for AAPL, NVDA, MSFT, and TSLA. Rank by evidence quality and market relevance.
```

## QVeris API Actions

- Discover `POST /search`: Find search, social, app, review, traffic, news, and quote data capabilities needed for this workflow.
- Inspect `POST /tools/by-ids`: Check coverage, parameters, freshness, latency, success signals, and billing_rule before paid calls.
- Call `POST /tools/execute`: Execute bounded QVeris calls and compose results into a traceable finance brief.

## Estimated QVeris Usage

This workflow usually needs 6-24 paid Calls after free Discover and Inspect preflight. Cost depends on provider billing, ticker count, and time window.

- Typical paid Call executions: 6-24
- Planning estimate: 6-240 credits
- Free actions: Discover, Inspect
- Paid actions: Call
- Note: Ask for explicit approval before paid Calls. Reduce tickers, windows, or source count if the estimate is above budget.

## Related Cases

- [Use FMP with QVeris](https://qveris.ai/blog/qveris-fmp-finance) - Turn structured financial data into callable agent capabilities.
- [Twelve Data market capabilities](https://qveris.ai/blog/qveris-twelve-data) - Add market data coverage for global research and screening workflows.
- [OpenClaw A-share finance assistant](https://qveris.ai/blog/openclaw-a-shares-finance-assistant) - A practical workflow for source-backed A-share monitoring.

## Human Page

https://qveris.ai/skills/qveris-alt-data-demand-signal
