Skip to content
noxstock
For agents

Agent output format

Answer templates and hard rules for agents using noxstock.

Start with the answer. Then show the smallest facts that support it, the freshness/caveats, and the calls used.

Hard rules

Use these in every noxstock agent answer:

Start with the answer.
Include freshness and as_of when relevant.
List calls/tools used.
Preserve units, signs, periods, filing dates, accessions, and unavailable reasons.
Do not invent missing fields.
Say "not available from noxstock" for unsupported data.
No investment advice, trade instruction, buy/sell/hold verdict, or execution guidance.

One-symbol brief

Answer: <short factual answer>

Current setup
- <price/performance/range facts from snapshot>
- <sector/industry or asset_type if relevant>

Valuation
- <multiples, valuation_context, yields, returns if called>

Risk/caveats
- <unsupported/degraded/stale/null/unavailable reasons>
- <filing/insider caveats if called>

Freshness
- Snapshot: <freshness>, as_of <timestamp>, market_status <status>
- Valuation: <freshness>, as_of <timestamp>
- Optional routes: <freshness/as_of/source dates>

Calls used
- <routes or tool names>

Valuation answer

Answer: <expensive / cheap / mixed / not enough context, based on returned fields>

Why
- <valuation_context anchor/position/percentile_5y/median_5y if available>
- <key multiples and yields>
- <snapshot context such as range or recent performance if relevant>

Caveats
- <missing context, unsupported ETF valuation, financial-company guardrails, stale/degraded data>

Freshness
- Snapshot: <freshness>, as_of <timestamp>, market_status <status>
- Valuation: <freshness>, as_of <timestamp>

Calls used
- snapshot, valuation

Compare answer

Answer: <one-sentence comparison, not a recommendation>

Scorecard
| Symbol | <field> | <field> | Caveat |
| --- | ---: | ---: | --- |
| <symbol> | <value> | <value> | <omitted fields or freshness note> |

Notes
- fields_requested: <fields>
- fields_omitted_by_symbol: <omissions if present>

Freshness
- Compare: <freshness>, as_of <timestamp>, market_status <status>

Calls used
- compare

SEC filing answer

Answer: <summary from filing text only>

Source
- Symbol: <symbol>
- Form: <form>
- Accession: <accession>
- Filing date: <filing_date>
- Period of report: <period_of_report>
- Section: <section>

Key points from the section
- <point from text>
- <point from text>
- <point from text>

Caveats
- <available false reason, section not available, cold EDGAR/retryable issue, symbol_status if relevant>

Freshness
- Filing/section: <freshness>, as_of <timestamp>

Calls used
- filings_list, filings_get, filings_section

Never mix news, consensus, transcripts, stock price movement, or memory into a filing-text summary.

Insider answer

Answer: <notable / quiet / not available, based on summary_90d>

90-day Form 4 summary
- Market activity: <buy_count>, <sell_count>, net_shares_market_only <signed value>, net_value_usd <signed value>, net_direction <value>
- All activity: <transactions>, net_shares_all_kinds <signed value>, kinds <transactions_by_kind>
- Notices: <summary_90d.notices if returned>

Recent transactions
- <transaction_date>: <insider_name>, <transaction_kind>, <shares>, <value_usd if available>, 10b5-1 <true/false>

Freshness
- Insider: <freshness>, as_of <timestamp>, market_status <status>

Calls used
- insider

Technical answer

Answer: <extended / neutral / weak / not enough technical context>

Technical setup
- <RSI/zone, moving-average distance, trend strength>
- <52-week distance, drawdown, volume, streak/gap context>

Caveats
- <market_status is not execution readiness>
- <degraded/null long-window fields if present>

Freshness
- Technicals: <freshness>, as_of <timestamp>, market_status <status>
- Price action: <freshness>, as_of <timestamp>, market_status <status>

Calls used
- technicals, price_action

Unsupported data wording

Use plain wording:

Not available from noxstock: analyst consensus and price targets.
Not available from noxstock for this asset type: ETF valuation multiples returned freshness "unsupported".

Do not soften missing data into guesses. Unsupported is a product state, not a prompt to improvise.