pay-with-any-token

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

4|2|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Iziedking/hawkeye --skill pay-with-any-token-iziedking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pay-with-any-token
Source: https://github.com/Iziedking/hawkeye/tree/main/.agents/skills/pay-with-any-token
Command: npx skills add https://github.com/Iziedking/hawkeye --skill pay-with-any-token-iziedking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the disruption caused by HTTP 402 Payment Required responses when accessing paid APIs, which block automated workflows, agent operations, and machine-to-machine service access that requires programmatic payment fulfillment without manual intervention.

Core Features & Use Cases

  • MPP 402 Automation: Automatically handles Machine Payment Protocol (MPP) 402 challenges via the Tempo CLI, with built-in wallet balance checks and automatic retry logic for failed payment attempts.
  • Cross-Chain Token Funding: When the Tempo wallet has insufficient balance, it swaps and bridges tokens from any supported EVM chain using the Uniswap Trading API to fund the wallet without requiring pre-funded Tempo accounts or manual transfers.
  • x402 Protocol Support: Handles x402 standard payment challenges using EIP-3009 off-chain signed transfers for one-time API payments, with support for multiple EVM networks including Base, Ethereum, and Tempo.
  • Use Case: An autonomous on-chain trading agent that needs to access paid market data or analytics APIs can use this Skill to automatically pay 402 challenges using tokens held on any EVM chain, eliminating the need for manual wallet operations or pre-allocated payment reserves.

Quick Start

Use the pay-with-any-token skill to automatically resolve 402 Payment Required errors when accessing paid APIs, funding your Tempo wallet with tokens from any EVM chain as needed to complete the payment and retrieve the requested resource.

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 Required responses for API access?

Automate HTTP 402 Payment Required responses by using the Tempo CLI and Uniswap Trading API to detect insufficient wallet balances, execute token swaps, and bridge funds to complete machine-to-machine payments.

Can I pay for x402 API challenges using tokens from any EVM chain?

Yes, you can pay x402 API challenges by swapping and bridging tokens from any supported EVM chain to fund your Tempo wallet, eliminating the need for pre-funded accounts or manual transfers.

How does cross-chain token bridging work with the Machine Payment Protocol?

Cross-chain token bridging for the Machine Payment Protocol automatically triggers when a Tempo wallet balance is insufficient, using the Uniswap Trading API to swap and bridge funds from other EVM chains before retrying the original API request.

Do I need a pre-funded Tempo wallet to handle autonomous agent 402 challenges?

No, you do not need a pre-funded Tempo wallet. The system automatically detects insufficient balances, swaps tokens from any EVM chain, and bridges funds to fulfill the 402 payment challenge.

What EVM networks are supported for EIP-3009 off-chain signed transfers?

EIP-3009 off-chain signed transfers for x402 standard payment challenges are supported on multiple EVM networks, including Base, Ethereum, and Tempo.

Why does my automated workflow fail when accessing paid market data APIs?

Automated workflows fail accessing paid APIs due to HTTP 402 Payment Required blocks. This is resolved by automatically fulfilling the payment challenge via MPP and retrying the original API request to retrieve the resource.