xytara 3.9.10 → 3.9.12

package/RELEASE_NOTES.md

@@ -1,5 +1,8 @@
-`xytara` 3.9.10 makes paid MCP calls catalogable by the CDP Bazaar whatever client the buyer uses.
+`xytara` 3.9.12 makes the MCP server's tools catalogable one by one in x402 discovery (the CDP Bazaar) and stops publishing any buyer data there. It also answers probes of the runtime's paid routes and stray A2A calls with directions instead of bare errors.
 
-- The Bazaar lists a resource from the `resource` and `extensions` fields of the payment it settles. Many x402 clients don't copy the challenge's `extensions` into their payment, and the `PAYMENT-REQUIRED` header leaves them out to stay small, so those payments settled without anything to catalog.
-- The pay-per-call MCP server at `https://mcp.naxytra.com/mcp` (and `/mcp/http402`) now sends the facilitator its own resource and discovery (`bazaar`) extension for the tool whenever the buyer's payment leaves them out. A buyer that does send its own keeps them. The signed EIP-3009 authorization is passed through unchanged, so nothing the buyer signed changes.
-- No change to pricing, payment, routing, the provider ledger or the client package.
+- **No buyer data in discovery:** the x402 discovery (Bazaar) extension now carries a fixed, public example call for each tool. Before, it used the buyer's own call arguments, and they could have been published in a public catalog. Each own tool's example validates against its input schema and runs. Provider tools get an example derived from their schema.
+- **One discovery entry per tool:** each tool's payment resource URL names the tool (`https://mcp.naxytra.com/mcp#<tool>`, `…/mcp/http402#<tool>`). The resource also carries `serviceName`, `tags` and `iconUrl`, and its description is the tool's own description with its price.
+- **Reference-shaped discovery extension:** the `http` (HTTP-402 variant) and `mcp` (MCP-native) discovery schemas follow the shape the x402 reference SDK produces. The `PAYMENT-REQUIRED` header now carries the extension (when it fits in 8,000 characters), so x402 SDK clients echo it in their payment. Provider-tool challenges carry it too.
+- **Runtime paid routes:** a `GET` or `HEAD` on `/x402/commands/execute`, `/x402/mcp/tools/invoke` or `/x402/credits/topup` answers `405` with `Allow: POST`, the request body shape, how payment works and the discovery links, instead of `404`.
+- **Clearer unknown methods on MCP:** A2A methods such as `message/send` sent to the MCP endpoint are pointed at the A2A lane (`/v1/a2a`) and the agent card. `skills/list` and other unknown methods are told to use `tools/list` and `tools/call`.
+- No change to pricing, payment, settlement, routing, the provider ledger or the client package.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "xytara",
-  "version": "3.9.10",
+  "version": "3.9.12",
   "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.",
   "main": "client.js",
   "exports": {