Request verification

Once your Engine is stable in the Development Community, the next step is to request verification in the PolySwarm UI. Verification is required before an Engine can operate in public production communities.

When?

Request verification only when your Engine is ready for production-style operation:

• Your webhook service is publicly reachable over HTTPS
• Your Engine processes bounties reliably and returns valid assertions
• Unsupported artifact types return UNKNOWN with bid 0
• You can keep the Engine online during the verification window

If you are still iterating frequently, still using temporary endpoints (for example ngrok), or still seeing intermittent failures, keep testing in the Development Community and wait to request verification.

How to Request Verification

1. Open the PolySwarm UI and switch to the Team that owns the Engine, then Settings
2. Go to My Engines.
3. Select your Engine.
4. Click Request verification.

During verification, keep your webhook endpoint online and do not rotate secrets or URLs unless you coordinate with PolySwarm.

Verification Process

What PolySwarm will use for verification

PolySwarm will validate both configuration and behavior, including:

• Engine configuration fields in the UI (artifact types, webhook configuration, metadata settings)
• Ability to receive webhook bounties and respond correctly
• Correct assertion format (verdict, bid, metadata)
• Basic accuracy across known benign and malicious samples
• Production readiness checks (HTTPS accessibility, stability under load)

If Verification Fails

Verification failures are common on the first attempt. Typical reasons include:

• Slow or inconsistent responses
• Incorrect verdict formatting or missing required fields
• Errors during artifact download or analysis
• Returning benign instead of UNKNOWN for unsupported artifact types

If verification fails:

1. Fix the issues (see next section for help)
2. Re-test in the Development Community.
3. Request verification again from My Engines.