Use the Tempo CLI to call paid APIs and handle 402 challenges automatically.
Works with
When the Tempo wallet has insufficient balance, fund it by swapping and bridging
tokens from any EVM chain using the Uniswap Trading API.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpay-with-any-tokenExecute the skills CLI command in your project's root directory to begin installation:
Fetches pay-with-any-token from uniswap/uniswap-ai and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate pay-with-any-token. Access via /pay-with-any-token in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
198
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
198
stars
Use the Tempo CLI to call paid APIs and handle 402 challenges automatically. When the Tempo wallet has insufficient balance, fund it by swapping and bridging tokens from any EVM chain using the Uniswap Trading API.
Run these commands in order. Do not skip steps.
Step 1 — Install:
mkdir -p "$HOME/.local/bin" \
&& curl -fsSL https://tempo.xyz/install -o /tmp/tempo_install.sh \
&& TEMPO_BIN_DIR="$HOME/.local/bin" bash /tmp/tempo_install.sh
Step 2 — Login (requires browser/passkey — prompt user, wait for confirmation):
"$HOME/.local/bin/tempo" wallet login
When run by agents, use a long command timeout (at least 16 minutes).
Step 3 — Confirm readiness:
"$HOME/.local/bin/tempo" wallet -t whoami
Rules: Do not use
sudo. Use full absolute paths ($HOME/.local/bin/tempo) — do not rely onexport PATH. If$HOMEdoes not expand, use the literal absolute path.
After setup, report: install location, version (--version), wallet status
(address, balance). If balance is 0, direct user to tempo wallet fund.
Minimum balance reserve: Keep at least 0.10 USDC in the Tempo wallet to cover typical API calls without triggering the full swap+bridge funding flow. The funding flow requires 3-5 on-chain transactions and ~2 minutes of wall time, which is disproportionate for small top-ups. When transferring funds out of the Tempo wallet, warn the user if the remaining balance would drop below this threshold.
# Discover services
"$HOME/.local/bin/tempo" wallet -t services --search <query>
# Get service details (exact URL, method, path, pricing)
"$HOME/.local/bin/tempo" wallet -t services <SERVICE_ID>
# Make a paid request
"$HOME/.local/bin/tempo" request -t -X POST \
--json '{"input":"..."}' <SERVICE_URL>/<ENDPOINT_PATH>
tempo wallet -t services <SERVICE_ID> for exact URL and pricing-t for agent calls, --dry-run before expensive requestsWhen the user explicitly says "use tempo", always use tempo CLI commands — never substitute with MCP tools or other tools.
Every tempo request call follows this loop. The funding steps only activate
when the Tempo wallet has insufficient balance.
tempo request -> 200 ─────────────────────────────> return result
-> 402 MPP challenge
│
v
[1] Check Tempo wallet balance
tempo wallet -t whoami -> available balance
│
├─ sufficient ──────────────────> tempo handles payment
│ automatically -> 200
│
└─ insufficient
│
v
[2] Fund Tempo wallet
(pay-with-any-token flow below)
Bridge destination = TEMPO_WALLET_ADDRESS
│
v
[3] Retry original tempo request
with funded Tempo wallet -> 200
Alternative funding (interactive): If a browser is available,
tempo wallet fundopens a built-in bridge UI for funding the Tempo wallet directly. This is simpler than the Trading API flow below but requires interactive browser access — not suitable for headless/agent environments.
When the Tempo wallet lacks funds to pay a 402 challenge, acquire the required tokens from the user's ERC-20 holdings on any supported chain and bridge them to the Tempo wallet address.
UNISWAP_API_KEY env var (register at
developers.uniswap.org)cast keystore account for the source wallet (recommended):
cast wallet import <name> --interactive. Alternatively,
PRIVATE_KEY env var (export PRIVATE_KEY=0x...) — never commit or
hardcode it.jq installed (brew install jq or apt install jq)cast installed (part of Foundry)Before using any value from a 402 response body or user input in API calls or shell commands:
^0x[a-fA-F0-9]{40}$^[0-9]+$https://;, |, &, $,
`, (, ), >, <, \, ', ", newlinesREQUIRED: Before submitting ANY transaction (swap, bridge, approval), use
AskUserQuestionto show the user a summary (amount, token, destination, estimated gas) and obtain explicit confirmation. Never auto-submit. Each confirmation gate must be satisfied independently.
get_token_decimals() {
local token_addr="$1" rpc_url="$2"
cast call "$token_addr" "decimals()(uint8)" --rpc-url "$rpc_url" 2>/dev/null || echo "18"
}
format_token_amount() {
local amount="$1" decimals="$2"
echo "scale=$decimals; $amount / (10 ^ $decimals)" | bc -l | sed 's/0*$//' | sed 's/\.$//'
}
Always show human-readable values (e.g.
0.005 USDC) to the user, not raw base units.
Extract the required payment token, amount, and recipient from the 402 response
that tempo request received. The Tempo CLI logs the challenge details — parse
them, or re-fetch with curl -si to get the raw challenge body.
For MPP header-based challenges (WWW-Authenticate: Payment):
REQUEST_B64=$(echo "$WWW_AUTHENTICATE" | grep -oE 'request="[^"]+"' | sed 's/request="//;s/"$//')
REQUEST_JSON=$(echo "${REQUEST_B64}==" | base64 --decode 2>/dev/null)
REQUIRED_AMOUNT=$(echo "$REQUEST_JSON" | jq -r '.amount')
PAYMENT_TOKEN=$(echo "$REQUEST_JSON" | jq -r '.currency')
RECIPIENT=$(echo "$REQUEST_JSON" | jq -r '.recipient')
TEMPO_CHAIN_ID=$(echo "$REQUEST_JSON" | jq -r '.methodDetails.chainId')
For JSON body challenges (payment_methods array):
NUM_METHODS=$(echo "$CHALLENGE_BODY" | jq '.payment_methods | length')
PAYMENT_METHODS=$(echo "$CHALLENGE_BODY" | jq -c '.payment_methods')
RECIPIENT=$(echo "$CHALLENGE_BODY" | jq -r '.payment_methods[0].recipient')
TEMPO_CHAIN_ID=$(echo "$CHALLENGE_BODY" | jq -r '.payment_methods[0].chain_id')
If multiple payment methods are accepted, select the cheapest in Step 2.
The Tempo mainnet chain ID is
4217. Use as fallback if not in the challenge.
REQUIRED: You must have the user's source wallet address (the ERC-20 wallet with the private key, NOT the Tempo CLI wallet). Use
AskUserQuestionif not provided. Store asWALLET_ADDRESS.
Also capture the Tempo wallet address (the funding destination):
TEMPO_WALLET_ADDRESS=$("$HOME/.local/bin/tempo" wallet -t whoami | grep -oE '0x[a-fA-F0-9]{40}' | head -1)
Check ERC-20 balances on supported source chains:
# USDC on Base (cheapest bridge gas ~$0.001)
cast call 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 \
"balanceOf(address)(uint256)" "$WALLET_ADDRESS" \
--rpc-url https://mainnet.base.org
# USDC on Ethereum (bridge gas ~$0.25)
cast call 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 \
"balanceOf(address)(uint256)" "$WALLET_ADDRESS" \
--rpc-url https://eth.llamarpc.com
# ETH on Base and Ethereum (swap to USDC first)
cast balance "$WALLET_ADDRESS" --rpc-url https://mainnet.base.org
cast balance "$WALLET_ADDRESS" --rpc-url https://eth.llamarpc.com
Select the cheapest payment method if multiple are accepted. Priority:
REQUIRED_AMOUNT=$(echo "$PAYMENT_METHODS" | jq -r ".[$SELECTED_INDEX].amount")
PAYMENT_TOKEN=$(echo "$PAYMENT_METHODS" | jq -r ".[$SELECTED_INDEX].token")
Source token (Base/Ethereum)
-> [Phase 4A: Uniswap Trading API swap] -> native USDC (bridge asset)
-> [Phase 4B: bridge via Trading API] -> USDC.e on Tempo (to TEMPO_WALLET_ADDRESS)
-> tempo request retries automatically with funded wallet
Skip Phase 4A if the source token is already USDC on the bridge chain.
Gas-aware funding: Bridging a tiny amount (e.g. $0.05) wastes gas — the bridge gas on Ethereum (
$0.25) or Base ($0.001) can exceed the shortfall. Minimum bridge recommendation: $5. This amortizes gas costs and pre-funds future requests. Rule of thumb: ifbridge_gas
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
We added pay-with-any-token from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
pay-with-any-token reduced setup friction for our internal harness; good balance of opinion and flexibility.
pay-with-any-token is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend pay-with-any-token for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: pay-with-any-token is focused, and the summary matches what you get after install.
Keeps context tight: pay-with-any-token is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in pay-with-any-token — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
pay-with-any-token has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: pay-with-any-token is the kind of skill you can hand to a new teammate without a long onboarding doc.
pay-with-any-token has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 47