Standin writes one casting notice per surface, each obeying that place's own limits, and checks every notice after it is written against what that place requires. A role with a never-ask phrase in it is refused before any work runs.
Nothing opens in this browser — this one takes a job and does the work on our own graphics cards in Oregon. The free allowance below is how you try it: 20 notices, no card and no payment, on the key you are issued.
The phrase is named, nothing is charged, and the same phrase coming back from the model gets no retry either.
The problem
A role gets described in a hurry, posted in four places, and one of the four phrases in it is the kind that turns a casting call into evidence — an ask that cannot lawfully be made a condition of work, a requirement that is really a demand, a rate that is really a contingency. Posted once it is screenshotted forever, and every board has different rules about what a notice must contain and may not.
A role containing a never-ask phrase is refused at the door with the phrase named and nothing charged. It is not quietly rewritten into something postable, because the problem is the ask and not the wording.
One notice per place you post, inside that place's limits and containing what that place requires — the rate disclosure, the contact rule, the content description. Checked in Python after writing.
If the model returns the same never-ask phrase, there is no second attempt. A retry here would just be the program trying to find a phrasing that gets past its own gate.
You keep the list of phrases that must never appear in a casting notice — the asks that cannot be a condition of work. If the role you typed contains one, Standin stops, names the phrase, and charges nothing. It does not soften it. Softening is the harm: it produces a notice that reads acceptably and still describes the same ask, which is worse than the blunt version because now it is deniable.
How it works
What the part is, the rate, the dates, what is required and what is not. Your own words — which is what the phrase gate reads before anything else happens.
Where you are posting. Each has different required disclosures and different limits, so each gets its own notice rather than one notice cut to the shortest length.
Each notice comes back with what was required and whether it is present. A notice missing a required disclosure is rewritten before you see it, not flagged for you to fix.
What it will never do
This is a program that writes recruitment copy for an industry where recruitment copy is scrutinised. All four refusals are about not helping you across a line.
Pricing
A notice is one role for one surface. Four surfaces for one role is four notices because it is four documents with four different sets of requirements. Twenty are free on every key, and refusals are never charged.
Five roles across four surfaces each.
A year of casting across every board you use.
A studio or agency casting continuously.
Per notice written. A refused role costs nothing, which means the gate is free and only the writing is paid for. Your licence key is emailed to you within two working days of payment.
Checkout is our own bitcoin server, not a card processor. The units you buy are added to your key: buy from the Buy more box inside the program and they arrive on their own once the payment confirms, or buy here and paste the invoice number from your receipt into that box.
Questions
You do. The list is yours and it lives in your own settings.
That is deliberate: the phrases that must never appear in your notices depend on your jurisdiction and your counsel, not on a vendor's taste. What the program guarantees is that once a phrase is on the list, no notice containing it is ever written — not softened, not flagged, not written.
Because the thing that is wrong is the ask, not the sentence.
A rewritten version describes the same condition in acceptable language, which makes it harder to see and no more lawful. If the role needs to change, that is a decision a person makes about the role.
No. It writes notices. Screening applicants is a different job with different risks, and conflating the two would put a model in the path of deciding who gets work.
No. Writing runs on Tower 1's own graphics cards in Oregon, and the phrase gate runs in Python before anything is sent to it at all.
A key. One line of text, issued to you and shown exactly once — only its hash is kept here, so it cannot be looked up later and we could not tell you what yours is. Every key arrives with a free allowance already on it, which is the tier at the top of the pricing above, and the work starts the first time you send a job with that key on it.
Each job is metered in the unit named in the pricing, and a unit that fails — a file that will not read, a row the model held back — is not charged and is named in the job report rather than silently skipped. When an allowance runs out the next job is refused before any work starts, with the number it used printed on the refusal.
More units are bought in bitcoin. The checkout is a bitcoin server we run ourselves. Buy from the Buy more box inside the program and the units are added to your key on their own as soon as the payment confirms; buy from the plan buttons above and paste the invoice number from your receipt into that same box. Each payment adds its units once, to one key.
It costs nothing to be refused. If a phrase in the way you normally describe the part comes back named, that is worth more than the twenty free notices.