Detect possible plugin conflicts API

Flag duplicate active plugin slugs and caller-supplied conflict pairs. A match is not a confirmed runtime conflict.

The Detect possible plugin conflicts operation is part of the WordPress Fleet Intelligence API on BRAINIAC.software. Flag duplicate active plugin slugs and caller-supplied conflict pairs. A match is not a confirmed runtime conflict. It is exposed as POST /api/v1/wordpress-fleet/plugin-conflict-detect and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied site inventories WordPress.org public plugin and theme metadata Limitations: Inventories are copied only from labeled fields in the request. Public release data comes from the caller or WordPress.org metadata. An older version is a version-age warning, not a confirmed vulnerability. An update is never marked safe from metadata alone. No WordPress site is logged into or modified. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Normalize a WordPress site inventory, Audit WordPress plugin versions, Audit WordPress theme versions, Check update compatibility metadata. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/wordpress-fleet/plugin-conflict-detect

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/wordpress-fleet/plugin-conflict-detect" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "sites": [
    {
      "id": "S-1"
    }
  ],
  "plugins": [
    {
      "siteId": "S-1",
      "slug": "cache-a",
      "version": "1.0",
      "active": true
    },
    {
      "siteId": "S-1",
      "slug": "cache-b",
      "version": "1.0",
      "active": true
    },
    {
      "siteId": "S-1",
      "slug": "cache-a",
      "version": "1.1",
      "active": true
    }
  ],
  "conflicts": [
    {
      "left": "cache-a",
      "right": "cache-b",
      "detail": "caller says these caches conflict"
    }
  ]
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

WordPress Fleet Intelligence APIFull docsHow it works