Multi-agent real estate commission split

Closing a residential or commercial deal often means three money lines share one gross commission: a referring agent or network takes a referral fee, the brokerage house keeps its company split, and the producing agent keeps what remains. If the two percentages sum to more than one hundred percent, the engine rejects the request with a clear invalid input error instead of inventing negative agent pay.

Inputs: total commission, brokerage split, and referral fee

Both percentages must be non-negative and each is capped at one hundred so a single field cannot alone exceed the whole pot. Negative commission amounts fail validation because they do not describe a normal closing. All validation runs before money math, so bad requests never produce half-filled settlement rows. Send a JSON body with three required fields. Total commission is the gross commission pot before any multi-agent allocation, as a non-negative finite number or numeric string; aliases commission, total, amount, and gross_commission are accepted when your client already names the field differently. Brokerage split percent is the company house share expressed as a percentage of that total—for example thirty means thirty percent—not a decimal fraction; aliases brokerage_percent, brokerage, broker_split, and company_split map to the same value so form builders can keep familiar labels. Referral fee percent is the referring party share of the same total, again as a percentage such as twenty-five for twenty-five percent; aliases referral_percent, referral, referral_fee, and referring_agent_percent are supported. Missing any of the three fields fails with invalid_input naming the missing key. When brokerage split percent plus referral fee percent exceeds one hundred, the engine raises invalid_input explaining that the combined percentages must not exceed one hundred percent—the classic over-allocation trap for multi-party commission tools.

How referral, brokerage, and agent net amounts are computed

The response echoes the normalized total commission and both input percentages, then returns agent_percent, percent_sum, referral_amount, brokerage_amount, and agent_net, plus currency_decimals equal to two and method equal to commission_split_multi_agent for stable client branching. Identical inputs always produce identical JSON because the path is pure arithmetic with no network, no random seed, and no wall clock.

API usage, pricing, workflows, and practical limits

Call the free in-browser multi-agent commission split calculator when coaching new agents, reviewing offer sheets, or double-checking a desk spreadsheet without installing another app. Keep commission sizes within ordinary commercial ranges; extremely large amounts are rejected so isolate math stays bounded. The product promise is a transparent three-party allocation of one gross commission with an explicit over-one-hundred percent guard—not dual-agency side math, not sliding company schedules by production tier, and not automatic MLS fee tables, which belong in specialized tools with different SEO intent. Use the prepaid API when a brokerage CRM, transaction coordinator bot, team dashboard, or compliance export needs a stable KIT contract at $0.002 per successful item; validation failures never consume balance after the engine rejects the request. Pair this endpoint with mortgage or closing-cost tools only if you already know the commission pot in a single currency—this capability does not convert FX, prorate taxes, or apply franchise fees beyond the two percentage inputs. Authors shipping SDKs can map referral_amount, brokerage_amount, and agent_net directly into settlement UIs and payout messages.