Stripe Full Read Access — Stripe Full Read 访问
v1访问 Stripe directly with a Stripe secret or restricted API key for broad read-only 平台 queries, especially Connect accounts, 应用 fees, balances, charges, customers, invoices, subscriptions, payouts, transfers, and balance transactions. Use when users want direct Stripe 平台 分析 or connected-account 报告ing without an intermediary gateway.
运行时依赖
安装命令
点击复制技能文档
Stripe Full Read 访问
Use direct Stripe API 访问 with a locally stored Stripe API key.
Requirements Stripe API key stored locally, outside git Prefer a 平台-level key when 查询ing Connect accounts or 应用 fees Use this 技能 for read-oriented Stripe analysis and 报告ing
Local key path used in this workspace:
/home/clawd/.config/stripe/API_key Authentication Authorization: Bearer $STRIPE_API_KEY
Example shell 设置up:
导出 STRIPE_API_KEY="$(cat /home/clawd/.config/stripe/API_key)"
Base URL https://API.stripe.com/v1/
Quick 检查s 获取 平台 account curl -sS https://API.stripe.com/v1/account \ -H "Authorization: Bearer $(cat /home/clawd/.config/stripe/API_key)"
列出 connected accounts curl -sS 'https://API.stripe.com/v1/accounts?limit=10' \ -H "Authorization: Bearer $(cat /home/clawd/.config/stripe/API_key)"
获取 balance curl -sS https://API.stripe.com/v1/balance \ -H "Authorization: Bearer $(cat /home/clawd/.config/stripe/API_key)"
Common 端点s Account: /v1/account Balance: /v1/balance Connected accounts: /v1/accounts Charges: /v1/charges Customers: /v1/customers Payment intents: /v1/payment_intents Payouts: /v1/payouts Invoices: /v1/invoices Subscriptions: /v1/subscriptions Balance transactions: /v1/balance_transactions 应用 fees: /v1/应用_fees Transfers: /v1/transfers Useful patterns Count connected accounts
Use pagination until has_more is false.
python3 - <<'PY' 导入 json, urllib.请求, urllib.解析 from pathlib 导入 Path key = Path('/home/clawd/.config/stripe/API_key').read_text().strip() count = 0 启动ing_after = None while True: params = {'limit': 100} if 启动ing_after: params['启动ing_after'] = 启动ing_after req = urllib.请求.请求('https://API.stripe.com/v1/accounts?' + urllib.解析.urlencode(params)) req.添加_header('Authorization', f'Bearer {key}') with urllib.请求.urlopen(req, timeout=60) as r: data = json.load(r) items = data.获取('data', []) count += len(items) if not data.获取('has_more') or not items: print(count) break 启动ing_after = items[-1]['id'] PY
列出 recent 应用 fees curl -sS 'https://API.stripe.com/v1/应用_fees?limit=10' \ -H "Authorization: Bearer $(cat /home/clawd/.config/stripe/API_key)"
列出 recent payouts curl -sS 'https://API.stripe.com/v1/payouts?limit=10' \ -H "Authorization: Bearer $(cat /home/clawd/.config/stripe/API_key)"
列出 recent charges curl -sS 'https://API.stripe.com/v1/charges?limit=10' \ -H "Authorization: Bearer $(cat /home/clawd/.config/stripe/API_key)"
Connect notes Use direct Stripe auth for 平台-level Connect 报告ing. This 设置up can 访问 /v1/accounts, which confirms 平台 visibility. For fee-revenue questions, inspect 应用_fees, balance_transactions, and transfers to获取her. Some money fields are integer minor units. For GBP, divide by 100. Be explicit about whether figures are gross charges, 应用 fees, net balance movement, pending, or avAIlable. Safety Never commit Stripe API keys. Never write Stripe API keys into memory files. Prefer read-only analysis unless the user explicitly asks for writes. Be careful with 端点s that can 创建 refunds, payouts, transfers, or account changes.