xytara 3.9.11 → 3.9.12

package/RELEASE_NOTES.md

@@ -1,6 +1,8 @@
-`xytara` 3.9.11 adds the stateless MCP protocol (2026-07-28) to the pay-per-call MCP server and makes provider-tool payments catalogable by the CDP Bazaar.
+`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.
 
-- **MCP 2026-07-28 (stateless, SEP-2575)** at `https://mcp.naxytra.com/mcp`: `server/discover` answers with the supported versions (`2026-07-28` first, then the handshake versions back to `2024-11-05`), the server capabilities, instructions and `serverInfo` (in result `_meta`, and top-level for SDKs built against the SEP as accepted). Requests that carry `io.modelcontextprotocol/protocolVersion` in `_meta` work without `initialize`, and the client is identified from `_meta` clientInfo. An unsupported version declared that way gets `-32022` with `supported` / `requested` and HTTP 400; an unknown method on a stateless request gets HTTP 404. Handshake clients (`initialize`) behave exactly as before, and the `MCP-Protocol-Version` header alone never changes that. CORS allows the `Mcp-Method` and `Mcp-Name` headers.
-- **Bazaar for provider tools:** a paid call to an independent provider's tool now reaches the payment facilitator with the server's resource (priced at the offer the buyer paid) and discovery extension when the buyer's client leaves them out, as own tools already did. The signed authorization is unchanged.
-- The daily buyer-journey report names the method and route for failures that carry no other detail, such as a runtime route that does not exist.
-- 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.11",
+  "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": {