What authentication does the HotStoks API use?

An API key passed as a request header. Jentic stores the key encrypted in your Jentic One instance and injects it at execution time, so the raw key never enters the agent's prompt or memory.

Can I run custom SQL queries with the HotStoks API?

Yes. POST /v1/query accepts a SQL statement against the underlying market data tables. Use GET /v1/tables and GET /v1/tables/{table_name}/schema first if you need to introspect column names before composing the query.

What are the rate limits for the HotStoks API?

HotStoks applies per-key rate limits scaled to plan. Custom SQL queries count as a single request regardless of result size, so prefer one expressive query over many single-symbol calls when you can. Honor 429 responses on tight loops.

How do I fetch a real-time quote with the HotStoks API through Jentic?

Run pip install jentic, search for 'real-time stock quote', load the GET /v1/stocks/{symbol}/quote schema, and execute with the symbol parameter. Jentic adds the API key header automatically.

Can I get historical prices for a stock with the HotStoks API?

Yes. GET /v1/stocks/{symbol}/prices returns the historical price series for the requested ticker. For multi-symbol or filtered historical pulls, use POST /v1/query with a SQL statement against the prices table.

Can I limit what my agent is allowed to do with the HotStoks API?

Yes. Because you self-host Jentic One, your own rules decide which HotStoks operations and credentials the agent may use, so you add only the calls it needs to its allowed set, such as POST /v1/query for SQL screens or GET /v1/stocks/{symbol}/quote for a single quote. Every HotStoks operation is read-only equity data, so nothing here places orders or mutates account state. You can leave out endpoints like the market movers or historical prices calls if a given agent should never reach them.