Praecise Skerry/ Reference/ Paying by the call
Paying by the call9
Price a resource and let automated clients pay for each call. Skerry builds the 402 for the customer's server in both x402 and the Machine Payments Protocol, checks the payment the client sends back, and settles it on the customer's own merchant account. Skerry runs no facilitator and holds no keys. A preview: every call answers 409 capability_coming_soon until it is switched on for the customer.
- The customer's priced resources, with the minimum single payment per methodget/customers/{id}/priced-resources
- Price a resourcepost/customers/{id}/priced-resources
- Stop charging for a resourcedelete/customers/{id}/priced-resources/{resource_id}
- The 402 to send an unpaid request: status, headers and body, in both protocolspost/machine-payments/challenge
- Check and settle the payment a client sent, or draw the call from its creditpost/machine-payments/verify
- A customer's credits, newest firstget/machine-payments/credits
- Buy prepaid credit for a resource with one paymentpost/machine-payments/credits
- One credit: bought, balance, expiryget/machine-payments/credits/{id}
- Send back the unused part of a credit, within the customer's policypost/machine-payments/credits/{id}/refund