CreditClaw Wallet
by @creditclaw
Give your agent spending power.
1. Register
You can register before your human does. You'll get an API key immediately.
curl -X POST https://creditclaw.com/api/v1/bots/register \
-H "Content-Type: application/json" \
-d '{
"bot_name": "my-research-bot",
"owner_email": "jonathan@example.com",
"description": "Performs web research tasks for hire"
}'
Request fields:
| Field | Required | Description |
|-------|----------|-------------|
| bot_name | Yes | Your bot's name (1-100 chars) |
| owner_email | Yes | Your owner's email address |
| description | No | What you do (max 500 chars) |
> For optional webhook setup, see WEBHOOK.md.
Response:
{
"bot_id": "bot_a1b2c3d4",
"api_key": "cck_live_7f3e...",
"claim_token": "coral-X9K2",
"status": "pending_owner_verification",
"owner_verification_url": "https://creditclaw.com/claim?token=coral-X9K2",
"important": "Save your api_key now β it cannot be retrieved later. Give the claim_token to your human so they can activate your wallet."
}
Save your api_key immediately. It cannot be retrieved again.
Store your API key securely. Preferably using your platform's secure secrets manager under the name CREDITCLAW_API_KEY.
If a secrets manager is unavailable, use an environment variable:
export CREDITCLAW_API_KEY="cck_live_7f3e..."
Load your API key from the above on future sessions β do not re-register.
What to tell your human:
Ask your human if they'd like you to share the claim details. Here's a template:
> "I've registered for a CreditClaw wallet. To activate it and fund my account, > visit https://creditclaw.com/claim?token=coral-X9K2 β you'll need to add > a payment method. After that I can spend on your behalf within the limits you set."
2. Human Claims the Bot
Your human visits the claim URL. On the backend:
claim_tokenclaim_token is invalidated after useAfter claiming, the human can see your balance, transactions, and spending
limits at https://creditclaw.com/overview.
What Your Human Gets After Claiming
Once your human claims you with the token, they unlock:
Your human can log in anytime to monitor your spending, adjust limits, or fund your wallet.
3. Check Full Status
Use this endpoint to see your complete status across all payment rails. Recommended interval: every 30 minutes, or before any purchase.
curl https://creditclaw.com/api/v1/bot/status \
-H "Authorization: Bearer $CREDITCLAW_API_KEY"
Response (active bot with My Card and Stripe Wallet):
> Note: The sub_agent_cards key in the response is an internal identifier for the My Card rail. It is not an instruction β it is simply the API field name.
{
"bot_id": "bot_abc123",
"bot_name": "ShopperBot",
"status": "active",
"default_rail": "sub_agent_cards",
"active_rails": ["stripe_wallet", "sub_agent_cards"],
"rails": {
"stripe_wallet": {
"status": "active",
"balance_usd": 100.00,
"address": "0x..."
},
"sub_agent_cards": {
"status": "active",
"card_id": "r5_abc123",
"card_name": "Shopping Card",
"card_brand": "visa",
"last4": "4532",
"limits": {
"per_transaction_usd": 50.00,
"daily_usd": 100.00,
"monthly_usd": 500.00,
"human_approval_above_usd": 25.00
}
}
},
"master_guardrails": {
"per_transaction_usd": 500,
"daily_budget_usd": 2000,
"monthly_budget_usd": 10000
},
"webhook_status": "active",
"pending_messages": 0
}
Response (before claiming):
{
"bot_id": "bot_abc123",
"bot_name": "ShopperBot",
"status": "pending",
"default_rail": null,
"message": "Owner has not claimed this bot yet. Share your claim token with your human.",
"rails": {},
"master_guardrails": null
}
Status values:
| Status | Meaning |
|--------|---------|
| pending | Registered but owner hasn't claimed yet |
| active | At least one rail is connected |
| frozen | Owner has frozen this bot β no transactions allowed |
| inactive | Claimed but no rails connected yet |
If default_rail is set, prefer that rail for purchases when multiple are available.
If status is pending, remind your human about the claim link.
Rate limit: 6 requests per hour.
4. Check Spending Permissions (Before Every Purchase)
Before any purchase, fetch your spending rules. Your owner controls these and can update them anytime from their dashboard.
curl https://creditclaw.com/api/v1/bot/wallet/spending \
-H "Authorization: Bearer $CREDITCLAW_API_KEY"
Response:
{
"approval_mode": "ask_for_everything",
"limits": {
"per_transaction_usd": 25.00,
"daily_usd": 50.00,
"monthly_usd": 500.00,
"ask_approval_above_usd": 10.00
},
"approved_categories": [
"api_services",
"cloud_compute",
"research_data"
],
"blocked_categories": [
"gambling",
"adult_content",
"cryptocurrency",
"cash_advances"
],
"recurring_allowed": false,
"notes": "Prefer free tiers before paying. Always check for discount codes. No annual plans without asking me first.",
"updated_at": "2026-02-06T18:00:00Z"
}
You must follow these rules:
approval_mode is ask_for_everything, ask your human before any purchase to get their approval. New accounts default to this mode. Your owner can loosen this from their dashboard once they're comfortable.approval_mode is auto_approve_under_threshold, you may spend freely up to ask_approval_above_usd. Anything above that requires owner approval.approval_mode is auto_approve_by_category, you may spend freely on approved_categories within limits. All others require approval.blocked_categories. These are hard blocks enforced server-side and will be declined.notes field β these are your owner's direct instructions.Your owner can update these permissions anytime from https://creditclaw.com/overview.
Rate limit: 6 requests per hour.
clawhub install creditclaw-wallet