Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

fix(x402): give the SIWX extension its origin so paid routes stop dying on import under @x402/extensions 2.25

nirholascfc1a8913b2f
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 7458ddd73..215fe692c 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,6 +4,11 @@
Public history for [three.ws](https://three.ws), newest first. New pages come from `added` dates in data/pages.json; everything else is curated in data/changelog.json. Also available as [JSON](https://three.ws/changelog.json) and [RSS](https://three.ws/changelog.xml), live at [three.ws/changelog](https://three.ws/changelog).
+## 2026-09-18
+
+- **Granite Guardian now answers on three.ws, not just in the docs**: The governance check that screens what an agent is asked to do, and vetoes it when the request is a jailbreak, harmful, or fraudulent, runs on IBM Granite Guardian. It was built to call IBM's hosted watsonx.ai service, so on our live site it answered with a not-configured error, and the new agent identity check quietly skipped itself for the same reason. IBM publishes Granite Guardian's weights openly, so we now run the model ourselves on a dedicated GPU as a second lane: watsonx still leads wherever it is set up, and our own copy answers whenever it is not. Every verdict now says which model and which lane produced it. The identity check also compares a new agent against existing ones using the site's regular embedding service when Granite embeddings are unavailable; it lists the look-alikes it finds but only scores them on Granite, because that is what its thresholds were tuned on. (`/docs/ibm`) `[fix, infra]`
+- **Paid x402 endpoints are answering again**: For several hours on September 18, nearly every paid endpoint on three.ws, the x402 discovery document at /.well-known/x402, the payment facilitator and the MCP server answered with a server error instead of a price. A routine update to the library behind wallet sign-in changed what it needs at startup, and our code tripped over it the moment it loaded, before any request could be served. Agents and marketplace validators that probed us saw a broken seller. The sign-in code now supplies what the library expects, returning buyers can sign back in to what they already paid for exactly as before, and the deploy checks now refuse to ship when the tested dependencies differ from the ones the live site will run, which is how this got past us. (`/docs/x402`) `[fix, infra]`
+
## 2026-09-17
- **Agent Wallet Agreement** (`/legal/agent-wallet`): The agreement governing every agent wallet: experimental custodial software, deposits by anyone at their own risk, no insurance, no guaranteed withdrawal or recovery, and no liability for lost funds.
diff --git a/api/_lib/siwx-server.js b/api/_lib/siwx-server.js
index 809be6f84..1221338c1 100644
--- a/api/_lib/siwx-server.js
+++ b/api/_lib/siwx-server.js
@@ -29,10 +29,31 @@ import { evmTransport } from './evm/rpc.js';
import { env } from './env.js';
import { siwxStorage, normalizeAddress } from './siwx-storage.js';
-const siwxResourceServerExtension = createSIWxResourceServerExtension({ storage: siwxStorage });
-
export { SIGN_IN_WITH_X };
+// @x402/extensions >= 2.25 binds a resource-server extension to one configured
+// origin and throws at construction when none is given, so the extension can no
+// longer be a module-level singleton built from storage alone (that threw on
+// import and took every paidEndpoint() route down with it). The origin comes
+// from the resource URL, which the server builds from env.APP_ORIGIN and never
+// from a request header, so a caller cannot steer it. One extension per origin,
+// built on first use.
+const extensionsByOrigin = new Map();
+
+function siwxOriginOf(resourceUrl) {
+ return new URL(resourceUrl).origin;
+}
+
+function extensionFor(resourceUrl) {
+ const origin = siwxOriginOf(resourceUrl);
+ let extension = extensionsByOrigin.get(origin);
+ if (!extension) {
+ extension = createSIWxResourceServerExtension({ storage: siwxStorage, origin });
+ extensionsByOrigin.set(origin, extension);
+ }
+ return extension;
+}
+
// Lazily build a viem PublicClient so verifySIWxSignature can verify
// smart-contract wallets (EIP-1271) and counterfactual wallets (EIP-6492).
// Uses our private RPC (env.BASE_RPC_URL) first so buyer addresses are not
@@ -83,13 +104,37 @@ export async function declareSiwxExtensionFor({
expirationSeconds,
});
const declaration = stub[SIGN_IN_WITH_X];
- const enriched = await siwxResourceServerExtension.enrichPaymentRequiredResponse(declaration, {
+ const enriched = await extensionFor(resourceUrl).enrichPaymentRequiredResponse(declaration, {
resourceInfo: { url: resourceUrl },
requirements: unique.map((network) => ({ network })),
});
return { [SIGN_IN_WITH_X]: enriched };
}
+// Check a parsed SIWX payload: the message must belong to this origin, be
+// fresh, and carry an unused nonce, and the signature must verify (EOA,
+// EIP-1271, EIP-6492, or Solana ed25519). Shared by the paidEndpoint() re-entry
+// path below and the auth-hints path (api/_lib/x402/auth-hints.js) so both
+// track the library's result shape in one place. Returns
+// `{ ok: true, address }` with the address already normalized, or
+// `{ ok: false, stage: 'message' | 'signature', error }`.
+export async function verifySiwxProof({ payload, resourceUrl }) {
+ const validation = await validateSIWxMessage(payload, new URL(siwxOriginOf(resourceUrl)), {
+ maxAge: 5 * 60 * 1000,
+ checkNonce: async (n) => !(await siwxStorage.hasUsedNonce(n)),
+ });
+ if (!validation.isValid) {
+ return { ok: false, stage: 'message', error: validation.invalidMessage };
+ }
+
+ const verification = await verifySIWxSignature(payload, { evmVerifier: getEvmVerifier() });
+ if (!verification.isValid || !verification.payer) {
+ return { ok: false, stage: 'signature', error: verification.invalidMessage };
+ }
+
+ return { ok: true, address: normalizeAddress(payload.chainId, verification.payer) };
+}
+
// Given an incoming Vercel request, attempt to authenticate via
// SIGN-IN-WITH-X. Returns:
// { ok: true, address, network } on full success.
@@ -111,20 +156,13 @@ export async function authenticateSiwx({ req, resourceUrl }) {
return { ok: false, status: 400, code: 'siwx_parse_failed', error: err.message };
}
- const validation = await validateSIWxMessage(payload, resourceUrl, {
- maxAge: 5 * 60 * 1000,
- checkNonce: async (n) => !(await siwxStorage.hasUsedNonce(n)),
- });
- if (!validation.valid) {
- return { ok: false, status: 401, code: 'siwx_message_invalid', error: validation.error };
- }
-
- const verification = await verifySIWxSignature(payload, { evmVerifier: getEvmVerifier() });
- if (!verification.valid || !verification.address) {
- return { ok: false, status: 401, code: 'siwx_signature_invalid', error: verification.error };
+ const proof = await verifySiwxProof({ payload, resourceUrl });
+ if (!proof.ok) {
+ const code = proof.stage === 'message' ? 'siwx_message_invalid' : 'siwx_signature_invalid';
+ return { ok: false, status: 401, code, error: proof.error };
}
- const normalizedAddress = normalizeAddress(payload.chainId, verification.address);
+ const normalizedAddress = proof.address;
if (!(await siwxStorage.hasPaid(resourceUrl, normalizedAddress))) {
return {
ok: false,
diff --git a/api/_lib/x402/auth-hints.js b/api/_lib/x402/auth-hints.js
index d99298b31..42826a2ee 100644
--- a/api/_lib/x402/auth-hints.js
+++ b/api/_lib/x402/auth-hints.js
@@ -25,18 +25,12 @@
// - auth-hints SIWX is a free alternative to payment — the wallet just
// needs to sign a fresh CAIP-122 challenge.
-import {
- parseSIWxHeader,
- validateSIWxMessage,
- verifySIWxSignature,
-} from '@x402/extensions/sign-in-with-x';
-import { createPublicClient } from 'viem';
-import { base } from 'viem/chains';
-import { evmTransport } from '../evm/rpc.js';
+import { parseSIWxHeader } from '@x402/extensions/sign-in-with-x';
import { env } from '../env.js';
import { authenticateBearer, hasScope } from '../auth.js';
-import { siwxStorage, normalizeAddress } from '../siwx-storage.js';
+import { siwxStorage } from '../siwx-storage.js';
+import { verifySiwxProof } from '../siwx-server.js';
export const AUTH_HINTS_EXTENSION_KEY = 'auth-hints';
export const SIWX_HEADER = 'sign-in-with-x';
@@ -208,21 +202,6 @@ function readSiwxHeader(req) {
return typeof raw === 'string' && raw.length > 0 ? raw : null;
}
-// Lazy viem client used to verify EIP-1271 / EIP-6492 smart-wallet signatures.
-// Mirrors siwx-server.js so both code paths share the same RPC.
-let _baseClient;
-function getEvmVerifier() {
- if (!env.BASE_RPC_URL) return undefined;
- if (!_baseClient) {
- // BASE_RPC_URL stays primary (a private node, so buyer addresses are not
- // broadcast to public RPCs on the happy path); the shared Base endpoints
- // only take over when it fails, so a dead private node cannot block
- // every smart-wallet sign-in.
- _baseClient = createPublicClient({ chain: base, transport: evmTransport(base.id, { primaryUrl: env.BASE_RPC_URL }) });
- }
- return _baseClient.verifyMessage.bind(_baseClient);
-}
-
/**
* Verify a SIGN-IN-WITH-X header against the auth-hints contract:
* - parse the CAIP-122 envelope (delegated to @x402/extensions)
@@ -246,20 +225,12 @@ export async function verifyAuthHintsSiwx({ req, resourceUrl }) {
return { ok: false, reason: 'invalid_siwx_proof' };
}
- const validation = await validateSIWxMessage(payload, resourceUrl, {
- maxAge: 5 * 60 * 1000,
- checkNonce: async (n) => !(await siwxStorage.hasUsedNonce(n)),
- });
- if (!validation.valid) {
- return { ok: false, reason: 'invalid_siwx_message', detail: validation.error };
+ const proof = await verifySiwxProof({ payload, resourceUrl });
+ if (!proof.ok) {
+ const reason = proof.stage === 'message' ? 'invalid_siwx_message' : 'invalid_siwx_signature';
+ return { ok: false, reason, detail: proof.error };
}
-
- const verification = await verifySIWxSignature(payload, { evmVerifier: getEvmVerifier() });
- if (!verification.valid || !verification.address) {
- return { ok: false, reason: 'invalid_siwx_signature', detail: verification.error };
- }
-
- const address = normalizeAddress(payload.chainId, verification.address);
+ const address = proof.address;
// Atomically claim the nonce so the proof can't be replayed against this
// endpoint. The claim is the authoritative gate, not the earlier
diff --git a/data/changelog.json b/data/changelog.json
index 5cbe4418e..391f82300 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,11 +1,24 @@
{
"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.",
"entries": [
+ {
+ "date": "2026-09-18",
+ "title": "Paid x402 endpoints are answering again",
+ "summary": "For several hours on September 18, nearly every paid endpoint on three.ws, the x402 discovery document at /.well-known/x402, the payment facilitator and the MCP server answered with a server error instead of a price. A routine update to the library behind wallet sign-in changed what it needs at startup, and our code tripped over it the moment it loaded, before any request could be served. Agents and marketplace validators that probed us saw a broken seller. The sign-in code now supplies what the library expects, returning buyers can sign back in to what they already paid for exactly as before, and the deploy checks now refuse to ship when the tested dependencies differ from the ones the live site will run, which is how this got past us.",
+ "tags": [
+ "fix",
+ "infra"
+ ],
+ "link": "/docs/x402"
+ },
{
"date": "2026-09-18",
"title": "Granite Guardian now answers on three.ws, not just in the docs",
"summary": "The governance check that screens what an agent is asked to do, and vetoes it when the request is a jailbreak, harmful, or fraudulent, runs on IBM Granite Guardian. It was built to call IBM's hosted watsonx.ai service, so on our live site it answered with a not-configured error, and the new agent identity check quietly skipped itself for the same reason. IBM publishes Granite Guardian's weights openly, so we now run the model ourselves on a dedicated GPU as a second lane: watsonx still leads wherever it is set up, and our own copy answers whenever it is not. Every verdict now says which model and which lane produced it. The identity check also compares a new agent against existing ones using the site's regular embedding service when Granite embeddings are unavailable; it lists the look-alikes it finds but only scores them on Granite, because that is what its thresholds were tuned on.",
- "tags": ["fix", "infra"],
+ "tags": [
+ "fix",
+ "infra"
+ ],
"link": "/docs/ibm"
},
{
diff --git a/public/changelog-recent.json b/public/changelog-recent.json
index 9fd9ca0c2..cce23f1c4 100644
--- a/public/changelog-recent.json
+++ b/public/changelog-recent.json
@@ -1,14 +1,36 @@
{
- "generated_at": "2026-09-17T23:48:58.720Z",
+ "generated_at": "2026-09-18T07:13:35.035Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
"url": "https://three.ws"
},
- "total": 3701,
+ "total": 3703,
"complete": false,
"full_feed": "/changelog.json",
"entries": [
+ {
+ "date": "2026-09-18",
+ "type": "update",
+ "title": "Granite Guardian now answers on three.ws, not just in the docs",
+ "summary": "The governance check that screens what an agent is asked to do, and vetoes it when the request is a jailbreak, harmful, or fraudulent, runs on IBM Granite Guardian. It was built to call IBM's hosted watsonx.ai service, so on our live site it answered with a not-configured error, and the new agent identity check quietly skipped itself for the same reason. IBM publishes Granite Guardian's weights openly, so we now run the model ourselves on a dedicated GPU as a second lane: watsonx still leads wherever it is set up, and our own copy answers whenever it is not. Every verdict now says which model and which lane produced it. The identity check also compares a new agent against existing ones using the site's regular embedding service when Granite embeddings are unavailable; it lists the look-alikes it finds but only scores them on Granite, because that is what its thresholds were tuned on.",
+ "link": "/docs/ibm",
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
+ {
+ "date": "2026-09-18",
+ "type": "update",
+ "title": "Paid x402 endpoints are answering again",
+ "summary": "For several hours on September 18, nearly every paid endpoint on three.ws, the x402 discovery document at /.well-known/x402, the payment facilitator and the MCP server answered with a server error instead of a price. A routine update to the library behind wallet sign-in changed what it needs at startup, and our code tripped over it the moment it loaded, before any request could be served. Agents and marketplace validators that probed us saw a broken seller. The sign-in code now supplies what the library expects, returning buyers can sign back in to what they already paid for exactly as before, and the deploy checks now refuse to ship when the tested dependencies differ from the ones the live site will run, which is how this got past us.",
+ "link": "/docs/x402",
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
{
"date": "2026-09-17",
"type": "launch",
@@ -1598,27 +1620,6 @@
"fix",
"docs"
]
- },
- {
- "date": "2026-09-08",
- "type": "update",
- "title": "The changelog page no longer downloads three and a half thousand entries to show you this week",
- "summary": "Opening the changelog fetched the entire history, every entry since the site existed, and wrote all of it into the page in one go: 870 KB over the wire and, on a mid-range phone over a slow connection, eleven seconds where the page would not respond to anything. It now paints the newest 150 entries from a small feed and pages in the rest only when you filter or ask for older updates, so the thing you came for is on screen almost immediately and the full history is one tap away. Entry pages, the What's New strip on the features page and the Walk changelog read the small feed too. The complete feed at /changelog.json is unchanged and still the one to use if you are building on it.",
- "link": "/changelog",
- "tags": [
- "improvement"
- ]
- },
- {
- "date": "2026-09-08",
- "type": "update",
- "title": "The ChatGPT and AR docs now describe the AR launcher that actually runs",
- "summary": "Three corrections to the documentation for the ChatGPT surfaces and augmented reality. The AR reference still said the one-tap launcher at /api/ar draws the model itself in Google's model-viewer, which stopped being true when the launcher became a pure router: it now sends Android straight into Scene Viewer and everyone else to a bundled page that builds a real USDZ on the device, which is what iPhone's Quick Look needs. The pages are named correctly throughout, including which one does the file conversion, so nobody debugging an iPhone handoff starts in the wrong file. The ChatGPT AR page also credited a single generation engine for every model, when the connector actually tries the free engines in turn and steps down to a slower one if the first is cold, which is why generation keeps working when one lane is down. And the paid studio server's page promised that anyone can browse its tool catalogue without credentials, without mentioning that a connector client is deliberately answered with a sign-in challenge instead, as the connector standard requires; both paths are now written down, with a command that works. That page's tool tables also describe nine tools that were previously only named in its price list, so no tool appears with a price and no explanation.",
- "link": "/docs/ar",
- "tags": [
- "docs",
- "fix"
- ]
}
]
}
diff --git a/public/changelog.json b/public/changelog.json
index a9216297f..bca648cfd 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,11 +1,33 @@
{
- "generated_at": "2026-09-17T23:48:58.691Z",
+ "generated_at": "2026-09-18T07:13:35.000Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
"url": "https://three.ws"
},
"entries": [
+ {
+ "date": "2026-09-18",
+ "type": "update",
+ "title": "Granite Guardian now answers on three.ws, not just in the docs",
+ "summary": "The governance check that screens what an agent is asked to do, and vetoes it when the request is a jailbreak, harmful, or fraudulent, runs on IBM Granite Guardian. It was built to call IBM's hosted watsonx.ai service, so on our live site it answered with a not-configured error, and the new agent identity check quietly skipped itself for the same reason. IBM publishes Granite Guardian's weights openly, so we now run the model ourselves on a dedicated GPU as a second lane: watsonx still leads wherever it is set up, and our own copy answers whenever it is not. Every verdict now says which model and which lane produced it. The identity check also compares a new agent against existing ones using the site's regular embedding service when Granite embeddings are unavailable; it lists the look-alikes it finds but only scores them on Granite, because that is what its thresholds were tuned on.",
+ "link": "/docs/ibm",
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
+ {
+ "date": "2026-09-18",
+ "type": "update",
+ "title": "Paid x402 endpoints are answering again",
+ "summary": "For several hours on September 18, nearly every paid endpoint on three.ws, the x402 discovery document at /.well-known/x402, the payment facilitator and the MCP server answered with a server error instead of a price. A routine update to the library behind wallet sign-in changed what it needs at startup, and our code tripped over it the moment it loaded, before any request could be served. Agents and marketplace validators that probed us saw a broken seller. The sign-in code now supplies what the library expects, returning buyers can sign back in to what they already paid for exactly as before, and the deploy checks now refuse to ship when the tested dependencies differ from the ones the live site will run, which is how this got past us.",
+ "link": "/docs/x402",
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
{
"date": "2026-09-17",
"type": "launch",
diff --git a/public/changelog.xml b/public/changelog.xml
index 4024a511b..78716f955 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -6,6 +6,22 @@
<atom:link href="https://three.ws/changelog.xml" rel="self" type="application/rss+xml"/>
<description>What's new on three.ws: features, improvements, and releases, newest first.</description>
<language>en</language>
+ <item>
+ <title>Granite Guardian now answers on three.ws, not just in the docs</title>
+ <link>https://three.ws/docs/ibm</link>
+ <guid isPermaLink="false">2026-09-18:Granite Guardian now answers on three.ws, not just in the docs</guid>
+ <pubDate>Fri, 18 Sep 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The governance check that screens what an agent is asked to do, and vetoes it when the request is a jailbreak, harmful, or fraudulent, runs on IBM Granite Guardian. It was built to call IBM's hosted watsonx.ai service, so on our live site it answered with a not-configured error, and the new agent identity check quietly skipped itself for the same reason. IBM publishes Granite Guardian's weights openly, so we now run the model ourselves on a dedicated GPU as a second lane: watsonx still leads wherever it is set up, and our own copy answers whenever it is not. Every verdict now says which model and which lane produced it. The identity check also compares a new agent against existing ones using the site's regular embedding service when Granite embeddings are unavailable; it lists the look-alikes it finds but only scores them on Granite, because that is what its thresholds were tuned on.</description>
+ </item>
+ <item>
+ <title>Paid x402 endpoints are answering again</title>
+ <link>https://three.ws/docs/x402</link>
+ <guid isPermaLink="false">2026-09-18:Paid x402 endpoints are answering again</guid>
+ <pubDate>Fri, 18 Sep 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>For several hours on September 18, nearly every paid endpoint on three.ws, the x402 discovery document at /.well-known/x402, the payment facilitator and the MCP server answered with a server error instead of a price. A routine update to the library behind wallet sign-in changed what it needs at startup, and our code tripped over it the moment it loaded, before any request could be served. Agents and marketplace validators that probed us saw a broken seller. The sign-in code now supplies what the library expects, returning buyers can sign back in to what they already paid for exactly as before, and the deploy checks now refuse to ship when the tested dependencies differ from the ones the live site will run, which is how this got past us.</description>
+ </item>
<item>
<title>Agent Wallet Agreement</title>
<link>https://three.ws/legal/agent-wallet</link>
diff --git a/public/features.json b/public/features.json
index 92791e1ab..73aa446ae 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-17T23:48:58.673Z",
+ "generated_at": "2026-09-18T07:13:34.969Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
diff --git a/tests/api/auth-hints.test.js b/tests/api/auth-hints.test.js
index 3b6f4c4dd..4775295c1 100644
--- a/tests/api/auth-hints.test.js
+++ b/tests/api/auth-hints.test.js
@@ -219,7 +219,7 @@ describe('authenticateAuthHintsRequest — SIWX (EOA)', () => {
issuedAt: new Date().toISOString(),
expirationTime: new Date(Date.now() + 5 * 60_000).toISOString(),
};
- const payload = await createSIWxPayload(serverExtension, signer);
+ const payload = await createSIWxPayload(serverExtension, signer, serverExtension.uri);
header = encodeSIWxHeader(payload);
});
@@ -276,6 +276,7 @@ describe('authenticateAuthHintsRequest — SIWX (EOA)', () => {
expirationTime: new Date(Date.now() + 5 * 60_000).toISOString(),
},
signer,
+ 'https://app.test/api/x402/agent-reputation',
);
const replayHeader = encodeSIWxHeader(payload);
const req = { headers: { 'sign-in-with-x': replayHeader } };
diff --git a/tests/api/x402-paid-endpoint-siwx.test.js b/tests/api/x402-paid-endpoint-siwx.test.js
index 1e8c2d449..b7f2780b4 100644
--- a/tests/api/x402-paid-endpoint-siwx.test.js
+++ b/tests/api/x402-paid-endpoint-siwx.test.js
@@ -116,12 +116,12 @@ function solanaAdapterSigner(kp) {
async function signSiwxFromChallenge(challenge, signer, chainId) {
const info = challenge.extensions[SIGN_IN_WITH_X].info;
const completeInfo = { ...info, chainId, type: 'ed25519' };
- const payload = await createSIWxPayload(completeInfo, signer);
+ // The client binds the challenge to the origin it was served from, so the
+ // request URL is the challenge's own uri.
+ const payload = await createSIWxPayload(completeInfo, signer, info.uri);
return encodeSIWxHeader(payload);
}
-describeIfDb('paidEndpoint() + siwx', () => {});
-
function describeIfDb(name, fn) {
if (HAS_DB) return describe(name, fn);
return describe.skip(name, fn);