Three ways to work with a Public account
NexusTrade stores a portfolio as explicit conditions and trading actions. Aurora can research a company, create the rules and submit historical backtests. A separate paper deployment records simulated behavior going forward. Python and TypeScript SDKs and MCP tools expose the same account workflow.
Public describes native Agents that propose a workflow from a prompt, require activation approval and retain activity and transaction records. Its public page says some illustrated capabilities are not yet available. Public MCP is separate: it lets an external AI client access the account and place orders.
NexusTrade also has a direct Public brokerage integration. You can author and test a portfolio in NexusTrade, connect the Public account and select it for the live portfolio. Native Public Agents and a NexusTrade deployment are separate workflows.
Compare the working model
| Rule authoring | Saved indicators, conditions and actions | Native Public Agent workflow proposed from a prompt |
| Validation | Historical backtests and separate paper deployments | Review proposed workflows and trade scenarios; check account feature availability |
| Broker access | Direct Public account connection in NexusTrade | Native Public account or external Public MCP |
| Audit trail | Saved configuration, results and deployed portfolio history | Native activity feed and transaction ledger |
No matching rows. Clear the filter to see all records.
Use the direct Public connection in NexusTrade
Open Live Trading in NexusTrade, select Public and complete the connection flow for your account. Confirm the account and buying power before selecting it for a live portfolio. Test the rules in paper trading and inspect proposed order sizing first.
The implementation supports stocks, crypto and options, including multi-leg options, subject to account approval. Broker permissions and asset availability still determine which orders can be accepted.
Use Public MCP when you want an external client
Public documents a separate remote server at https://mcp.public.com/mcp with browser authorization. Use the Public setup instructions for your client. Authorizing that connector can permit account reads and orders; it does not create a NexusTrade portfolio or make Public responsible for the external agent.
Who each route may suit
Choose native Public Agents if you prefer authoring and reviewing automation inside the brokerage account. Check whether the workflow you need is available rather than relying on an illustrated example.
Choose NexusTrade when you want a research and testing workspace with explicit saved rules, then a direct Public connection for execution. Choose Public MCP when you want your existing external assistant to interact directly with Public.
Costs, account eligibility and comparison scope
Check the current subscription, compute charges, brokerage fees, supported country and account permissions for the workflow you intend to use. A platform capability does not establish that your account can trade a particular instrument.
This comparison describes workflows checked October 10, 2026. We have not run matched strategies or live accounts across the products, so it contains no ranking of returns, fill quality or execution speed.