{"contentType":"text/markdown","text":"# Resumable production pilot\n\nThis example spends exactly 1 real USDC on Base to fund prepaid RPC access. It is for an owner-approved live pilot after production enablement. No live payment is required to read this guide or inspect the script.\n\nRead the current capabilities, prepaid schedule and general Terms first. Obtain the owner’s approval of the account email, billing location when required by the capabilities response, both terms hashes, a one-dollar payment ceiling, and a usage ceiling between 1 and 100 cents. Tax is included in the dollar, so usable RPC credit may be lower. Do not set approval on someone else’s behalf.\n\nInstall Node.js 22 and `viem`. Save the published example script locally and review it. Keep a separate wallet file and configuration file with permissions 0600, and use a dedicated state directory with permissions 0700. Never put keys, signatures or state in Git or chat. The wallet file contains `privateKey`.\n\nThe configuration contains `email`, `billing` (an empty object when automatic tax is disabled, otherwise the location fields required by capabilities), `walletFile` (absolute path), `paymentCapCents: 100`, `usageCapCents`, `acceptedTermsSha256`, `acceptedGeneralTermsSha256`, and `approveLivePayment: true`. Use the exact hashes obtained from the current API. Use a separate state directory and an owner-authorized wallet for this account.\n\nRun `node examples-production.mjs /absolute/private-config.json /absolute/private-state-directory`.\n\nThe script checks live Base and exact service origins, saves account and payment retry identities before writes, persists the exact signed proof before submission, polls the original payment after uncertain responses, and stores the replacement management credential before retiring the old one. A later run with completed state uses that saved credential without opening the wallet. It never automatically raises a budget or creates another top-up.\n\nIf a payment remains confirming, run with the same state directory later. Never replace an uncertain payment. If a credential-rotation response is lost, review the credentials before explicitly retrying. The final output contains status and a private file path, not credentials. Keep the script and config for your own account only.\n"}