Partner Integration
Two ways to build on TRUE: the referral programme with its own reporting endpoints, and MCP for putting TRUE data and tools inside your own product.
Two ways in
- Refer users and earn a share of the fees they pay, with reporting you can pull rather than screenshot.
- Build on TRUE’s data and tools through MCP or the trading API, inside your own product.
They are independent. Plenty of partners do only the first.
The referral programme
Your rate is set by the fees your referrals generated in the last 30 days, not by their volume. Referring a few serious traders beats referring many dormant accounts, and the ladder is built so that it does.
| Level | 30-day referred fees | Your share |
|---|---|---|
| 1 | $0 | 10% |
| 2 | $250 | 12% |
| 3 | $1,000 | 15% |
| 4 | $4,000 | 18% |
| 5 | $10,000 | 22% |
| 6 | $25,000 | 25% |
Swaps, perps and predictions pay the same rate at every level, and copy trading counts as perps. Your referrals also pay 10% less in fees, for life, which is the part that makes the link worth clicking.
Full detail, including what the share is calculated on, is on Fees and Rebates.
Reporting endpoints
Authenticated as the partner. Everything the dashboard shows, you can pull.
GET https://app.truefinance.ai/api/v1/partner/summary GET https://app.truefinance.ai/api/v1/partner/referrals GET https://app.truefinance.ai/api/v1/partner/earnings GET https://app.truefinance.ai/api/v1/partner/settlements summary is your current level and the fees behind it. referrals is who you brought. earnings is what has accrued. settlements is what has been paid.
The rate and the basis are the same on every partner-facing read. What your dashboard shows is what pays, and if an endpoint ever disagreed with the dashboard that would be a bug in the endpoint, not a different accounting view.
Building on TRUE
An earlier version of this page documented a hosted widget script and a partner SSO exchange endpoint. Neither exists. If you want TRUE inside your product, the supported paths are the two below.
MCP
The cleanest option for an AI product. One endpoint, standard Model Context Protocol, and the same tools TRUE’s own assistants use: prices, market data, asset search, news, on-chain intelligence and user context.
For a product with many users, use OAuth so each tool call runs as that user rather than as you. See MCP and Authentication.
Trading API
Market data is public and needs no key. Trading needs a key bound to a wallet, and orders carry that wallet’s signature. See Trading API.
What TRUE will not do for you
- Hold your users’ funds. TRUE is non-custodial for your users exactly as it is for ours. See Non-Custodial by Design.
- Sign on a user’s behalf. Every value-moving action is that user’s signature.
- Give you a higher tier by asking. Elevated API limits are granted against a described use case and require an IP allowlist.
See also
- Fees and Rebates — the full commission detail.
- MCP · Trading API
- Non-Custodial by Design — what TRUE is, and what it never holds.