Scoring profiles control how VeriSwarm Gate weighs evidence when computing agent trust scores. Every workspace uses a profile -- the default is general, but you can switch to a preset that matches your use case or apply custom weight overrides.
Gate scores agents across four dimensions: Identity, Risk, Reliability, and Autonomy. Each dimension is computed from weighted input signals. A scoring profile defines:
low, moderate, high, and severe labels.When you change your workspace's scoring profile, all future score computations use the new weights. Existing scores are not retroactively recalculated.
Five presets are available out of the box:
general (Default)Balanced evaluation across all dimensions. Suitable for most platforms.
high_securityFor platforms where credential integrity and exploit resistance are paramount -- financial services, infrastructure management, security tooling.
social_platformOptimized for communities, social apps, and content platforms where coordinated abuse and deception are the primary threats.
developer_toolsFor developer platforms, CI/CD integrations, and code-adjacent tooling where task success and tool trace consistency matter most.
marketplaceFor agent marketplaces, app stores, and platform ecosystems where verified identity and community reputation drive trust.
Navigate to Account > Settings and look for the Scoring Profile section.
curl https://veriswarm.ai/v1/suite/scoring/profile \
-H "x-account-access-token: YOUR_SESSION_TOKEN"
Response:
{
"profile_code": "general",
"identity_weights": {
"key_attestation": 0.30,
"domain_verification": 0.20,
"runtime_attestation": 0.20,
"declaration_completeness": 0.15,
"identity_stability": 0.15
},
"risk_weights": {
"policy_violation_rate": 0.25,
"exploit_susceptibility": 0.20,
"coordination_anomaly": 0.20,
"secret_hygiene_failures": 0.15,
"rate_abuse": 0.10,
"deception_flags": 0.10
},
"reliability_weights": {
"task_success": 0.30,
"correction_response": 0.20,
"evidence_integrity": 0.20,
"trusted_endorsements": 0.15,
"incident_free_age": 0.15
},
"autonomy_weights": {
"scheduler_consistency": 0.25,
"tool_trace_consistency": 0.20,
"latency_signature": 0.20,
"self_initiation_ratio": 0.15,
"low_human_override": 0.10,
"session_continuity": 0.10
},
"composite_weights": {
"identity": 0.35,
"reliability": 0.25,
"risk_inverse": 0.20,
"autonomy": 0.20
},
"tier_thresholds": {
"tier_3": {"min_identity": 80, "max_risk": 20, "min_reliability": 80},
"tier_2": {"min_identity": 55, "max_risk": 35, "min_reliability": 60},
"tier_0": {"max_identity": 30, "max_reliability": 30}
},
"risk_bands": {
"low": [0, 20],
"moderate": [21, 49],
"high": [50, 74],
"severe": [75, 100]
},
"available_presets": ["general", "high_security", "social_platform", "developer_tools", "marketplace"]
}
Requires admin or owner role. Changing the profile takes effect on the next score computation for each agent.
curl -X POST https://veriswarm.ai/v1/suite/scoring/profile \
-H "x-account-access-token: YOUR_SESSION_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"profile_code": "high_security"
}'
You can start from any preset and selectively override specific weights. Overrides are merged with the base preset -- you only need to specify the weights you want to change.
curl -X POST https://veriswarm.ai/v1/suite/scoring/profile \
-H "x-account-access-token: YOUR_SESSION_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"profile_code": "general",
"weight_overrides": {
"risk": {
"policy_violation_rate": 0.30,
"exploit_susceptibility": 0.25,
"coordination_anomaly": 0.15,
"secret_hygiene_failures": 0.15,
"rate_abuse": 0.10,
"deception_flags": 0.05
}
}
}'
The weight_overrides structure:
{
"identity": { "signal_name": weight, ... },
"risk": { "signal_name": weight, ... },
"reliability": { "signal_name": weight, ... },
"autonomy": { "signal_name": weight, ... },
"composite": { "dimension_name": weight, ... }
}
All keys are optional. Only include the categories you want to override. Within each category, the overridden weights are merged with the preset's defaults.
Validation: Weights within each category must sum to exactly 1.0. The API returns a 422 Unprocessable Entity error with details if the resulting weights are invalid.
| Signal | Description |
|---|---|
key_attestation |
Strength of cryptographic key evidence |
domain_verification |
Whether the agent's claimed domain is verified |
runtime_attestation |
Evidence from the agent's runtime environment |
declaration_completeness |
How complete the agent's manifest/profile is |
identity_stability |
Consistency of identity signals over time |
| Signal | Description |
|---|---|
policy_violation_rate |
Frequency of policy rule violations |
exploit_susceptibility |
Vulnerability to known exploit patterns |
coordination_anomaly |
Suspicious coordinated behavior with other agents |
secret_hygiene_failures |
Exposed credentials, leaked secrets |
rate_abuse |
Excessive request rates or API abuse |
deception_flags |
Indicators of deceptive behavior |
| Signal | Description |
|---|---|
task_success |
Task completion rate |
correction_response |
How well the agent responds to corrections |
evidence_integrity |
Consistency and integrity of submitted evidence |
trusted_endorsements |
Endorsements from other trusted agents |
incident_free_age |
Duration since last incident |
| Signal | Description |
|---|---|
scheduler_consistency |
Regularity of autonomous scheduling |
tool_trace_consistency |
Consistency in tool usage patterns |
latency_signature |
Response time patterns indicating automation |
self_initiation_ratio |
Ratio of self-initiated vs requested actions |
low_human_override |
Infrequency of human intervention |
session_continuity |
Ability to maintain long-running sessions |
weight_overrides are applied on top of the new base preset. Set weight_overrides to null to clear them.