xytara 3.9.1 → 3.9.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/RELEASE_NOTES.md +4 -4
  2. package/package.json +1 -1
package/RELEASE_NOTES.md CHANGED
@@ -1,6 +1,6 @@
1
- `xytara` 3.9.1 gives the runtime host its own x402 discovery entry and advertises an honest price range wherever one URL carries calls at different prices.
1
+ `xytara` 3.9.2 says, for every paid resource in x402 discovery, how an unpaid call is answered and what the advertised `payTo` means, and sends the runtime's `PAYMENT-REQUIRED` header in standard base64.
2
2
 
3
- - **Runtime `/.well-known/x402`** — the runtime host (`/.well-known/x402`, alias `/.well-known/x402.json`) now serves a discovery entry for its own paid routes only (`/x402/commands/execute`, `/x402/mcp/tools/invoke`, `/x402/credits/topup`), with the configured accepts, a link to its OpenAPI document and the provider-network contract. It answers 404 when the runtime takes no x402 payments.
4
- - **Price range in discovery** — on the runtime entry and the MCP executor's `/.well-known/x402`, each payment option keeps `amount` (the cheapest call) and adds `maxAmount`, plus `minAmount` when some calls cost less, in the shape the x402 discovery working group is converging on. The MCP executor's range spans the standard and attesting tools and widens to any listed provider tool's own price; the runtime's widens to active provider offers. The live payment-required challenge stays authoritative for each call.
5
- - **Verifiers** — the MCP executor verifier checks that the `PAYMENT-REQUIRED` header and the challenge body carry identical terms on `/mcp` and `/mcp/http402`; the runtime state-guard verifier exits on failure instead of holding `verify:all` open.
3
+ - **Payment transport per resource** — `resource_details[]` in the runtime's and the MCP executor's `/.well-known/x402` now carries `payment_transport`: `http-402` (HTTP 402 with a `PAYMENT-REQUIRED` header) or `mcp-tool-result` (x402 MCP transport: HTTP 200 with a payment-required tool result), plus a one-line `payment_transport_detail`. An indexer that probes only for HTTP 402 can tell a working MCP endpoint from an unpaid one.
4
+ - **What `payTo` means** — `payment.pay_to` states that `payTo` is naxytra's settlement address for every paid call, provider-run tools included: it identifies who receives the payment, not who ran the call. Each provider's share is paid out to its own address by a weekly sweep once at least $1.00 is owed, and the signed delivery receipt names the provider that executed the call.
5
+ - **`PAYMENT-REQUIRED` in standard base64** — the runtime encoded the header as base64url, which browser clients decoding with `atob()` reject. It is now standard base64, like `PAYMENT-RESPONSE` and the MCP executor; the verifier checks the encoding and that the header decodes to exactly the body's `payment_required`.
6
6
  - Client package (thin): unchanged.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "xytara",
3
- "version": "3.9.1",
3
+ "version": "3.9.2",
4
4
  "description": "Client for the hosted naxytra runtime: discover a capability, pay per call with x402 (gasless USDC on Base) or credits, get the deliverable and a signed delivery receipt you can verify offline. The runtime is a hosted service; this package is the client.",
5
5
  "main": "client.js",
6
6
  "exports": {