SDK & Agent Tooling

Mercenta provides client packages, smart contract primitives, and agent skill manifests for programmatic procurement, machine checkout, and storefront deployment.

For complete NPM documentation and usage guides, see the dedicated NPM Packages & Libraries guide.

1. Published NPM Packages

All packages are published on the official NPM Registry under the verified mercenta publisher identity:

mercenta-primitives: Reusable Arc smart contracts, 5-step PolicyGate, x402 payment rails, and Viem utilities.
```
npm install mercenta-primitives
```
mercenta-client: Lightweight, dependency-free public catalogue client SDK.
```
npm install mercenta-client
```
mercenta-aomi-skill: Canonical agent skill for Claude Code, Cursor, Codex, OpenCode, and Hermes.
```
npm install mercenta-aomi-skill
# or
npx skills add rdmbtc/mercenta
```

2. Server Integration & HTTP APIs

For custom backend pipelines, Mercenta exposes standard REST endpoints authenticated with scoped API keys. Keep API keys strictly server-side and configure reasonable request timeouts:

Endpoints Reference: API Endpoints
Authentication: API Authentication Guide
Swagger / OpenAPI: Interactive Specification

Circle App Kit and the Viem adapter are server integration dependencies. Human wallet signatures or deterministic policy engine clearances are required for blockchain execution. No model receives an unconstrained wallet private key.

3. Telegram Storefront Starter

To launch a branded RU/EN bot, see the Telegram shop starter guide. It includes a turnkey starter, public branding configuration, Python/SQLite long polling, and a hardened VPS systemd service example.

4. Supply & Fulfillment Boundaries

Internal supply integrations are represented strictly as Wholesale Provider or Fulfillment Gateway. Proprietary vendor credentials, upstream account keys, and direct supplier identities are shielded behind the secure execution vault and are never exposed across public API contracts.