GPT55 Wallet Signing Safety Pack
Buyer-owned x402 wallet signing safety pack for agents and wallets. Returns typed-data, calldata, chain, spender, allowance, receipt, and private-key boundary checks after payment. First-purchase activation is https://gpt55.558686.xyz/x402/wallet-signing-safety-pack.json and the dedicated buyer runtime is https://gpt55.558686.xyz/x402/wallet-signing-safety-pack-first-payment-client.mjs. The standard Payment-Required header now includes firstPaymentClient, paymentClientUrl, paymentActivationUrl, and sameRequestRetryRequired so header-only x402 clients can download the buyer-owned runtime, sign locally, and retry the same request with X-PAYMENT. Private keys are never sent to GPT55; use PAY_REAL_X402=1 EVM_PRIVATE_KEY=$EVM_PRIVATE_KEY in the downloaded client only from the buyer environment.
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://gpt55.558686.xyz/v1/paid/wallet-signing-safety-pack", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"replace": "with provider-approved input"
}),
});
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.Review the provider input schema before running this non-read-only method. No payment code is included.
- Exact route checked
not safely testable · potentially-mutating-method:POST
- Origin unavailable
ERR_SSL_PACKET_LENGTH_TOO_LONG
- Observed in 402-index
Discovered through self-registered.
- Registry record checked
Registry health: healthy.
EVIDENCE
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.