Trade copying.
Built with Rust.
From your first authenticated request to a monitored master–follower workflow. Clear examples, explicit sizing and practical recovery.
Start building → Explore the API-
01 · Connect with confidence
Understand keys, account IDs and transport before sending a request.
-
02 · Control the lifecycle
Start once, inspect state, pause and clean up your test.
-
03 · Make sizing explicit
Choose lot, balance or equity sizing and account for broker constraints.
-
04 · Diagnose the result
Separate network success from management success and broker execution.
Your first successful request¶
Requires Stable Rust, Cargo and protoc on PATH. Install dependencies and run the read-only List example. Keep your key in MRPC_API_KEY.
use rustcopier::client::CopierService;
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
let key = std::env::var("MRPC_API_KEY")?;
let service = CopierService::connect("https://copy.mrpc.pro", &key).await?;
let result = service.list().await?;
if !result.ok { return Err(result.error.into()); }
for copier in result.copiers { println!("{}: paused={}", copier.id, copier.paused); }
Ok(())
}
Full setup · Testing guide · All SDKs
Watch a real demo failure and recovery¶
Copier troubleshooting video follows an oversized follower request from its broker rejection through a corrected demo opening and closing. It demonstrates the control-panel workflow; the lifecycle recipes, sizing guide and error guide explain how to apply the checks in this SDK.
Use disposable demo accounts first. Hosted service usage is paid; consult current pricing. A successful management response does not prove that a broker executed the copied trade.