For publishers.

Muhabbit does not republish the news. It adds its own work about it: an impact score, a summary in its own words and a translation, and it sends every reader to your page for the story itself.

Your headline, your publication's name and a link to your page, on every story. Open the source is the first action on each story page, right under the headline.

A summary Muhabbit's AI writes in its own words. If a generated sentence repeats 12 or more words in a row from your text, it is cut before the summary is stored.

Never your article body. The API passes on at most the first 120 characters of your text, and the site shows none of it. Muhabbit keeps the text it read only while its pipeline needs it.

No copies of your images. Muhabbit does not store or serve your photos. The API passes on the address of your own preview image, and Telegram alerts carry a link that Telegram previews from your page.

Posts on X appear through X's own embed on their story page, credited to the author, next to Muhabbit's own summary.

To stop MuhabbitBot reading your pages at all, use robots.txt or a text and data mining reservation. MuhabbitBot lists the signals it honors.

Write to hello@muhabbit.com from your publication's domain, with Takedown in the subject. Name the site or feed and say which of these you want. Requests are usually handled the same working day.

Remove your source. Muhabbit stops reading your feed, and every story from it leaves the site, the API, RSS and the MCP tools at once, older stories included.

Remove one story. An editor takes it down, and its page answers not found.

Something narrower. Fewer stories, a delay, or headlines without summaries: tell us what you need, and you get a plain answer about what Muhabbit can do for your feed.

A removal can be undone. Write again and your source is switched back on.

Muhabbit links readers to publishers' pages, which makes it an information location tool under 17 U.S.C. 512(d). To report infringement, send a notice to hello@muhabbit.com that includes:

• your physical or electronic signature, as the owner or someone authorized to act for the owner;
• the work you say is infringed;
• the Muhabbit page or API item to remove, with its link;
• your address, phone number and email;
• a statement that you believe in good faith that the use is not authorized by the owner, its agent or the law;
• a statement that the notice is accurate and, under penalty of perjury, that you are authorized to act for the owner.

Muhabbit removes or disables the link quickly once a valid notice arrives.

Counter-notice. If your story was removed because of someone else's notice and you believe that was a mistake, send to the same address: your signature; the removed material and where it appeared; a statement under penalty of perjury that you believe in good faith it was removed by mistake or misidentification; and your name, address and phone, with consent to the jurisdiction of the federal court for your address (or, outside the United States, any district where Muhabbit may be found) and agreement to accept service from the person who sent the notice. Muhabbit forwards it to that person and restores the material in 10 to 14 business days unless they tell Muhabbit they have filed suit.

Repeat infringers. Muhabbit switches off sources that are the subject of repeated valid notices, and ends the API access of customers who repeatedly infringe.

The public record at /events keeps every published headline in a hash chain, so no one can edit it after the fact. Entries for your stories stay in it. If that is a problem for you, say so in your request.

Alerts already delivered, and copies API customers made before the removal, are outside Muhabbit's control.

Headlines and excerpts stay yours. Muhabbit's API licenses only what Muhabbit makes: its summaries and their translations, scores and narratives. API customers must name and link you with any headline they show, and may not republish your content. See the terms.