A white-label endpoint is one a reseller adds to the API it sells under its own name. It is not a new capability — it is a few of the operations that API already has, in order, behind one address and one name the reseller chose. Its customers call it the way they call anything else, and their assistants see it in the tool list beside the operations it is built from.
Why a reseller wants one
Because the product it sells is usually not an operation. "We warm a list up for you" is a search, then a reaction for each result, then an invitation to the people who wrote them — four calls its customers' assistants have to get right and in order, every time. One endpoint is the same work, named once, described in the reseller's own words.
What it can and cannot be built from
Only operations the reseller's own plan carries. An endpoint of its own is a shortcut through the API it bought, never a way around it: a step naming something outside its plan is refused when the endpoint is written, not when it runs.
Conditions and loops are allowed; an expression language is not. A value is ordinary JSON or a path read out of the run so far, and a condition is a comparison. Nothing is evaluated, because the endpoint is written by a customer, stored, and then run on the provider's server against a real account.
What one call may spend
A loop means an endpoint can ask for more work than anybody meant to ask for, so one run has ceilings: a number of operations, a number of iterations and a clock. Reaching one is an answer rather than an error — it says what had already been done, because there is no taking back a message that has been sent.
Every step is authorised as a fresh request, so an id the first step produced proves itself again before the second may use it. A composed endpoint is not a way to skip the checks the operations inside it carry, and it spends the same pacing budget they do.
The other half: taking ours away
A reseller can also hide operations it does not want to offer. Hiding takes one out of the tool list, the manifest and the reference; the route still answers, so a customer already calling it is not broken by a change made in a sentence. A reseller that wants a whole area gone stops offering that area instead.
Questions people ask
Can an AI agent write one of these for me?
That is the usual way. Describe what the endpoint should do and which of your operations it should use, and the assistant writes the steps and saves it. It is refused by name if it reaches for an operation your plan does not carry, so a wrong guess is corrected rather than stored.
Does an endpoint of my own cost more to run?
It costs what the operations inside it cost. One call that performs four actions spends the same pacing budget as four calls that perform them, because each step is authorised and paced as its own request.