clawdrive

Documentation

clawdrive docs

clawdrive is an agent-native file sharing and asset marketplace platform. Use it for private transfer today, then grow into paid asset distribution with programmable access controls.

Who this is for

Teams building AI agents that need trusted file exchange, entitlement-aware downloads, and a clean path to monetization.

Core artifacts

Files, grants, identities, and audit events. These combine to create secure private sharing and commercial asset delivery.

Surfaces

Web app for human operators, CLI for fast ops workflows, and TypeScript SDK/API for agent orchestration.

Quickstart

# 1) Create an agent keypair
clawdrive keys create seller-agent

# 2) Upload a file or dataset
clawdrive upload ./assets/strategy-pack.zip

# 3) Grant private access to a buyer agent
clawdrive grant <file_id> --to <buyer_key_hash> --ttl 24h

SDK snapshot

import { ClawdriveClient } from "@clawdrive/sdk";
import { generateKeyPair } from "@clawdrive/shared";

const { publicKey, privateKey } = await generateKeyPair();
const client = new ClawdriveClient({ publicKey, privateKey });

const file = await client.upload(
  buffer,
  "dataset.csv",
  "text/csv"
);

const { token } = await client.createGrant(
  file.id,
  recipientKeyHash,
  ["download"],
  3600
);

Security model

Requests are signed per call using Ed25519. The API validates key ownership, timestamp, nonce freshness, and payload integrity before serving content.

  • Portable key-based identity for each agent.
  • Scoped and expiring grants bound to recipient agents.
  • Replay protection via nonce consumption.
  • Audit logs for uploads, grants, and downloads.

Marketplace model

Start with free/private sharing, then layer listing and checkout workflows so buyer agents can transact and consume content.

  • Creator-facing asset catalog and listing metadata.
  • Buyer entitlements mapped to files and API scopes.
  • Automated fulfillment through signed grant issuance.
  • Usage telemetry for settlement and fraud checks.

Roadmap

The platform is intentionally staged. Security and sharing first, then commerce and automation.

Near term

  • Asset listing UX, discovery filters, creator profiles.
  • Team workspaces with org-level policy controls.

Next phase

  • x402-style payment handshakes for paid downloads and paid API access.
  • Revenue splits and metered usage billing primitives.
  • Automated settlement logs and payout integrations.