git:20261008.1a28e75 to git:20261015.d0ec6af

20 added, 18 removed. Audit A to A.

---

name: charge

- description: Verify and settle one provider-side paid call through Runx Hosted with approval and provider readback.

+ description: Quote, then verify and settle, one buyer's payment for a resource you sell, with approval and provider readback.

---

# Charge

- `charge` is the public seller-side contract for a paid operation. Its OSS graph

- is deliberately thin: it submits the exact tool call, hosted pricing policy,

- opaque returned credential reference, verification capability reference, and

- idempotency seed to the approved Runx Hosted payment operation, then requires a

- provider readback before the run can close.

+ `charge` is the seller contract. `quote` states the payment requirements for

+ one HTTPS resource at an exact price. The default `charge` runner settles the

+ buyer's payment against those requirements once, then requires a readback of

+ the same payment, settled at that price for that resource, before the run can

+ close and the resource is released.

- Runx Hosted owns pricing validation, challenge and credential semantics,

- settlement admission, provider credentials, rail execution, idempotency,

- recovery, and the private payment ledger. The OSS runtime owns the generic

- provider-effect gate and receipt envelope. It does not implement a payment rail

- or infer settlement from caller input.

+ The rail is x402, settled through Coinbase CDP (`coinbase/cdp`) in the

+ seller's own account. Runx Hosted verifies the payment payload with the

+ facilitator, settles it, keeps the attempt idempotent and recoverable, and

+ holds the CDP credential. The OSS runtime owns the generic provider-effect gate

+ and the receipt envelope; it implements no rail and infers no settlement from

+ caller input.

## Operator guide

- Use this skill when Runx is the provider of a paid operation. Use `spend` on the

- buyer side and `refund` for a receipt-linked reversal. A hosted connector and

- grants for `payment.charge` and `payment.charge.read` are required.

+ Use this skill when you are the seller. Use `pay` on the buyer side and

+ `refund` to reverse a settled charge. A hosted `coinbase/cdp` grant is

+ required.

- Stop on missing or ambiguous policy, credential reference, capability,

- counterparty, or idempotency material. Refuse raw card, wallet, provider-key, or

- bearer material. Never release the paid operation unless hosted execution and

- readback agree on a terminal successful charge.

+ Pass the buyer's payment payload and the quoted requirements exactly as they

+ arrived, with the digest that binds the paid request, and a stable idempotency

+ seed. Stop on missing or mismatched requirements, resource, amount or currency.

+ Refuse raw card, wallet, provider-key, or bearer material. Never release the

+ resource unless settlement and readback agree on a settled payment.