polymer-pay-proxy

Route upstream HTTP requests through the Polymer Pay proxy with x402 payments.

1|2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/polymerdao/pay-apis --skill polymer-pay-proxy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polymer-pay-proxy
Source: https://github.com/polymerdao/pay-apis/tree/main/skills/polymer-pay-proxy
Command: npx skills add https://github.com/polymerdao/pay-apis --skill polymer-pay-proxy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables developers to forward HTTP requests through Polymer Pay, automatically handling x402-based payments so you don't manage per-request settlements manually.

Core Features & Use Cases

  • Proxy any upstream x402-enabled request through Polymer Pay with automated payment negotiation.
  • Verify proxy health via the /healthz endpoint.
  • Use a single API key to access multiple x402-enabled services through the base URL.

Quick Start

Proxy a request through Polymer Pay by calling the base URL with your POLYMER_PAY_API_KEY.

Frequently Asked Questions about polymer-pay-proxy

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

FAQPage Schema
How do I proxy HTTP requests to handle x402 payments automatically?

To proxy upstream HTTP requests and trigger x402 payments automatically, set your POLYMER_PAY_API_KEY environment variable and route calls through the base URL https://pay.polymerlabs.org/proxy/{scheme}/{host} with the API key in the x-polymer-pay-api-key header.

What is the x402 payment proxy mechanism and how does it work?

The x402 payment proxy intercepts upstream HTTP requests and manages payment negotiation automatically. Routing traffic through the Polymer Pay base URL lets the proxy handle per-request settlements using your single API key, eliminating manual payment management.

Do I need an API key to use the Polymer Pay proxy for upstream requests?

Yes, you need a POLYMER_PAY_API_KEY to use the Polymer Pay proxy. You must set this key in your environment and include it in the x-polymer-pay-api-key header so the proxy can authenticate and process your upstream x402 payment negotiations.

Can I access multiple x402-enabled services with a single API key?

Yes, you can access multiple x402-enabled services with a single API key. The Polymer Pay proxy uses one base URL and your POLYMER_PAY_API_KEY to route and manage automated payments across different target hosts without requiring separate credentials.

How do I check if the payment proxy is running and healthy?

Check the payment proxy health by calling the /healthz endpoint. This verifies the operational status of the Polymer Pay proxy to ensure it is ready to handle upstream x402 payment routing before sending live traffic.

Why does my proxied request fail to negotiate x402 payments?

Proxied requests fail to negotiate x402 payments if the POLYMER_PAY_API_KEY is missing or invalid. Ensure the key is set in your environment and passed correctly in the x-polymer-pay-api-key header, then verify proxy health via the /healthz endpoint.