Repository navigation
AiFinPay for WordPress 0.3.0
Install: WordPress admin → Plugins → Add Plugin → Upload Plugin → aifinpay-0.3.0.zip, then activate. Requires WordPress 6.5+ and PHP 8.1+. Updating from 0.2.0: upload the zip and choose "Replace current with uploaded"; the plugin stays active, keeps its settings, and every protected path keeps the price it had.
- Each protected path can have its own price. Under Settings → AiFinPay → Protected paths, add
standard,complexorpremiumafter a path, for example/reports/* premium; a path without one costs the site-wide Price per request. The new Price of each path table shows what each path costs. In Enforce the REST API and the feed cost what the highest-priced page path costs, because they show the same posts. - Prices follow
@aifinpay/gate0.11.0: the HTTP 402,/.well-known/x402.json,/llms.txtand the registration with AiFinPay carry each path's price, and an agent's prepaid batch is spent at the price of the path it opens. A $0.02 batch pays for 40 Standard, 10 Complex or 4 Premium requests. - The HTTP 402 no longer carries
protocol_fee_bps. The fee is set per merchant and stated by the quote, as in@aifinpay/gate0.11.0; 168 parity checks match it byte for byte. - The connect code help names the dashboard page it is on: Profile & keys → API keys → Connect a CMS site.
SHA-256 of the zip: eecb4612d9a98e17f2b919c179884f5400aa779a8b54d65b0c32ee09ea517885