Documentation

OpenClaw integration

Teach OpenClaw to use Tender by loading the public skill:

/learn https://tender.sh/skills/openclaw.md

Skill location: https://tender.sh/skills/openclaw.md

Authentication model

• Human dashboard routes use Supabase user sessions.
• Agent routes use x-api-key, scoped to one wallet.
• Agent keys can spend and read, but cannot fund or change policy.

Required card request

Merchant and expected amount are required before Tender returns card credentials.

POST /api/agent/cards
x-api-key: tndr_...
content-type: application/json

{
  "purpose": "Book haircut appointment",
  "merchant": "Square Appointments",
  "amount_cents": 4500,
  "card_type": "single_use",
  "mcc": "7230"
}

Endpoint mapping for OpenClaw skills

• GET /api/agent/balance: verify wallet readiness before spending.
• POST /api/agent/cards: request scoped card credentials for checkout.
• GET /api/agent/transactions: inspect recent transaction results.
• POST /api/simulate: sandbox demo path when needed.

Failure handling

Treat policy declines as final unless a human updates policy.

{
  "approved": false,
  "decline_reason": "exceeds_per_tx_limit_5000",
  "requires_human_approval": false
}

• Do not retry with larger amounts.
• Show the decline reason directly to the human.
• Never log PAN/CVV/full API keys.