Testing private configurations

Create an agent configuration, explicitly set visibility to private, add its instructions and Lorebooks, then start a conversation with your own account. Private testing uses the same model rates as other conversations and requires chat.play.

Private configurations stay owner-only until you change access. Set visibility to unlisted when you want others with the ID to use one. Community review and listing are separate from this access setting. Delete test configurations through the authoring API when you no longer need them.

The current HarperHarbor API does not provide /trial-cards endpoints, trial slots or automatic trial expiry. Applications should use the documented private-configuration lifecycle.