xytara 3.1.7 → 3.1.8

package/RELEASE_NOTES.md

@@ -1,11 +1,9 @@
-`xytara` 3.1.7 completes the Coinbase CDP facilitator path, proven with a real Base mainnet settlement.
+`xytara` 3.1.8 refreshes the public MCP executor's machine-readable description so it leads with its pay-per-call story.
 
-A facilitator can signal a verification or settlement result either with a 200 and the result in the body, or with a non-2xx status and the same body. Coinbase CDP returns HTTP 400 for an invalid payment (with `{isValid:false, invalidReason, invalidMessage}`). The client previously treated any non-2xx as an unreachable transport error and never read the body, so a CDP verdict was misclassified. This release reads the result from the body regardless of HTTP status, which was the last blocker for Base mainnet settlement through CDP.
+The server card and discovery surfaces previously described the executor as a generic tool list ("summaries, DNS lookup, catalog, replies, and JSON checks"). They now lead with what matters to an agent: pay-per-call MCP tools settled with x402 (USDC on Base mainnet). This improves how the executor is presented wherever its card is pulled — the MCP registry, Glama, x402scan, and any discovery-aware agent.
 
 Highlights:
 
-- the facilitator client treats any `/verify` or `/settle` response that carries an `isValid` or `success` flag as the facilitator's result, regardless of HTTP status; only a missing or unparseable body is a transport failure
-- failure details now surface the facilitator's `invalidReason` / `invalidMessage` / `errorReason` and a truncated response-body excerpt, so operators can see exactly why a facilitator rejected a payment
-- adds regression checks for facilitators that return a non-2xx status with a result body
-- no change for facilitators that return 200 with the result; the default Base Sepolia path is unaffected
-- verified end to end: a real Base mainnet USDC payment settled on-chain through the CDP facilitator and minted self-serve credits
+- the executor's `server.json`, served server card, and 402 discovery description now read "Pay-per-call MCP tools for agents, settled with x402 (USDC on Base mainnet). No API keys."
+- bumps the MCP executor to 3.1.8; the release workflow republishes it to the official MCP registry with the new description, which Glama then syncs
+- no change to tools, payment, settlement, or any route

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "xytara",
-  "version": "3.1.7",
+  "version": "3.1.8",
   "description": "Agent-commerce runtime for quote, pay, execute, deliver, meter, and integrate.",
   "main": "index.js",
   "bin": {