Claw Trust Scores logo Claw Trust Scores

API Docs

Drop-in trust checks for agent workflows. Use one API key and these endpoints to log events, read trust + behavior scores, gate actions, and export audit trails.

Base URL https://clawtrustscores.com

What This Does

Before your app sends money, shares keys, or runs risky actions, this service tells you whether the other agent looks safe, risky, or needs review.

3 Steps

1. Get your API key

Use the signup form on the homepage. You will get a key like claw_xxx. Copy it immediately (shown once, not emailed) and put it in your backend/server config as an environment variable (for example CLAWTRUST_API_KEY).

CLAWTRUST_API_KEY=INSERT_YOUR_API_KEY_HERE
2. Ask for trust + behavior scores

Your backend sends the API call with header x-api-key. You get trust score (risk), behavior score (reliability), explanation, and signalQuality.

3. Make a decision

Use the score or preflight endpoint to allow, review, or block. Trigger this before risky actions (payment, key share, tool execution).

Exactly Where To Put The Key

# backend .env file
CLAWTRUST_API_KEY=INSERT_YOUR_API_KEY_HERE
# OpenClaw skill config
{
  "env": {
    "CLAWTRUST_API_KEY": "INSERT_YOUR_API_KEY_HERE"
  }
}

Put the key on your agent server/machine. Do not put it in frontend browser code.

Try It Now (No Coding)

Result will appear here.

This calls GET /v1/score using your key and returns both trust and behavior sections.

Optional: Policy Controls

You can skip this on day one. Default policy works for most teams.

Preset result will appear here.

These actions call /v1/policy/presets/* and /v1/policy. Guardrail means sensitive payment/security events must come from verified integrations.

You can also set minSignalQuality (0-100) in POST /v1/policy to force review when score quality is too weak.

For high-risk actions, you can require portable credentials by setting requiredAttestations, requireAttestationsForRiskAbove, and attestationFailureDecision in POST /v1/policy.

If you just want to launch fast, start with: /v1/events, /v1/score, /v1/integrations/clawcredit/preflight, and /v1/usage.
Where to add your key: in your app/backend env vars, bot server config, or workflow tool secrets (Zapier/Make/n8n). Do not paste API keys into public frontend code or chat messages.