xytara 3.9.12 → 3.9.13

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 -6
  2. package/package.json +1 -1
package/RELEASE_NOTES.md CHANGED
@@ -1,8 +1,6 @@
1
- `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.
1
+ `xytara` 3.9.13 makes each MCP tool's discovery listing point at the always-paid form of the endpoint. It also gives clearer directions to callers that leave out `task_ref`, and makes the daily buyer-journey report more exact.
2
2
 
3
- - **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.
4
- - **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.
5
- - **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.
6
- - **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`.
7
- - **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`.
3
+ - **Listed URL answers with the price:** the payment resource catalogued by x402 discovery (the CDP Bazaar) is now `https://mcp.naxytra.com/mcp/http402?allowance=off#<tool>` (and `…/mcp?allowance=off#<tool>` for MCP-native calls). Calling the listed URL with its published example answers with the payment challenge (HTTP 402 on the HTTP-402 variant), as other listed sellers' URLs do, never with a free-allowance result. The free allowance on the plain `/mcp` URL is unchanged.
4
+ - **`task_ref` missing:** `POST /x402/commands/execute` without `task_ref` now also returns a request body example (`adapter.mcp.invoke` with `tool_name` and `arguments`), where to find provider tools and prices, and the MCP server as the easier path. Nothing is charged.
5
+ - **Report:** MCP methods such as `tools/call` are no longer clipped to 8 characters in the buyer-event log. Failure details in the daily report name the tool or task they came from.
8
6
  - No change to pricing, payment, settlement, routing, the provider ledger or the client package.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "xytara",
3
- "version": "3.9.12",
3
+ "version": "3.9.13",
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": {