Access Polymer Labs proof generation and query serviceGET /proof-api · x402 API by auth
Access Polymer Labs proof generation and query service. Request proofs using proof_request (returns job ID) or query proof status using proof_query. Supports payment proofs. Read the docs here https://docs.polymerlabs.org/docs/build/prove-api-V2/api-endpoints
What does this x402 API do?
Access Polymer Labs proof generation and query service. This is an x402-gated GET API resource from auth. The latest safe availability check could not reach the resource on 2026-08-15. The listing records $0.01 USD-denominated per request on Base. No settled paid call has been verified.
- Published price
- $0.01 USD-denominated per request
- Networks
- Base
- Latest evidence
- The latest safe availability check could not reach the resource on 2026-08-15
- Resource ID
- bae018c5ad239d1d6e9bc32e
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://auth.api.polymer.zone/proof-api", {
method: "GET",
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.This sends no payment. Inspect the 402 response before adding a wallet-enabled client.
- Exact route checked
skipped origin unreachable · origin-check:UNSAFE_URL_ENOTFOUND: https://auth.api.polymer.zone/
- Origin unavailable
UNSAFE_URL_ENOTFOUND: https://auth.api.polymer.zone/
- Observed in 402-index
Discovered through bazaar.
- Registry record checked
Registry health: down.
What evidence supports this listing?
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call. Read the discovery and verification methodology →
Which networks and payment options does it accept?
The normalized listing price is $0.01 USD-denominated per request. Raw protocol requirements remain visible below for implementation and audit use.