For Earning Platforms, Trading Apps & Fintech Products

Ship trading. Skip the build.

An API for Trade Account provisioning, execution, telemetry, and reporting. Your users never leave your product; you keep the brand, billing, and customer relationship.

Book technical discovery View API reference
Non-custodial MetaTrader 5 API & Whitelabel
api.sentitrade.xyz/v1
$600M+Cumulative volume
63,000+Closed deals
$38MSingle-day peak
99.9%Live-beta uptime

One integration sits on the execution infrastructure behind Senti's live beta. These figures describe real infrastructure activity and availability. They are not investment returns, yield projections, or guarantees of trading performance.

[01]Reference / 01 : 13

A completed embedded integration, with no Senti product surface

A partner earning platform has completed the technical integration of Senti's non-custodial execution engine into its own product. Their users stay inside the partner's interface. It is shown here as an integration pattern, not a customer performance reference.

Documented integration flow

Users stay in your product. The broker holds the funds.

The partner's engineering team completed the technical integration of Senti's execution engine into their platform. This is evidence of a completed technical integration. Production rollout is a separate step, confirmed with each platform on its own timeline.

Partner app + funding input → broker account → Senti API → MT5 forex and gold execution → reporting back to the partner app

  • Users remain in the partner's interface and never touch a Senti product surface.
  • The broker continues to hold the account funds.
  • Senti's role is limited to non-custodial trading execution infrastructure and operational activity.
  • Senti does not own, promise, or guarantee the partner's customer outcomes.
[02]The hidden second roadmap / 02 : 13

The feature your users see hides an infrastructure business

Adding trading to an existing product is not one endpoint. Your team must coordinate account lifecycle, execution, broker connectivity, operational status, reporting, and the exception paths that appear after launch. Building all of that internally creates a second roadmap.

  • Product waits for infrastructure before it can validate demand.
  • Engineers maintain broker and execution complexity instead of differentiating the customer experience.
  • Operations teams inherit new account and incident workflows.
  • Every scale milestone adds more runtime, monitoring, and support pressure.
  • The customer journey fragments when users must leave your app to complete a trading flow.
[03]API / 03 : 13

Infrastructure primitives, not a finished interface

Senti supplies the execution layer as API primitives your team composes into its own product flow. Your frontend and orchestration stay yours.

[01] Trade Account provisioning

Provisioning and lifecycle infrastructure for the Trade Accounts your product creates on behalf of its users.

[02] Trading automation and execution

The automation and execution infrastructure that runs the supported trading workflow against the connected broker.

[03] Telemetry and reporting inputs

Operational telemetry and reporting inputs you can surface back inside the product experience your users already know.

[04] Broker connectivity

Broker connectivity within the supported scope, so your team integrates one agreed boundary instead of many.

[05] Monitoring and escalation

Infrastructure monitoring and a defined technical escalation path for the scope set in the API agreement.

[06] Non-custodial execution model

Execution runs without a Senti withdrawal path. User funds remain at the broker throughout.

The exact endpoints, authentication model, sandbox scope, rate limits, and supported brokers are validated against the current API documentation and confirmed during technical evaluation.

[04]Ownership boundary / 04 : 13

Keep what makes your product yours

Senti operates underneath your product. Your users do not need to leave your experience for a separate Senti product flow.

You own
Senti operates
User experience and product journey
Trade Account provisioning and lifecycle infrastructure
Brand, positioning, and customer communications
Trading automation and execution infrastructure
End-user onboarding and billing
Operational telemetry and reporting inputs
Strategy selection and customer-facing disclosures
Broker connectivity within the supported scope
Product analytics, support policy, and commercial offer
Infrastructure monitoring and technical escalation
The decision about when and where trading appears
The agreed technical service boundary
Non-custodial by design

User funds remain at the broker

Custody stays where it already is.

  • User funds remain at the broker. The broker holds the account funds throughout.
  • Senti provides trading execution infrastructure and does not provide a withdrawal path.
  • Your platform owns the customer relationship, strategy selection, and customer-facing disclosures.
  • Your own product flow and business model may create separate custody or regulatory obligations, which your team should assess with qualified local counsel.

Senti is trading automation infrastructure. It is not a broker, fund manager, copy-trading marketplace, signal seller, or promise of returns.

Review Trust & Security →

[05]Best fit / 05 : 13

Built for product teams with an audience and a differentiated experience

  • Earning platforms adding access to broker-based trading products.
  • Trading applications that want control over the user journey without building the full execution layer.
  • Fintech products introducing trading as a new capability.
  • Platforms with an existing frontend and engineering team that need infrastructure primitives rather than a finished branded interface.

Not the right route if you want Senti's complete product flow with only brand customization. In that case, evaluate the Trading Groups & Trading Academies solution instead.

[06]Architecture / 06 : 13

How Senti fits into your architecture

Request path

Your user → Your product experience → Your orchestration layer → Senti API → Broker Trade Account

Operational status and reporting inputs return through the integration to the product surface your users already know. The exact endpoints, authentication model, sandbox scope, rate limits, and supported brokers must be validated against the current API documentation and confirmed during technical evaluation.

[07]Build vs integrate / 07 : 13

From infrastructure backlog to product capability

Build the trading layer internally
Integrate Senti
Design and maintain account-lifecycle infrastructure
Use Trade Account provisioning primitives
Own broker connectivity and execution operations
Integrate through one agreed infrastructure boundary
Build telemetry and reporting inputs from the ground up
Bring execution and operational data into your product surface
Create monitoring and incident escalation processes
Establish a defined technical escalation path
Delay customer validation until the stack is ready
Start with one controlled end-to-end integration flow

Senti does not remove your responsibility for product, risk, compliance, or customer experience. It reduces the amount of undifferentiated infrastructure your team must build and operate to deliver them.

[08]Business outcomes / 08 : 13

What the integration protects

Validate sooner

Test a real trading journey before committing to a full internal infrastructure build.

Protect product focus

Keep engineering centered on the experience and capabilities your customers choose you for.

Keep the commercial relationship

Own end-user billing, packaging, and communications.

Scale with usage

Infrastructure cost follows provisioned Trade Accounts instead of a large fixed platform commitment.

Simplify the user journey

Keep trading inside your existing product surface.

Reduce custody exposure

Senti's execution model is non-custodial. User funds remain at the broker.

[09]Commercial model / 09 : 13

A per-Trade-Account fee, with no monthly base fee

The API service uses a per-Trade-Account infrastructure fee with no monthly base fee. Standard self-service integration has a $0 setup fee. For planning purposes, the current working baseline is approximately $10–12 per provisioned Trade Account per month.

Monthly provisioned Trade Accounts
Working discount from the illustrative base rate
1–49
Standard illustrative rate
50–249
10%
250–999
20%
1,000–4,999
30%
5,000+
Enterprise contract

This framework is shared for evaluation, not as a fixed public quote. The final base rate, applicable volume band, included scope, and commercial terms are confirmed in the contract. Your platform owns end-user billing. Senti bills your organization for the provisioned infrastructure under the agreed API contract. Standard API support uses a 24-hour email-response target. The 99.9% figure on this page is measured operational uptime from Senti's live beta. It is evidence of current infrastructure operation, not a contractual uptime guarantee for an API deployment.

[10]Integration path / 10 : 13

Start with one journey, then earn the right to expand

01
Map the use case

Define the user journey, Trade Account model, expected scale, broker scope, and the product outcome you need to validate.

02
Review the architecture

Confirm system boundaries, data flows, security questions, operational ownership, and the API surface required.

03
Validate in a controlled environment

Use the agreed sandbox scope to prove one provisioning-to-reporting journey.

04
Set production acceptance criteria

Agree on failure handling, support ownership, monitoring, and launch readiness.

05
Launch a limited cohort

Observe the complete operational loop before expanding users, Trade Accounts, or product flows.

06
Scale deliberately

Add more journeys and accounts after the technical and operational model has been accepted.

The integration timeline depends on your product architecture and the API scope you choose. It is confirmed after technical discovery.

[11]The alternatives / 11 : 13

Compare your options

Different categories solve different product problems. The right choice depends on what your team wants to own.

Option
Strong fit when…
What your team owns
Senti API
You want an automation-first trading capability inside your own product
Customer experience, orchestration, billing, disclosures, and product operations
Copy-trading networks such as ZuluTrade or eToro
Access to an established social or copy-trading experience is central to the offer
Integration into that network and the customer proposition built around it
cTrader or a broker whitelabel
A mature, broker-led trader interface and familiar trading workflow are the priority
The commercial relationship, configuration, and any capabilities required beyond the supplied platform
Build in-house
Execution infrastructure is part of your strategic core and you can staff it as a permanent capability
Broker integrations, runtime, telemetry, monitoring, security, maintenance, and incident response

Senti is not a universal replacement for these options. It is the fit when your product needs control of its own customer journey without taking on the entire trading automation infrastructure stack.

[12]Which route / 12 : 13

API, or a branded platform?

Both routes use Senti's trading automation infrastructure. The decision is about product control and billing responsibility, not a promise of trading performance.

Choose the Senti API when
Choose Trading Groups & Academies when
Your team already has a product users log into
You want a ready product flow under your brand
You want control over UX and orchestration
You prefer Senti's established workflow
You have engineering capacity for the integration
You want less frontend integration work
You want to own end-user billing
You want end users to subscribe through your branded surface
Your product flow is a source of differentiation
Speed and operational simplicity matter more than flow control
[13]Common questions / 13 : 13

Frequently asked questions

Is the API the same as the Trading Groups & Academies solution? +
No. API customers build and control their own interface and product flow. Trading Groups and Trading Academies use Senti's product flow under their own brand.
Will our users see Senti? +
The API is designed to operate as infrastructure beneath your product. Your team owns the customer-facing experience and decides how infrastructure partners are disclosed, subject to the agreement and applicable requirements.
Who bills the end user? +
Your platform does. In the API model, Senti bills your organization for provisioned Trade Account infrastructure under the contract.
What does "non-custodial" mean here? +
User funds remain at the broker. Senti provides trading execution infrastructure and does not provide a withdrawal path. Your own product flow and business model may create separate custody or regulatory obligations, which your team should assess with qualified local counsel.
What does the API cost? +
The model is per Trade Account, with no monthly base fee and $0 setup for the standard self-service path. Approximately $10–12 per provisioned Trade Account per month is an illustrative planning range only. The working framework discounts that base by 10% from 50 accounts, 20% from 250, and 30% from 1,000; 5,000+ accounts use an Enterprise contract. Final pricing and volume terms are contract-confirmed.
Can we begin with one use case? +
Yes. The recommended evaluation path starts with one controlled provisioning-to-reporting journey before adding more flows or accounts.
How long does integration take? +
It depends on your current architecture, required API surface, broker scope, security review, and production acceptance process. Senti confirms the delivery plan after technical discovery rather than promising a generic timeline.
Does Senti guarantee trading returns or yield? +
No. Senti provides trading automation infrastructure. Strategy selection, customer disclosures, risk, and performance remain the responsibility of your organization.
Who owns support when something goes wrong? +
Your team remains the customer-facing support owner. Senti provides technical escalation for the infrastructure scope defined in the API agreement. The handoff and incident process are agreed before production.
Also see: API reference· Trust & Security· Trading Groups & Academies

Keep your product. Add the layer.

Bring one target journey, your architecture, and expected Trade Account volume. We will map the smallest useful integration and name the open risks.

Read the docs The first conversation is an architecture review, not a generic product tour.