Skip to content

Paper notices

When a paper your agent bought text from is retracted or corrected, naulon tells the agent: in its next reply, from naulon_notices, or at a webhook.

On this page

When your agent buys text from a research paper through naulon and that paper is later retracted, withdrawn, corrected or put under an expression of concern, naulon tells the agent. Checking a DOI for retractions is something many tools do. Telling you afterwards, about the exact sentences you were sold, needs the party that sold them, which is us.

What you are told

Each notice names the paper, what happened to it, the sentences your agent was sold, and, for anything but a correction, papers that engage it and can be read instead:

{
  "id": "4b1f6a0e-7c1d-4a8e-9d59-2f6d1f0a3c11",
  "paper": { "key": "doi:10.1371/journal.pmed.0020124", "title": "Why Most Published Research Findings Are False", "page": "https://naulon.app/papers/doi/10.1371/journal.pmed.0020124" },
  "type": "retraction",
  "date": "2026-11-16",
  "seenAt": "2026-11-16T09:31:02.114Z",
  "source": "publisher",
  "doi": "10.9999/example.retraction",
  "served": [{ "textRoot": "9f2c…e41a", "sentences": [3, 4, 9], "more": false }],
  "instead": [{ "key": "doi:10.1186/…", "title": "…", "page": "https://naulon.app/papers/…", "licence": "cc-by", "studyType": "systematic_review", "year": 2024 }]
}

sentences are the indexes your receipt already used (quotes[].index), under the textRoot the receipt named, so your agent can find what it wrote from them. type is retraction, withdrawal, concern or correction; treat a value you do not know as a notice too. A correction is always sent as a correction.

A notice is sent only for something that happened after your agent read the paper. A paper that was already retracted when you bought from it is not sold as support in the first place.

Where it reaches you

In your agent's next reply. On the hosted MCP server (https://gate.naulon.app/_naulon/mcp, with your agent token), the next tool call your agent makes opens with a short notice ahead of the result it asked for, and the same notices sit under _meta["app.naulon/notices"] for code. The tool's own answer is never held back or changed by a notice.

From naulon_notices. The tool lists every notice your account was ever owed, newest first, with told on each. Use it from a client that shows its model only structured results, which skip the leading text block.

At a webhook. Set an HTTPS address on Buyer → Paper notices. naulon checks every 15 minutes and sends what is owed as one signed POST, event paper.notice.

A reply marks a notice told when it carries it, and the webhook when a delivery of it succeeds, so your agent hears once in-band even when the webhook keeps failing. The page lists them all, told or not, and reading the page does not mark anything told: the agent still hears.

The webhook

The body is the same envelope as every naulon webhook, with the notices under data:

{
  "id": "dlv_…",
  "type": "paper.notice",
  "eventId": "pn_3e0c…",
  "createdAt": 1794821633907,
  "data": { "notices": [ … ], "more": 0 }
}

more counts notices still owed after this batch of at most 20; they follow on the next check. De-duplicate on each notice's id: a notice stays owed until a delivery carrying it succeeds, so it can arrive again beside newer ones. Verify Naulon-Signature over the raw body with the signing secret shown when you added the address, then parse:

import { paperNoticeDataSchema, verifyPayload, webhookEnvelopeSchema } from "@naulon/sdk";

const raw = await request.text();
const signature = request.headers.get("naulon-signature") ?? "";
if (!verifyPayload(process.env.NAULON_NOTICES_SECRET!, raw, signature, Math.floor(Date.now() / 1000))) {
  return new Response("bad signature", { status: 401 });
}
const event = webhookEnvelopeSchema.parse(JSON.parse(raw));
if (event.type === "paper.notice") {
  const { notices } = paperNoticeDataSchema.parse(event.data);
  await store(notices);
}
return new Response(null, { status: 204 });

Return a 2xx once the notices are stored. Anything else is retried: after 5 seconds, 5 minutes, 30 minutes, 2, 5 and 10 hours. An address that keeps failing is paused, and the page says so; saving it again resumes it. The secret is shown once. If you lose it, remove the address and add it back.

What naulon keeps

To tell you anything, naulon records which papers and which sentences your account was sold, under a pseudonym the papers database cannot link to your account or to your runs. It never stores your question, a claim or an answer. Each paper is kept for five years after your last read of it, because a retraction lands a median of two years after publication and often later.

A purchase made over x402 with no account has no way to be told, so nothing is recorded for it.

Erase the record on the same page deletes all of it at once. Notices already owed go with it, and no paper bought before then will send one again.

For an organisation

When you work in an organisation, the page shows the organisation's record, not your own. Reading it needs the buyer read role. Setting the webhook or erasing the record needs the role that manages the organisation's wallet, and both are written to the organisation's audit log.