pay-with-any-token

Automate HTTP 402 payment challenges via Tempo CLI and Uniswap Trading API.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/NickVanzo/hackathon-eth-global-2026 --skill pay-with-any-token-nickvanzo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pay-with-any-token
Source: https://github.com/NickVanzo/hackathon-eth-global-2026/tree/main/.claude/skills/pay-with-any-token
Command: npx skills add https://github.com/NickVanzo/hackathon-eth-global-2026 --skill pay-with-any-token-nickvanzo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the complex process of handling HTTP 402 payment challenges by coordinating token funding, credential creation, and retry logic using the Tempo CLI and Uniswap Trading API.

Core Features & Use Cases

  • Automated support for MPP and x402 payment flows with explicit user confirmation prompts.
  • End-to-end workflow from 402 challenge receipt to credential generation, signing, and retry.
  • Cross-chain funding and bridging orchestration when needed, including safety checks and prompts.

Quick Start

Invoke the pay-with-any-token workflow to automatically fund and pay 402 challenges using Tempo CLI and the Uniswap Trading API.

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 using Uniswap and Tempo?

Automating HTTP 402 payment challenges involves coordinating token funding, credential creation, and retry logic using the Tempo CLI and Uniswap Trading API to handle both MPP and x402 payment paths from challenge receipt to resubmission.

What is an x402 or MPP payment flow and when do I need to automate it?

An x402 or MPP payment flow is a mechanism that requires tokenized funding and credentialing to resolve HTTP 402 challenges. You need to automate it when handling complex cross-chain funding, bridging, and retry logic that demands orchestrated safety checks.

Can I handle cross-chain token funding and bridging for 402 payments automatically?

Yes, cross-chain token funding and bridging for 402 payments can be orchestrated automatically using Tempo CLI and Uniswap Trading API, which coordinates the required steps while enforcing safety checks and prompting for explicit user confirmation.

Do I need to manually confirm credentials when automating 402 payment retries?

No, you do not need to manually confirm every step because the workflow uses AskUserQuestion to prompt for explicit user confirmation only when required during credential generation, signing, and retry processes.

What's the best way to tokenize funding and credentialing flows for DeFi payments?

Tokenizing funding and credentialing flows for DeFi payments is best handled by orchestrating the end-to-end workflow from 402 challenge receipt to credential generation, signing, and resubmission using the Tempo CLI and Uniswap Trading API.

Why does my 402 payment retry fail during cross-chain funding orchestration?

Your 402 payment retry may fail during cross-chain funding if safety checks are not properly enforced or if explicit user confirmation prompts for bridging and credential signing are not completed before resubmission.