Drip Openclaw Billing

Drip OpenClaw Billing Skill

Use this skill to instrument OpenClaw requests with Drip so usage is traceable and billable.

Prerequisites

• DRIP_API_KEY configured
• DRIP_BASE_URL configured to your official trusted Drip API domain
• DRIP_WORKFLOW_ID configured for POST /v1/runs
• OPENCLAW_DEFAULT_CUSTOMER_ID configured if requests may omit explicit customerId
• OPENCLAW_TELEMETRY_FAIL_OPEN configured to match your policy (true for fail-open, false for fail-closed)
• A valid customerId for the requesting user/tenant
• OpenClaw runtime hook points for request start/end and tool-call boundaries

Required Credentials (Authoritative)

• Required env vars:
  • DRIP_API_KEY (primary credential)
  • DRIP_BASE_URL (trusted Drip API host)
  • DRIP_WORKFLOW_ID
• Optional env vars:
  • OPENCLAW_DEFAULT_CUSTOMER_ID
  • OPENCLAW_TELEMETRY_FAIL_OPEN
  • OPENCLAW_BILL_SKILL_CALLS

Provider keys like BRAVE_API_KEY or GOOGLE_API_KEY are not required by this billing skill itself. Only provide them if your own agent runtime directly calls those providers.

ClawHub Deployment Contract

• Keep this skill isolated from the core product flow; invoke only from OpenClaw-specific execution paths.
• Resolve customerId from ClawHub tenant/user identity at runtime.
• Pass stable idempotency keys for events and usage writes to avoid double charges on retries.
• Set allow_implicit_invocation: false in agents/openai.yaml so this skill only runs when explicitly invoked.
• Verify DRIP_BASE_URL points to an official trusted Drip endpoint before enabling production traffic.

ClawHub Runtime Settings (Recommended)

• Model: gpt-5 (or your production default with tool-calling enabled)
• Timeout: at least 60s for run + tool + usage emissions
• Retry policy: 2 retries with backoff on transient Drip write failures
• Invocation mode: explicit invocation only ($drip-openclaw-billing)

Required Integration Pattern

For each OpenClaw request:

1. Start run with POST /v1/runs
2. After each external tool/API call, emit POST /v1/events
3. If billable, emit POST /v1/usage (or /v1/usage/async)
4. End run with PATCH /v1/runs/:id

Telemetry Data Minimization (MUST)

Only send the minimum execution metadata needed for billing and diagnostics:

• Allowed metadata fields:
  • integration, requestId, provider, endpoint, statusCode, latencyMs, queryHash, tokens
  • source, action, tenantId, requesterId, runId, workflowId, error
• Prohibited metadata fields:
  • raw query text
  • raw prompts or model outputs
  • authorization headers
  • API keys, passwords, secrets
  • full request/response payload bodies

If query context is required, send only queryHash (sha256), never raw query text.

SDK Option (Recommended)

import { OpenClawBilling } from '@drip-sdk/node/openclaw';

const billing = new OpenClawBilling({
  apiKey: process.env.DRIP_API_KEY,
  customerId: 'cus_123',
  workflowId: 'wf_openclaw',
});

await billing.withRun(
  { externalRunId: 'openclaw_req_456' },
  async ({ runId }) => {
    await billing.withToolCall(
      {
        runId,
        provider: 'brave',
        endpoint: '/res/v1/web/search',
        query: 'best usdc billing api',
      },
      async () => {
        return fetch('https://api.search.brave.com/res/v1/web/search?q=best+usdc+billing+api');
      },
    );
  },
);

Raw API Option

Start run

POST /v1/runs

{
  "customerId": "cus_123",
  "workflowId": "wf_openclaw",
  "externalRunId": "openclaw_req_456",
  "metadata": { "integration": "openclaw" }
}

Emit tool event

POST /v1/events

{
  "customerId": "cus_123",
  "runId": "run_abc",
  "actionName": "google_search",
  "eventType": "TOOL_CALL",
  "outcome": "SUCCEEDED",
  "quantity": 1,
  "idempotencyKey": "openclaw_run_abc_google_search_001",
  "metadata": {
    "provider": "google",
    "endpoint": "/customsearch/v1",
    "statusCode": 200,
    "latencyMs": 285,
    "queryHash": "f2a9ad...",
    "tokens": 0
  }
}

Emit billable usage

POST /v1/usage

{
  "customerId": "cus_123",
  "usageType": "google_api_calls",
  "quantity": 1,
  "idempotencyKey": "openclaw_run_abc_google_search_001_usage",
  "metadata": {
    "runId": "run_abc",
    "provider": "google",
    "statusCode": 200,
    "latencyMs": 285
  }
}

End run

PATCH /v1/runs/:id

{ "status": "COMPLETED" }

On failure:

{
  "status": "FAILED",
  "errorMessage": "Provider timeout",
  "errorCode": "TOOL_TIMEOUT"
}

Mapping Guidance

• actionName: brave_search, google_search, <provider>_call
• eventType: usually TOOL_CALL or API_CALL
• usageType: api_calls or provider-specific meters like brave_api_calls
• quantity: normally 1, unless metering request units

References

• API examples: references/API.md
• Integration doc: docs/integration/openclaw-integration.md
• ClawHub deployment metadata: agents/clawhub.yaml
• ClawHub deploy/test runbook: OPENCLAW_CLAWHUB_DEPLOY_AND_TEST.md