HTR Invest
Settings
These words are not operations HTR can perform, and that is enforced by the build rather than by care:
achdepositmove_fundspayouttransferwirewithdraw
HTR never stores a brokerage password. The table that records a connection has no column for one: it keeps a masked account number and a handle into a separate secret store, never the secret itself.
No brokerage is connected, and HTR has no live brokerage integration to connect to. The only custodian today is a simulated paper broker, which holds no money and places no real order. The table below is what a connection WOULD grant, published before anyone is asked to grant it.
Every operation the interface defines, what it would let HTR do, and whether today's simulated broker implements it. The three that can move securities are listed first.
| Permission | What it allows | Kind | Simulated broker |
|---|---|---|---|
cancel_order |
Cancel an order HTR placed. | Can place or change an order | Supported |
replace_order |
Change the price or size of a working order. | Can place or change an order | Not supported — Cancel-and-resubmit is the honest shape for a simulator. Pretending to replace would hide that the order id changed. |
submit_order |
Place an order to buy or sell. | Can place or change an order | Supported |
connect |
Link your brokerage account to HTR. | Read only | Supported |
disconnect |
Unlink it, after which HTR has no further access. | Read only | Supported |
get_account |
Read the account's identity and status. | Read only | Supported |
get_balances |
Read cash and equity balances. | Read only | Supported |
get_buying_power |
Read how much could be deployed. | Read only | Supported |
get_market_status |
Read whether the market is open. | Read only | Supported |
get_order_status |
Read whether one order filled. | Read only | Supported |
get_orders |
Read the account's orders. | Read only | Supported |
get_portfolio_history |
Read the account's value over time. | Read only | Not supported — A simulator that invented a history would be fabricating the one series that must be built from daily snapshots and cash flows. Callers are refused and use HTR's own snapshots instead. |
get_positions |
Read what the account holds. | Read only | Supported |
Provider paper, valid in
DEMO and PAPER mode. A provider is bound to one
mode at construction, so a figure from a simulated account can never be
presented as a live one.
The design for this screen includes these. They are not shown as controls, because a setting that does not save is worse than an absent one — each reason is stated rather than left to be discovered.
| Setting | Would do | Why not |
|---|---|---|
| Change risk controls | Position size, daily loss cap, how many positions at once | Not editable from the web, deliberately. Risk gates must never be loosened to produce more trades, and the design puts these writes behind two-factor authentication, which does not exist yet. Offering them unprotected is the worse of the two. |
| Two-factor authentication | A second factor on sign-in and on risk changes | Not built. It is what the risk-control writes above are supposed to sit behind, so it comes first. |
| Active sessions and sign-out everywhere | See where you are signed in and end other sessions | Not built. There is no session list and no idle timeout. |
| Per-alert notification preferences | Choose which alerts reach you and how | Partly built: you can subscribe and unsubscribe, but there is no per-alert choice behind it, so none is shown. |
| What HTR charges | A monthly price and an annual rate | No rate is set. The design shows both as placeholders, so there is no price to publish and inventing one would be worse than the blank. |
| Terms, Privacy and Disclosures | The documents themselves | Not published. The screening methodology is the one document that exists, and it is linked below. |
- Stop or resume HTR — the whole-account kill switch, with the record of every time it was used.
- How screening works — the seven standards, and what each verdict means.
Notification subscribe and unsubscribe exist as endpoints but have no settings screen behind them yet, which is why they are listed above as not built rather than linked here.
Paper and backtest results are hypothetical and do not represent actual trading. Past performance does not guarantee future results. Shariah screens and purification/Zakat figures are calculation aids, not religious rulings.