pay-with-any-token

Name: pay-with-any-token
Availability: InStock
Author: bendr-20

Automate HTTP 402 payment challenges and x402 token payments via Uniswap and Tempo.

4|Updated Feb 10, 2026

Search Tags:#automation #payments #uniswap #tempo #x402 #402

Ready to run

npx skills add https://github.com/Bendr-20/helixa --skill pay-with-any-token

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pay-with-any-token
Source: https://github.com/Bendr-20/helixa/tree/main/.agents/skills/pay-with-any-token
Command: npx skills add https://github.com/Bendr-20/helixa --skill pay-with-any-token

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates complex HTTP 402 payment challenges and x402-style token payments to API providers by orchestrating Tempo CLI workflows with Uniswap Trading API.

Core Features & Use Cases

End-to-end pay-with-any-token flows: detect 402 challenges, select funding token, swap to bridge assets, bridge to Tempo, and retry the request.
x402 and MPP support: handles both traditional Tempo/MPP and EIP-3009 x402 paths with user confirmations and safe fallbacks.
Safe operation: balance checks, permission prompts, and detailed error handling for resilient automation.

Quick Start

Configure your private key and Tempo wallet, then run the pay-with-any-token workflow to automatically fund the Tempo wallet and retry a 402 challenge.

Frequently Asked Questions about pay-with-any-token

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate HTTP 402 payment challenges for API access?▼

Automating HTTP 402 payment challenges involves detecting the challenge, selecting a funding token, swapping on-chain via Uniswap, bridging assets to Tempo, and retrying the request. This workflow handles both traditional Tempo/MPP and EIP-3009 x402 paths with balance checks and user confirmations.

Can I pay for API access using any token through Uniswap?▼

Yes, you can pay for API access using any token by swapping your selected funding token to bridge assets on-chain via Uniswap's Trading API. The swapped assets are then bridged to Tempo to satisfy the 402 payment challenge and retry the HTTP request.

What is the difference between x402 and MPP payment workflows?▼

MPP workflows represent traditional Tempo payment paths, whereas x402 utilizes EIP-3009 token standards. This automation handles both paths, providing user confirmations, safe fallbacks, and robust error handling for resilient API payment processing.

How do I handle x402 token payments when my wallet lacks the required bridge asset?▼

When your wallet lacks the required bridge asset for x402 token payments, the workflow selects an available funding token, executes an on-chain swap via Uniswap's Trading API, and bridges the result to Tempo before retrying the request.

Does the Tempo CLI support automated 402 payment retries?▼

Yes, Tempo CLI workflows support automated 402 payment retries by orchestrating balance checks, on-chain Uniswap swaps, asset bridging, and HTTP request retries for both MPP and x402 environments.

What are the limitations of automating 402 payments with on-chain token swaps?▼

Automation limitations include potential on-chain swap failures, bridge delays, and insufficient funding token balances. The workflow mitigates these with permission prompts, detailed error handling, and safe fallbacks for resilient operation.