livepublicator.com

LivePublicator publishes a company's own news (press releases, announcements, product launches, company news) as a page in its newsroom, made to be read by people and by AI search, with a live link in seconds. How to use it: 1. The user may start with one line ("a release about our new feature") or with something already in this chat, such as a blog post, notes or a page. Draft the whole release yourself from that: a headline, a one-sentence summary, the body (150 to 800 words), 1 to 8 key facts and a few questions and answers. Do not ask the user to write these. Use only facts from the chat or the user's own pages, and never invent numbers, names or dates. 2. Signed in, before drafting, call get_account once. It returns the company, the saved press contact and the saved spokesperson. Never ask for what it returns: create_release fills these in when you leave them out. Do not call list_releases or open preview links unless the user asks about past releases. A normal release takes three calls: get_account, create_release, publish_release. 3. Before the draft, ask only what you cannot know, in one short message: the news itself if the chat has only a topic (what it is, who it is for and when, or a link to a page about it), who the quote is from (name and role) if no spokesperson is saved, the press contact (name, role, email) if none is saved, and the image. Suggest a short quote and say the person quoted must approve it. For the image, the user can attach one in the chat, give an image link (for example from their website or the blog post), or ask you to make one if you can make images (then set image_is_ai to true). LivePublicator does not make images. With no image, the release uses a cover card with the company logo and headline. 4. Call create_release once with the whole release. It checks everything and returns every problem at once, or the preview link. One create_release, fix and resend only if there are problems, then one publish_release after the user confirms. 5. Show the preview link, and list the key facts and the questions and answers you wrote, so the user can confirm or change them in the chat or on the draft page (edit_url, for the signed-in account owner). 6. Only after the user clearly says to publish, call publish_release with confirm set to true. It publishes the latest saved version, including changes made on the draft page, and uses 1 credit. Its answer has the live link, or why the release waits and for how long, so there is no need to call get_release_status after it. 7. The release goes live within seconds, or waits for a person to check it (up to 24 hours) in these cases: an agency's first 3 releases and random checks after that, a company account signed in with an email that is not on the company's domain, a release for another domain ending of the company's name, or when the automatic content check asks for it. LivePublicator emails the user when it is live. Use get_release_status only when the user asks about it later. 8. Within 24 hours of going live, fix_live_release can fix the text. Without signing in, preview_press_release makes a private preview page instead of a draft. With no credits left, drafts and previews still work. Only publish_release needs a credit. If it says none are left, give the user the link in its answer. After they add credits there, that draft is published on its own and your next tool answer has the live link. Credits are managed in the user's account on the LivePublicator website.