polymer-pay-proxy

name	polymer-pay-proxy
description	USE THIS SKILL WHEN: the user wants to proxy a request through Polymer Pay, call an x402 API directly, or needs to understand the Polymer Pay proxy URL pattern. Handles x402 payment negotiation automatically.
endpoints	[{"path":"/healthz","method":"GET","price":"$0.00","description":"Health check"},{"path":"/*","method":"ANY","price":"Varies","description":"Proxy any upstream x402 request"}]
metadata	{"polymer-pay-skill":{"emoji":"🔗","requires":{"env":["POLYMER_PAY_API_KEY"],"primaryEnv":"POLYMER_PAY_API_KEY"}}}
registries	{}
provider	dynamic

Polymer Pay Proxy

Proxy any upstream request through Polymer Pay; Polymer Pay handles x402 discovery and payment flow automatically.

Authentication

All requests route through the Polymer Pay proxy. Include your Polymer Pay API key in every request:

{
  "headers": {
    "Content-Type": "application/json",
    "x-polymer-pay-api-key": "{{POLYMER_PAY_API_KEY}}"
  }
}

Base URL: https://pay.polymerlabs.org/proxy/{scheme}/{host}

Common Operations

Health Check

Verify the Polymer Pay proxy is operational.

Pricing: $0.00

{
  "method": "GET",
  "url": "https://pay.polymerlabs.org/healthz",
  "headers": {
    "Content-Type": "application/json",
    "x-polymer-pay-api-key": "{{POLYMER_PAY_API_KEY}}"
  }
}

Response: Returns {"status":"ok"} when the proxy is healthy.

Proxy a Request

Forward any HTTP request through the Polymer Pay proxy. The proxy handles x402 payment negotiation automatically.

Pricing: Varies based on upstream endpoint

{
  "method": "POST",
  "url": "https://pay.polymerlabs.org/proxy/https/x402.browserbase.com/browser/session/create",
  "headers": {
    "Content-Type": "application/json",
    "x-polymer-pay-api-key": "{{POLYMER_PAY_API_KEY}}"
  },
  "body": {}
}

Response: The proxied response from the upstream x402 endpoint.

When to Use

• Calling x402 endpoints — Route any x402-enabled API call through Polymer Pay without handling payments manually.
• Unified API access — Use a single Polymer Pay API key to access multiple x402-enabled services.
• Automatic payment handling — Let Polymer Pay negotiate and process payments for per-request micropayments.

Best Practices

• Never reveal your API key — Keep POLYMER_PAY_API_KEY secure and never expose it in logs or client-side code.
• Use environment variables — Store your API key in POLYMER_PAY_API_KEY env var and reference {{POLYMER_PAY_API_KEY}} in requests.
• Check health before use — Verify the proxy is operational with /healthz if you encounter issues.
• For errors — See @skills/polymer-pay-api-errors/SKILL.md for complete error code reference and troubleshooting