Long-lived context tokens for ABM outreach with stated segments

When a personalised link is built for an email campaign or an account-based outreach sequence, the one-hour default token lifetime is nearly always too short. Passing ttlSeconds with your workspace API key extends the token to whatever your campaign needs, up to 90 days, so the link is still valid when a contact opens the email three weeks after it was sent.

The qualify endpoint now also accepts audience and stage alongside the summary. When your outreach tool already holds a reviewed persona, such as an IT Director in a specific vertical, you can assert that segment directly rather than asking the classifier to infer it from an English sentence. The classifier still runs to extract entities and build the atom search query, but the audience and stage you state take precedence, and confidence is set to 1 so the assembly engine treats the token as a certain signal rather than a probabilistic guess.

Both fields require the workspace API key. An unrecognised value returns a 400 carrying the list of valid options, so errors surface in your link-building tool rather than silently producing a token that personalises for the wrong segment. If the org is rate-limited or over quota, a stated mint returns a 429 or 402 rather than degrading to a default token, because a campaign link that serves default atoms is worse than no link at all.

The qualify cache is not affected by stated overrides. The same summary with two different stated audiences produces two correct tokens without any cache collision, and the stored classification always reflects pure classifier output so cache warming and analytics remain accurate.