INTEGRATION GUIDE · BETA · SOURCE CHECKED 16 NOV 2026
Migrate Node.js from the Perspective API (before 31 Dec 2026)
Perspective-shaped requests, independent scores. Change the connection, then validate the moderation decisions.
Google’s Perspective API notice gives 31 December 2026 as the shutdown date. Plan and test your migration before then.
1. Prepare a staging copy
Save the integration version, settings, current thresholds and old scores before changing providers. Create a Decision Models key in the dashboard; store it only on your server. Examples use environment variables, never real keys.
npm perspective-api-client (sloria) posts to the wrapper host constant; its constructor does not provide an endpoint override in the inspected revision. This is a specific package, not every Node Perspective client.
2. Change the endpoint and key
Option A: maintained wrapper patch
Patch index.js in a maintained fork or a reproducible dependency patch, then pass your Decision Models key as the existing apiKey option. Direct node_modules edits will be lost on reinstall.
- 'https://commentanalyzer.googleapis.com/v1alpha1/comments:analyze';
+ 'https://moderation.decisionmodels.io/v1alpha1/comments:analyze';Option B: plain fetch
On a Node runtime with built-in fetch and AbortSignal.timeout, save the following as smoke.mjs. Keep the key on the server; never ship it in a browser bundle.
async function analyze(text) {
const response = await fetch(
"https://moderation.decisionmodels.io/v1alpha1/comments:analyze", {
method: "POST",
headers: {"Content-Type": "application/json",
Authorization: `Bearer ${process.env.DM_MODERATION_KEY}`},
body: JSON.stringify({comment: {text},
requestedAttributes: {TOXICITY: {}}, doNotStore: true}),
signal: AbortSignal.timeout(15000)
});
if (!response.ok) throw new Error(`Moderation HTTP ${response.status}`);
return response.json();
}
const result = await analyze("Thank you for explaining.");
console.log(result.attributeScores.TOXICITY.summaryScore.value);Attributes and compatibility
The wrapper defaults to TOXICITY when neither an attributes option nor a requestedAttributes map is supplied. That is built-in here. The attributes option can choose other names; audit them. Payload defaults also show HTML stripping by default. The fetch example sends raw plain text and does not reproduce wrapper preprocessing.
Built-in and experimental attribute names
Built-in: TOXICITY, IDENTITY_ATTACK, INSULT, PROFANITY, THREAT. Built-in does not mean score parity with Perspective.
Experimental, not evaluated and uncalibrated: SEVERE_TOXICITY, SEXUALLY_EXPLICIT, FLIRTATION, SPAM, ATTACK_ON_AUTHOR, ATTACK_ON_COMMENTER, INCOHERENT, INFLAMMATORY, LIKELY_TO_REJECT, OBSCENE, UNSUBSTANTIAL. Responses identify requested experimental attributes in X-DM-Experimental-Attributes. Unknown attributes return 400. Check the current attribute and language documentation before enabling automatic actions.
Re-tune the thresholds
The wrapper returns scores and has no automatic flag/delete threshold. Inspect caller code for score comparisons and optional scoreThreshold request fields. The fetch example deliberately makes no moderation decision.
Use the migration tool with representative comments, their saved Perspective scores and optional human labels. Compare flag rates, flagged-set overlap and, where labels exist, precision and recall. Matching a flag rate does not guarantee the same flagged comments or accuracy. Tune each attribute and action separately; do not copy the old numbers into production without review.
3. Test and re-tune
With DM_MODERATION_KEY set privately, this smoke command should return HTTP 200 and a numeric attributeScores.TOXICITY.summaryScore.value between 0 and 1. It checks transport and response shape, not moderation quality.
curl --fail-with-body --max-time 15 \
'https://moderation.decisionmodels.io/v1alpha1/comments:analyze' \
-H "Authorization: Bearer $DM_MODERATION_KEY" \
-H 'Content-Type: application/json' \
--data '{"comment":{"text":"Thank you for explaining."},"requestedAttributes":{"TOXICITY":{}},"doNotStore":true}'node smoke.mjsFor the patched wrapper, run your existing analyze call with the new apiKey and assert a numeric summaryScore. Compare inputs after HTML stripping or truncation; a changed input is a second source of score changes.
In staging, test benign, abusive, borderline, quoted and multilingual comments; compare actual queue or warning actions with human decisions. Also test invalid keys, untested-language warnings, 429 rate limits and a timeout. Keep a manual moderation fallback rather than interpreting a failed request as a safe score. Check limits and errors and plan quotas and request rates.
4. Roll out with a fallback
The wrapper’s length check uses JavaScript string length; the API limit is UTF-8 bytes. Validate multibyte text against the byte limit. Keep wrapper behavior tests if replacing it with fetch. Roll back the dependency lockfile and code together.
Keep the saved version and settings so you can reverse this change. Before Google’s shutdown, you can restore the Google endpoint together with its Google key and old thresholds if that service remains available to your account. After shutdown, use a tested alternative or manual review. Never send a Decision Models key to the Google host, or a Google key to Decision Models.
Shared gaps: scores come from an independent model; sentence-level span annotations are unavailable (one whole-text span only). Only PLAIN_TEXT is accepted. Valid explicit language hints are accepted and echoed. Untested hints or detected languages carry X-DM-Language-Untested. Tested languages: English (5 attributes) and German (offensive-language proxy only). This is not evidence of language quality. Suggested-score feedback is acknowledged but not stored or used to train the model. See the full API contract.
Source notes
These instructions follow the linked source revisions, inspected on 16 November 2026. Your installed release may differ. Patches and examples are migration recipes, not upstream endorsements or a claim of an end-to-end verified integration.
wrapper host constant · constructor, request and payload behavior