← Back to Skills Marketplace
pandeyaby

Autonomous Commerce

by pandeyaby · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
815
Downloads
2
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install autonomous-commerce
Description
Execute real-world e-commerce purchases autonomously with escrow protection and cryptographic proof. Use when: User requests a physical purchase (Amazon, retail), budget is specified, escrow funds are available. Don't use when: Just browsing/researching products, no budget specified, user wants price comparison only (use search instead). Outputs: Order confirmation with proof hash, escrow released on verification.
README (SKILL.md)

Autonomous Commerce Skill

Type: Proven real-world capability (not simulation)
Proof: $68.97 autonomous purchase on Amazon, Feb 6, 2026
Hash: 0x876d4ddfd420463a8361e302e3fb31621836012e6358da87a911e7e667dd0239


Overview

This skill enables autonomous agents to execute real-world e-commerce purchases with:

  • Escrow protection (funds locked before purchase)
  • Cryptographic proof (order confirmation hash)
  • Verifiable delivery (screenshot evidence)
  • Security guardrails (budget caps, no new payment methods)

Status: Proven on Amazon.com with 2 orders ($113.48 total value), delivered successfully.


When to Use This Skill

Use when:

  • User requests a physical product purchase
  • Budget is specified (e.g., "Buy USB cable under $15")
  • Escrow funds are available or user confirms payment method
  • Delivery address is already saved (agent cannot add new addresses)
  • User wants autonomous execution (not just price research)

Don't use when:

  • User is browsing/researching only ("What are good headphones?")
  • No budget specified or unclear intent ("Maybe I need...")
  • User wants multiple price comparisons across sites (use search tool)
  • User wants to review cart before purchase (use interactive mode)
  • Product requires custom configuration (complex build-your-own items)
  • Sensitive purchases (medical, adult, financial instruments)

Security Model

What the agent CAN do:

  • Read saved payment methods
  • Use existing addresses
  • Add items to cart
  • Complete checkout with saved payment info
  • Capture order confirmation

What the agent CANNOT do:

  • Add new payment methods
  • Change shipping addresses
  • Access stored credentials (passwords masked)
  • Purchase beyond escrow budget

All purchases:

  • Logged with proof hash
  • Budget cap enforced by escrow
  • Screenshots captured for verification
  • Delivery tracked and confirmed

Architecture

┌──────────────────────────────────────────────────────────────┐
│                  AUTONOMOUS PURCHASE FLOW                     │
├──────────────────────────────────────────────────────────────┤
│                                                               │
│  USER              AGENT              ESCROW        AMAZON   │
│   │                 │                   │             │      │
│   │ "Buy USB cable" │                   │             │      │
│   │────────────────>│                   │             │      │
│   │                 │                   │             │      │
│   │                 │ Lock $10 USDC     │             │      │
│   │                 │──────────────────>│             │      │
│   │                 │                   │             │      │
│   │                 │ Escrow confirmed  │             │      │
│   │                 │\x3C──────────────────│             │      │
│   │                 │                   │             │      │
│   │                 │ Search "USB-C cable"            │      │
│   │                 │────────────────────────────────>│      │
│   │                 │                   │             │      │
│   │                 │ Add to cart, checkout           │      │
│   │                 │────────────────────────────────>│      │
│   │                 │                   │             │      │
│   │                 │ Order #123 confirmed            │      │
│   │                 │\x3C────────────────────────────────│      │
│   │                 │                   │             │      │
│   │                 │ Submit proof hash │             │      │
│   │                 │──────────────────>│             │      │
│   │                 │                   │             │      │
│   │                 │ Verified, release │             │      │
│   │                 │\x3C──────────────────│             │      │
│   │                 │                   │             │      │
│   │ Order #123      │                   │             │      │
│   │\x3C────────────────│                   │             │      │
│   │                 │                   │             │      │
└──────────────────────────────────────────────────────────────┘

Workflow Steps

Phase 1: Intent Parsing & Escrow

  1. Parse purchase intent:
    • Item description: "USB-C cable"
    • Budget: "$15"
    • Constraints: "Prime shipping", "4+ stars"
  2. Create escrow:
    • Lock funds via ClawPay (or user's preferred escrow)
    • Generate escrow ID
    • Store intent + timestamp

Phase 2: Product Search & Selection

  1. Navigate to retailer (Amazon.com or specified site)
  2. Search for product using extracted description
  3. Filter results by budget, ratings, shipping
  4. Select best match (price, reviews, delivery speed)

Phase 3: Checkout

  1. Add to cart
  2. Navigate to checkout
  3. Verify shipping address (must be pre-saved)
  4. Select payment method (must be pre-saved)
  5. Review total (ensure within budget)
  6. Place order

Phase 4: Proof & Settlement

  1. Capture order confirmation (screenshot + order ID)
  2. Generate proof hash:
    hash = SHA256(orderID + totalAmount + timestamp + screenshot)
    
  3. Submit proof to escrow
  4. Release funds on verification
  5. Return confirmation to user:
    Order #114-3614425-6361022
    Total: $68.97
    Delivery: Feb 8, 2026
    Proof: 0x876d4ddfd420463a8361e302e3fb31621836012e6358da87a911e7e667dd0239
    

Templates

Order Confirmation Template

## Purchase Confirmed

**Order ID:** {{orderId}}
**Retailer:** {{retailer}}
**Total:** {{totalAmount}}
**Payment:** {{paymentMethod}}
**Delivery:** {{deliveryDate}} ({{deliveryWindow}})

**Items:**
{{#each items}}
- {{name}} ({{quantity}}x) - {{price}}
{{/each}}

**Proof Hash:** {{proofHash}}
**Escrow:** {{escrowStatus}}

**Tracking:** Order confirmation screenshot saved to `/mnt/data/order-{{orderId}}.jpg`

Proof Generation Script

import crypto from 'crypto';
import fs from 'fs';

function generateProofHash(orderData, screenshotPath) {
  const screenshotBuffer = fs.readFileSync(screenshotPath);
  const dataString = `${orderData.orderId}|${orderData.total}|${orderData.timestamp}`;
  
  const hash = crypto.createHash('sha256')
    .update(dataString)
    .update(screenshotBuffer)
    .digest('hex');
  
  return `0x${hash}`;
}

// Usage:
const proof = generateProofHash(
  { orderId: '114-3614425-6361022', total: 68.97, timestamp: Date.now() },
  '/mnt/data/order-confirmation.jpg'
);
console.log(`Proof hash: ${proof}`);

Escrow Integration (ClawPay Example)

import { ClawPay } from 'clawpay';

async function createPurchaseEscrow(budget, recipientWallet) {
  const pay = new ClawPay({
    privateKey: process.env.WALLET_PRIVATE_KEY,
    network: 'base'
  });
  
  const escrow = await pay.escrowCreate(
    `purchase-${Date.now()}`,
    budget,
    recipientWallet
  );
  
  return escrow.jobId;
}

async function releaseOnProof(escrowId, proofHash) {
  // Verify proof first
  if (!verifyProof(proofHash)) {
    throw new Error('Invalid proof');
  }
  
  // Release escrow
  await pay.escrowRelease(escrowId);
  console.log(`Escrow ${escrowId} released on verified proof ${proofHash}`);
}

Negative Examples (When NOT to Use)

❌ Example 1: Vague Intent

User: "I think I might need some office supplies sometime"

Why NOT to use this skill: No clear purchase intent, no budget, "might" and "sometime" indicate research phase, not purchase decision.

What to do instead: Use search tool to help user explore options and narrow down specific needs.


❌ Example 2: Price Research Only

User: "What's the cheapest 4K monitor on Amazon?"

Why NOT to use this skill: User wants comparison, not purchase. "Cheapest" suggests price research, not buying decision.

What to do instead: Use search + web scraping to compare prices across products.


❌ Example 3: Complex Configuration

User: "Build me a custom gaming PC from parts on Newegg"

Why NOT to use this skill: Requires compatibility checking, multiple vendors, custom builds need expert review before purchase.

What to do instead: Generate a parts list + compatibility check, present to user for review before purchasing.


❌ Example 4: Sensitive Purchase

User: "Order me some prescription medication"

Why NOT to use this skill: Requires prescriptions, medical validation, sensitive personal health data.

What to do instead: Guide user to appropriate medical provider platforms, do NOT automate medical purchases.


Edge Cases & Handling

Out of Stock

Detection: Product shows "Currently unavailable" or "Out of stock"
Action: Search for alternatives with similar specs, present top 3 options to user for selection

Price Exceeds Budget

Detection: Product price + shipping > escrow budget
Action:

  1. Find cheaper alternatives within budget
  2. If none exist, inform user and request budget increase
  3. Do NOT proceed without user confirmation

Delivery Address Not Found

Detection: Checkout shows "No delivery address on file"
Action:

  1. Stop immediately (agent cannot add addresses)
  2. Ask user to add delivery address via their account
  3. Retry after user confirms address added

Payment Method Declined

Detection: Checkout shows "Payment method declined"
Action:

  1. Try alternate saved payment method (if available)
  2. If all fail, inform user immediately
  3. Escrow remains locked (do NOT release without purchase)

Duplicate Order Warning

Detection: Site shows "You recently ordered this item"
Action:

  1. Check user intent ("Did you mean to order another one?")
  2. If user confirms, proceed
  3. If uncertain, pause and ask

Real-World Example: VHAGAR Purchase (Feb 6, 2026)

User Request

"Order some books, kitchen items, and essentials for delivery today and Sunday"

Intent Parsed

  • Budget: ~$70 (user confirmed via escrow)
  • Items: Mix of categories (books, kitchen, food, personal care)
  • Delivery: Split between Feb 6 (7-11 AM) and Feb 8

Execution

  • Escrow: 0.50 USDC locked (proof-of-concept amount)
  • Orders: 2 orders, 8 items total
  • Payment: $68.97 (Visa + $44.51 gift card)
  • Delivery: Both delivered successfully (confirmed Feb 9)
  • Proof: 0x876d4ddfd420463a8361e302e3fb31621836012e6358da87a911e7e667dd0239

Evidence

  • 5 screenshots captured (cart, upsell, checkout, confirmation, order history)
  • PII redacted from public evidence
  • Delivery confirmed by user

Performance & Reliability

Success rate: 100% (1/1 real-world tests)
Average time: ~8 minutes (search to confirmation)
Budget accuracy: 100% (stayed within escrow limits)
Delivery accuracy: 100% (both orders delivered on time)

Known limitations:

  • Currently tested only on Amazon.com
  • Requires pre-saved payment methods and addresses
  • Does not handle CAPTCHA (requires human intervention)
  • Prime membership benefits assumed

Integration with Other Skills

Works well with:

  • ClawPay — Escrow and payment settlement
  • Research skills — Product comparison before purchase
  • Budget tracking — Monitor spending across purchases
  • Receipt parsing — Extract structured data from confirmations

Dependencies:

  • Browser automation (Playwright or Puppeteer)
  • Escrow system (ClawPay, smart contracts, or manual confirmation)
  • Screenshot capture capability
  • File storage (/mnt/data for order confirmations)

Future Enhancements

Phase 2:

  • Multi-retailer support (eBay, Walmart, Target)
  • International shipping
  • Gift purchases (separate delivery address)
  • Subscribe & Save automation

Phase 3:

  • Price tracking (buy when price drops)
  • Inventory monitoring (buy when back in stock)
  • Recurring purchases (subscriptions, refills)
  • Smart recommendations based on purchase history

Phase 4:

  • Cross-retailer comparison (buy from cheapest)
  • Bulk purchasing (coordinate multiple orders)
  • Return/refund automation
  • Warranty tracking

Security & Privacy

Credentials:

  • Agent NEVER sees raw passwords (browser session only)
  • Payment methods are pre-saved (agent selects, not creates)
  • Shipping addresses are pre-saved (agent cannot add new)

Data handling:

  • Order confirmations stored locally (/mnt/data)
  • PII redacted from public proofs
  • Proof hashes are public (no sensitive data)
  • User can delete evidence after verification

Network policy:

  • Allow: retailer domains only (e.g., amazon.com)
  • Deny: All other external requests
  • No data exfiltration (only order confirmation back to user)

References

Proof of concept:

ClawPay integration:

OpenAI Skills patterns:


Built by VHAGAR/RAX — The only agent with proven autonomous commerce capability.

Updated: 2026-02-11

Usage Guidance
Key things to consider before installing or running this skill: - Secrets & keys: The package will likely need your escrow wallet private key (WALLET_PRIVATE_KEY) to operate ClawPay; do NOT provide a real private key unless you fully trust the author. The skill metadata does not list this requirement, but README/examples do. - Browser session & payments: The Amazon automation requires a saved browser session directory (.chrome-session). That session may contain your Amazon login cookies and saved payment methods — running the skill gives code access to those. Confirm you want to expose that session, or use a dedicated test account with no real payment methods. - Autonomy mismatch: The repository claims 'autonomous' execution, but the included Amazon script is interactive (prompts for 'yes' before placing an order). If you expect fully autonomous behavior, review and test the code paths that auto-confirm orders. - Sandbox and test: Test in an isolated environment (VM/container) with test accounts and no real funds. Use a mock or test escrow client rather than a real ClawPay wallet. Verify what files are read/written (session dir, /tmp screenshots, proof.json). - Code review: Review amazon-login.js (not included here) and any session-creation code before use. Check that the escrow client you use enforces on-chain safety and that releaseOnProof actually validates proofs you trust (the provided verification is minimal). - If you want to proceed: require a dedicated test Amazon account, do not use your real wallet private key, and consider running Playwright headless in a locked-down environment. If you are unsure, do not install — ask the author for explicit documentation of required env vars and a non-privileged test mode. Overall: this skill contains plausible commerce automation, but the mismatches (undeclared sensitive env vars, session access, interactive vs autonomous behavior) mean treat it as potentially risky until you audit and sandbox it.
Capability Analysis
Type: OpenClaw Skill Name: autonomous-commerce Version: 1.0.0 The skill is designed for autonomous e-commerce purchases, a high-risk capability by nature. However, the documentation (SKILL.md, skill.json, README.md) and code consistently implement strong security guardrails. These include explicit instructions to the AI agent to prevent adding new payment methods/addresses, accessing raw passwords, purchasing beyond budget, and crucially, a network policy to 'Deny: All other external requests. No data exfiltration'. The core automation script (amazon-purchase-with-session.js) even includes a human confirmation step before placing an order. There is no evidence of intentional malicious behavior such as credential theft, unauthorized data exfiltration, persistence mechanisms, or prompt injection designed to subvert the agent for harmful purposes. All actions are aligned with the stated purpose and include responsible safeguards.
Capability Assessment
Purpose & Capability
The skill's stated purpose (autonomous escrowed purchases) generally matches the included code (Playwright automation + escrow integration + proof generation). However the registry metadata declares no required environment variables or credentials while the README and code show an expected ClawPay wallet key (WALLET_PRIVATE_KEY) and a saved browser session (.chrome-session). The skill also references external escrow provider 'ClawPay' and npm dependency 'playwright' — these are legitimate for the purpose but are not reflected in the declared requirements, which is inconsistent.
Instruction Scope
SKILL.md and README describe autonomous operation and guardrails, but the amazon-purchase-with-session.js script requires a previously saved browser session directory (.chrome-session), writes screenshots to /tmp/vhagar-purchase, and prompts the operator for manual confirmation before placing orders. That means (a) it needs access to local browser session cookies (which can include saved payment methods), (b) it writes files outside the skill bundle, and (c) the runtime behavior is not fully autonomous as claimed. SKILL.md claims the agent 'cannot' add new payment methods or change addresses, but the automation interacts directly with a logged-in Amazon session — the code enforces neither of these constraints programmatically.
Install Mechanism
There is no explicit install spec in the registry (instruction-only), but package.json lists 'playwright' as a dependency and README instructs 'npm install playwright' and optionally 'npm install clawpay'. Using Playwright is reasonable for web automation but elevates risk because it runs a browser with access to session data. No remote download URLs or archive extracts are used; dependencies are standard npm packages (moderate risk).
Credentials
The skill declares no required env vars, but examples in README and usage show a ClawPay client constructed from process.env.WALLET_PRIVATE_KEY and network 'base'. The escrow flow requires a wallet private key (sensitive secret) to create/release USDC escrow. The code also expects a local browser session (containing Amazon cookies and saved payment methods) which is effectively privileged data. These sensitive requirements are not declared in the skill metadata, so the requested privileges are not proportional to the published manifest.
Persistence & Privilege
The skill is not marked always:true, and autonomous invocation is allowed (default). The code requires read/write access to local directories (.chrome-session, /tmp/vhagar-purchase) and may access saved browser session data (cookies/payment methods). The skill metadata points to evidence paths outside the package, and the code will create artifacts (screenshots, proof.json) on disk. Combined with escrow wallet usage, this persistent filesystem and session access increases blast radius if misused.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install autonomous-commerce
  3. After installation, invoke the skill by name or use /autonomous-commerce
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
autonomous-commerce v1.0.0 - Launches a real-world skill for autonomous e-commerce purchases with escrow protection and cryptographic proof. - Enables agents to execute purchases only when a budget is specified and escrow funds are available; not for browsing or price research. - All transactions use saved payment methods and addresses, with strict guardrails (no new payment methods or addresses). - Each completed purchase provides cryptographic order proof and requires delivery verification. - Security and workflow steps are clearly defined, including templates for order confirmation and proof generation. - Proven capability with successful Amazon orders; includes clear examples of correct and incorrect usage.
Metadata
Slug autonomous-commerce
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Autonomous Commerce?

Execute real-world e-commerce purchases autonomously with escrow protection and cryptographic proof. Use when: User requests a physical purchase (Amazon, retail), budget is specified, escrow funds are available. Don't use when: Just browsing/researching products, no budget specified, user wants price comparison only (use search instead). Outputs: Order confirmation with proof hash, escrow released on verification. It is an AI Agent Skill for Claude Code / OpenClaw, with 815 downloads so far.

How do I install Autonomous Commerce?

Run "/install autonomous-commerce" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Autonomous Commerce free?

Yes, Autonomous Commerce is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Autonomous Commerce support?

Autonomous Commerce is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Autonomous Commerce?

It is built and maintained by pandeyaby (@pandeyaby); the current version is v1.0.0.

💬 Comments