Developer resources

One core. Four interfaces.

HTTP owns the Commerce contract. MCP, the JavaScript SDK and CLI are thin adapters to it.

Canonical service

Inspect before you integrate.

No wallet key, autonomous signer or mainnet settlement address is included.

Commerce discovery OpenAPI 3.1 contract Commercial status and inactive launch anchors Adapter availability Sandbox workflow

JavaScript SDK

Dependency-free ESM.

The client accepts a configurable base URL, but state changes fail unless discovery proves the approved synthetic XRPL Testnet contract.

import { AgentiScriptCommerceClient } from './src/index.js';

const commerce = new AgentiScriptCommerceClient();
const catalog = await commerce.catalog({ query: 'concept' });

Download SDK and CLI source

MCP and CLI

Use the interface that fits the workflow.

MCP uses Streamable HTTP at the canonical service. The CLI delegates to the SDK and keeps sensitive Testnet values out of command-line arguments.

node adapters/cli/bin/agentiscript-commerce.mjs catalog --query concept

node adapters/cli/bin/agentiscript-commerce.mjs quote \
  --family concept-definition \
  --slug agent-identity \
  --idempotency-key your-unique-key \
  --ack XRPL_TESTNET_SYNTHETIC_ONLY

Boundary: this sandbox can create synthetic Testnet quotes and validate Testnet payments. It does not authorize mainnet, real charging, autonomous spending, NFT sales or minting.