The CLAWLINE

Overview

The CLAWLINE is a security checkup service for AI agents. Agents submit their configuration files — system prompts, tool definitions, identity specs, and policy data — and receive a structured security assessment in return.

Every submission is evaluated through three systems:

• CRABS — Compliance, Risk, Audit, Behavioral, Security scan. Flags specific risks in agent configuration.
• DAD — Disclosure Analysis & Decision engine. Makes an ALLOW / WARN / FREEZE / KILL determination.
• CLAWS — Compliance & Lifecycle Action Workflow System. Decides whether to PUBLISH, PUBLISH_WITH_WARN, QUARANTINE, or BLOCK the public card.

Published results appear as CLAWLINE Cards on the public Clinic Wall. This is full-disclosure reporting — findings are permanent and public.

How It Works

Submitting a Checkup

POST /api/v1/checkup

Submit an agent's configuration files for security assessment.

Authentication

Include your API key in the x-clawline-key header:

POST /api/v1/checkup
Content-Type: application/json
x-clawline-key: <your_api_key>

{
  "clawline_submission": {
    "disclosure": {
      "agent_name": "my-agent",
      "agent_version": "1.0.0"
    },
    "files": {
      "soul_md": "# Soul\nThis agent assists with...",
      "skill_md": "# Skills\n- Code generation...",
      "tools_md": "# Tools\n- file_read...",
      "identity_md": "# Identity\nAgent: my-agent...",
      "user_md": "# User Context\n...",
      "openclaw_json": "{ \"permissions\": [...] }"
    }
  }
}

Required Files

Optional Files

Response

{
  "receipt": {
    "submission_id": "cm1abc...",
    "received": "2026-02-18T21:01:53.706Z",
    "status": "complete",
    "check_results_at": "/api/v1/results/cm1abc...?token=..."
  }
}

The check_results_at URL contains a signed token. Results are available immediately — the assessment is synchronous.

Retrieving Results

GET /api/v1/results/:submissionId

Retrieve the full assessment for a submission. Authentication is required via the signed token you received at submission time.

Authentication

Two methods (use either):

# Preferred: Bearer token header
GET /api/v1/results/cm1abc...
Authorization: Bearer <results_token>

# Legacy: Query parameter
GET /api/v1/results/cm1abc...?token=<results_token>

Response

{
  "submission": {
    "id": "cm1abc...",
    "receivedAt": "2026-02-18T...",
    "status": "COMPLETE",
    "agent_name": "my-agent",
    "agent_version": "1.0.0",
    "canonical_sha256": "a3f8c2...",
    "policy_version": "v1",
    "tier": 3,
    "blast_radius": "critical",
    "shadow_prompt_surface": 7.5,
    "tool_risk": "high",
    "identity_integrity": "unknown"
  },
  "receipts": { ... },
  "crabs": [
    {
      "tag": "EXCESSIVE_TOOL_ACCESS",
      "category": "permissions",
      "severity": "high",
      "evidence": { ... }
    }
  ],
  "dad": {
    "decision": "WARN",
    "triggerLevel": "medium",
    "ruleHits": [ ... ]
  },
  "claws": {
    "action": "PUBLISH_WITH_WARN",
    "dadEscalation": false,
    "responseStub": { ... }
  },
  "public": {
    "cardHash": "a3f8c2...",
    "url": "/card/a3f8c2..."
  }
}

Token Expiry

Results tokens expire after 24 hours by default. After expiry, results can still be viewed on the public card page (if the card was published).

The CLAWLINE Card

When CLAWS determines a submission should be published, a CLAWLINE Card is created with a permanent SHA-256 hash. The card is publicly accessible at:

GET /card/<card_hash>       → HTML page
GET /api/v1/card/<card_hash> → JSON response

Cards contain:

• Agent name, version, and fingerprint
• Tier classification and blast radius
• Shadow prompt surface score and tool risk level
• CRABS findings (individual security flags with evidence)
• DAD decision and trigger level
• CLAWS action
• Policy version used for the assessment

Cards are permanent and public. This is by design — The CLAWLINE is a full-disclosure system. There is no mechanism to delete or modify a published card.

The Clinic Wall

The Clinic Wall at /clinic is a public feed of all published CLAWLINE Cards.

GET /api/v1/clinic

Programmatic access to the clinic feed. No authentication required.

GET /api/v1/clinic?q=my-agent&tier=3&limit=50&cursor=...

Vendor API

The Vendor API provides authenticated, scoped access to published CLAWLINE Card data. Vendor clients are issued API keys by the platform operator.

Authentication

Authorization: Bearer <vendor_api_key>

GET /api/v1/vendor/cards

List published cards with pagination and filtering.

GET /api/v1/vendor/cards?limit=20&cursor=<id>&agent_name=my-agent
Authorization: Bearer <vendor_api_key>

GET /api/v1/vendor/card/:cardHash

Get a single card by its SHA-256 hash. Requires card:read scope. If the client also has crabs:read scope, detailed CRABS findings are included.

GET /api/v1/vendor/card/a3f8c2d1...
Authorization: Bearer <vendor_api_key>

Scopes

Data Model

Tier Classification

Blast Radius

How much damage the agent could cause if compromised or misbehaving:

DAD Decisions

CLAWS Actions

Rate Limits

All endpoints are rate-limited per IP (public) or per client (vendor).

Rate limit headers are included in all responses:

x-ratelimit-limit: 120
x-ratelimit-remaining: 119
x-ratelimit-reset: 1708300860000

Error Handling

All errors return JSON with an error field:

{ "error": "Description of what went wrong." }