Magick Nu Tradeworks

Name: Tradeworks API
Brand: Tradeworks
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingbasic8 EndpointsREST

Install Jentic One Beta

Connect the Tradeworks to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tradeworks, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmagick.nu%2Ftradeworks-main" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmagick.nu%2Ftradeworks-main" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Tradeworks API.

Create new Tradeworks user accounts via POST /users

Rotate the MT4 account password using PUT /tradingAccounts/password/{username}/{brokerserver}/{mt4username}

GET STARTED

Start building with Tradeworks API

Explore with Jentic

View OpenAPI Document

For Agents

Provision Tradeworks users, register MT4 trading accounts, and look up strategy templates through eight REST endpoints aimed at retail forex automation.

Use for: I need to register a new Tradeworks user from our onboarding flow, Attach an MT4 trading account to an existing Tradeworks user, Rotate the MT4 password for a user's broker connection, Check whether a username is already taken before signup

Not supported: Does not handle order placement, position management, or live MT4 trade execution - use for Tradeworks user provisioning, MT4 account registration, password rotation and strategy template lookup only.

Use Cases

Patterns agents use Tradeworks API for, with concrete tasks.

★ Forex Trader Onboarding

Run a frictionless signup flow that provisions a Tradeworks user and binds their MT4 account in one pass. The agent calls GET /users/email/{email} and GET /users/username/{username} to validate availability, POST /users to create the profile, and POST /tradingAccounts to register the MT4 connection. Suitable for forex affiliates and white-label brokers that need a programmatic signup pipeline.

POST /users to create the new Tradeworks user, then POST /tradingAccounts to attach the MT4 broker server and credentials

Strategy Template Discovery

Surface the Tradeworks strategy library to traders before they wire it to an MT4 account. GET /strategies/templates returns every published template, and GET /strategies/strategyId/{strategyId} fetches a single strategy's configuration. Useful for affiliate dashboards and strategy comparison tools that want to render a selection UI ahead of trading account binding.

Call GET /strategies/templates and render each template name and id, then GET /strategies/strategyId/{strategyId} when the trader picks one

Credential Rotation

Drive scheduled password rotation for Tradeworks users and their MT4 broker connections. PUT /users/password/{username} rotates the Tradeworks login, and PUT /tradingAccounts/password/{username}/{brokerserver}/{mt4username} rotates the MT4 password. Useful for security operators enforcing a credential hygiene policy across a managed pool of forex accounts.

PUT /tradingAccounts/password/{username}/{brokerserver}/{mt4username} for every account flagged in the rotation queue

AI Agent Forex Account Provisioning

Let an AI assistant onboard a forex client end-to-end without holding the underlying broker credentials. Through Jentic the agent searches for the user creation operation, loads the schema for /users and /tradingAccounts, and executes with credentials brokered by the vault. Useful for chatbots embedded in affiliate sites that funnel traders into Tradeworks.

Search Jentic for 'create a tradeworks user', load POST /users, and execute with the email, username and password supplied by the user

Key Endpoints

8 endpoints — jentic publishes the only available openapi specification for tradeworks, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/users

Create a new Tradeworks user

POST

/tradingAccounts

PUT

/tradingAccounts/password/{username}/{brokerserver}/{mt4username}

Update an MT4 account password

GET

/strategies/templates

List all template strategies

GET

/strategies/strategyId/{strategyId}

Get a strategy by ID

GET

/users/email/{email}

Check email availability

GET

/users/username/{username}

Check username availability

PUT

/users/password/{username}

Update a user's password

POST

/users

Create a new Tradeworks user

POST

/tradingAccounts

PUT

/tradingAccounts/password/{username}/{brokerserver}/{mt4username}

Update an MT4 account password

GET

/strategies/templates

List all template strategies

GET

/strategies/strategyId/{strategyId}

Get a strategy by ID

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Tradeworks API by hand means encoding basic-auth credentials on every request and coordinating them across user provisioning, MT4 account registration, password rotation, and strategy-template paths. Through Jentic you install once, import Tradeworks from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

You choose which Tradeworks operations the agent may call, so you can limit it to the ones it needs, such as creating a user or listing strategy templates, and leave out others like rotating an MT4 account password unless you add them. The agent only reaches the operations in the set you allow.

Credential isolation

Your Tradeworks credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a Tradeworks user' or 'register an MT4 account', and Jentic returns the matching Tradeworks operation with its input schema so the agent calls the right endpoint directly.

FAQs

Specific to using Tradeworks API through Jentic.

Why is there no official OpenAPI spec for Tradeworks?

Magick.nu does not publish an OpenAPI specification for Tradeworks; the API is documented only through a Swagger UI page on the developer site. Jentic generates and maintains this spec so AI agents and developers can call Tradeworks via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Tradeworks API use?

The Tradeworks API requires HTTP Basic authentication - the developer Swagger page asks for username and password. Through Jentic the credential is stored encrypted in your Jentic One instance, so an agent calls /users or /tradingAccounts with a scoped token rather than embedding the basic-auth pair.

Can the Tradeworks API place trades on MT4?

No. The exposed endpoints cover user provisioning, MT4 account registration via POST /tradingAccounts, password rotation, and strategy template lookup. Order placement and execution flow through the MT4 terminal itself, not through the eight REST endpoints in this spec.

What are the rate limits for the Tradeworks API?

Per-endpoint rate limits are not defined in the spec. The base URL points at a dev environment (http://devui.magick.nu/rest), so production limits should be confirmed with Magick.nu directly before high-volume usage.

How do I register a new MT4 account through Jentic?

Run pip install jentic, search for 'register an mt4 trading account', and Jentic surfaces POST /tradingAccounts with its input schema. Execute with the broker server, MT4 username and password fields and Jentic returns the registered account record.

How do I check whether a username is available before signup?

Call GET /users/username/{username} with the desired username as a path parameter. The endpoint returns an availability flag so the signup flow can prompt for an alternative before it issues POST /users. The same pattern applies to GET /users/email/{email} for email availability.

Magick Nu Tradeworks

Connect the Tradeworks to your agent

Capabilities

Start building with Tradeworks API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs