Can I get account list with the Webull OpenAPI?

Yes. Use the GET /openapi/account/list endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Webull OpenAPI?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I get account list through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get account list'. Jentic returns the matching Webull OpenAPI operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Webull OpenAPI have?

The Webull OpenAPI exposes 13 endpoints covering accounts, market data, trading operations.

Can I limit what my agent is allowed to do with the Webull OpenAPI?

Yes. Because you run Jentic One yourself, you decide which Webull operations the agent can call, so you can grant read-only access to GET /openapi/account/list, GET /openapi/assets/balance, and GET /openapi/assets/positions while withholding everything else. Webull carries account and order details in the request body rather than the path, so trade actions such as POST /openapi/trade/order/place, /cancel, and /replace stay unavailable unless you deliberately add them. Your app key and signing key are stored encrypted by your own instance and injected only for the operations you allow, so the agent never sees raw secrets or reaches endpoints outside its scope.