Partners

Your customers, our rails.

CAPX holds tokenised shares in custody, prices them from live oracles and settles in shillings. You can put that inside your own app — Dar es Salaam listings and US equities, bought in the currency your customer already holds, with one API key.

Two boards, one call

CRDB, NMB and the rest of the DSE in shillings. Apple, NVIDIA and the tokenised US board in dollars. Same endpoint, the currency is a field — a customer holding USDC buys US equities directly, and converts once to reach the DSE.

Your customers stay yours

You authenticate them. CAPX never issues them a password and has no sign-in path that goes around you. They carry your own reference, so neither side needs a mapping table.

The same book as everyone else

A customer you introduce is an ordinary CAPX account. Same ledger, same custody, same solvency check against what is actually held on-chain. There is no second book to reconcile.

Dividends handled

A tokenised equity reflects a dividend by raising its multiplier, so the holder's share count grows rather than their cash. CAPX reads that and credits whoever held the claim. You read it back per customer.

Verification is real

You file your customer's documents through the API; CAPX reviews them. Buying is gated on approval, and nothing you can send sets that — the obligation is ours and so is the decision.

Funding is yours to start

Prompt your customer's mobile money, or hand them a one-off bank reference. The rail is chosen by the same code the CAPX app uses, so there is no second path for money arriving.

Retries are safe

Every money endpoint takes an Idempotency-Key and returns the original answer to a repeat. A dropped connection costs you a retry, not a double order.

How it goes

Step 1
Apply
Takes a few minutes. You get a test key straight away and can start building.
Step 2
Build
Read markets, create customers, file their verification — all on the test key.
Step 3
Approval
A person reads your application. Your live key arrives with it.
Step 4
Go live
Swap the key. Nothing else in your integration changes.

Apply

Tell us who you are.

You get a test key immediately and can build while we read this.

Registered company name *Who we should talk toContact email *The approval and your live key go here.PhoneCompany registration numberCountry of registrationWebsiteCustomers you expect in year oneWhat are you building? *This is the part that gets read properly. Regulatory standing in your market matters more than volume.

A buy, end to end

# 1. your customer, carrying your own id for them
curl -X POST https://www.capx.broker/api/partner/v1/users \
  -H "Authorization: Bearer $CAPX_KEY" \
  -d '{"email":"asha@example.com","reference":"cust_8812",
       "name":"Asha Mwinyi","phone":"+255700000000"}'

# 2. buy 50,000 shillings of CRDB
curl -X POST https://www.capx.broker/api/partner/v1/orders \
  -H "Authorization: Bearer $CAPX_KEY" \
  -H "Idempotency-Key: ord_9f21" \
  -d '{"user":"cust_8812","security":"CRDB",
       "side":"buy","amount":50000}'

# 3. or Apple, in dollars
curl -X POST https://www.capx.broker/api/partner/v1/orders \
  -H "Authorization: Bearer $CAPX_KEY" \
  -H "Idempotency-Key: ord_9f22" \
  -d '{"user":"cust_8812","security":"AAPLc",
       "side":"buy","amount":25,"currency":"USDC"}'

Full API reference

CAPX is operated by NEDA Labs Limited. Tokenised US equities are issued by Coinbase and are available only to persons in eligible jurisdictions outside the United States; you are responsible for applying that restriction to your own customers. Nothing here is an offer of securities or investment advice.