xytara 3.9.12 → 3.9.14

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.14 makes x402 discovery (CDP Bazaar) decisions visible and keeps resource descriptions within the facilitator's limit. It also moves the remaining xoonya references to `https://api.naxytra.com/xoonya`.
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
+ - **Discovery decisions are visible:** the MCP server reads the facilitator's `EXTENSION-RESPONSES` (for example `{"bazaar":{"status":"processing"}}`, or `rejected` with a reason) on verify and settle. A settled call's payment response (`result._meta["x402/payment-response"]` and `PAYMENT-RESPONSE`) carries it as `extensions.bazaar`, and `GET https://mcp.naxytra.com/bazaar/status` lists the latest decisions per resource (resource URL, stage, status, reason; nothing about the payer).
4
+ - **Resource descriptions under 500 characters:** each tool's payment resource description now leads with the price and terms, and only the tool's blurb is shortened, so it stays under 480 characters.
5
+ - **xoonya address:** the runtime's links and summaries for the xoonya verifier use `https://api.naxytra.com/xoonya` (the same service, now served behind the runtime's host).
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.14",
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": {