INTEGRATION GUIDE · BETA · SOURCE CHECKED 16 NOV 2026
Migrate PHP 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.
Stajor/perspectiveapi stores its endpoint in a class constant (PHP wrapper URL and constructor). Its request method uses self::API_URL, so changing a subclass constant is not an endpoint override. Maintain a fork or use a direct HTTP client.
2. Change the endpoint and key
Wrapper patch
- const API_URL = 'https://commentanalyzer.googleapis.com/v1alpha1';
+ const API_URL = 'https://moderation.decisionmodels.io/v1alpha1';Construct CommentsClient with your Decision Models key instead of the Google token. The inspected wrapper disables certificate verification. Correct that line in the same maintained fork; do not carry it into production:
- 'verify' => false,
+ 'verify' => true,Plain Guzzle
Save as smoke.php in a project with Guzzle installed:
<?php
require 'vendor/autoload.php';
$client = new GuzzleHttp\Client(['timeout' => 15, 'connect_timeout' => 3]);
$response = $client->post(
'https://moderation.decisionmodels.io/v1alpha1/comments:analyze', [
'headers' => ['Authorization' => 'Bearer ' . getenv('DM_MODERATION_KEY')],
'json' => ['comment' => ['text' => 'Thank you for explaining.'],
'requestedAttributes' => ['TOXICITY' => new stdClass()],
'doNotStore' => true]
]);
$data = json_decode((string) $response->getBody(), true, 512, JSON_THROW_ON_ERROR);
echo $data['attributeScores']['TOXICITY']['summaryScore']['value'], PHP_EOL;Without Guzzle, use the plain curl command in the test section or the PHP cURL example.
Attributes and compatibility
The wrapper’s requestedAttributes setter takes your attribute map; it has no default moderation attribute set. The Guzzle example requests built-in TOXICITY. Use empty objects, not JSON arrays, for attribute options.
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 does not implement a flagging threshold. It passes requestedAttributes through to the API. Find your application’s score comparisons and scoreThreshold options before switching providers.
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}'php smoke.phpFor the wrapper path, exercise both analyze() and suggestScore() if your application uses them. Confirm error responses remain errors rather than approving the comment.
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 can send context and feedback fields; the replacement does not use contextual conversation entries for scoring or store suggested-score feedback. Treat only whole-text spans as available. Roll back your maintained package revision, application settings and key 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.
PHP wrapper URL and constructor · attribute options · transport, TLS and self::API_URL