npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@pram1616/meshforge-sdk

v1.0.2

Published

MeshForge orchestration SDK for autonomous agent intent execution

Readme

@pram1616/meshforge-sdk

MeshForge orchestration SDK for autonomous agent intent execution.

Install

npm install @pram1616/meshforge-sdk viem

Requirements

  • A viem publicClient
  • A viem walletClient connected to the signer/controller account
  • Deployed MeshForge contracts (SDK includes default addresses used by MeshForge app)

Quick Start

import { createMeshForgeSdk } from '@pram1616/meshforge-sdk';
import { createPublicClient, createWalletClient, custom, http } from 'viem';
import { celoSepolia } from 'viem/chains';

const publicClient = createPublicClient({
  chain: celoSepolia,
  transport: http(process.env.NEXT_PUBLIC_RPC_URL),
});

const walletClient = createWalletClient({
  chain: celoSepolia,
  transport: custom(window.ethereum),
});

const [controller] = await walletClient.getAddresses();

const sdk = createMeshForgeSdk({
  publicClient,
  walletClient,
  controller,
  x402Endpoint: process.env.NEXT_PUBLIC_THIRDWEB_X402_ENDPOINT,
  x402ApiKey: process.env.NEXT_PUBLIC_THIRDWEB_X402_API_KEY,
  requireX402: false,
  autoAcceptIntent: false,
});

Main Usage (fulfillIntent)

import { createMeshForgeSdk } from '@pram1616/meshforge-sdk';

const sdk = createMeshForgeSdk({
  publicClient,
  walletClient,
  controller: '0xYourController',
  x402Endpoint: process.env.NEXT_PUBLIC_THIRDWEB_X402_ENDPOINT,
  x402ApiKey: process.env.NEXT_PUBLIC_THIRDWEB_X402_API_KEY,
});

const result = await sdk.fulfillIntent({
  taskType: 'cross_border_payment',
  value: '100',
  fromRegion: 'KE',
  toRegion: 'UG',
  executionSteps: [
    { id: '1', label: 'lock_escrow' },
    { id: '2', label: 'execute_transfer' },
    { id: '3', label: 'settlement' }
  ],
  riskProfile: 'CROSS_BORDER',
});

console.log({
  intentId: result.intentId,
  status: result.status.status,
  stageTrace: result.stageTrace,
  relayedByX402: result.relayed,
  route: result.routePlan,
});

API Surface

  • createMeshForgeSdk(config)

    • config.publicClient: viem public client
    • config.walletClient: viem wallet client
    • config.controller: signer/controller address (0x...)
    • config.x402Endpoint?: x402 relay endpoint
    • config.x402ApiKey?: x402 API key
    • config.requireX402?: when true, throws if x402 env/config is missing
    • config.autoAcceptIntent?: auto-run acceptIntent stage when possible
  • sdk.fulfillIntent(input) / sdk.executeTask(input)

    • High-level orchestration flow: identity → broadcast → route metadata → escrow/execution/proof (best-effort by role) → trace commit → dispute/settlement logic
  • sdk.getExecutionStatus({ intentId })

    • Returns status object with statusCode, status, merkleRoot, dispute flags, and actor addresses
  • sdk.submitExecutionTrace({ intentId, executionSteps, step? })

    • Builds merkle root from step data and commits it on-chain
  • sdk.settleIntent({ intentId })

    • Attempts to settle intent lifecycle
  • Legacy primitives:

    • sdk.broadcastIntent(title, description, valueCusd)
    • sdk.acceptIntent(intentId)

Input Reference

FulfillIntentInput important fields:

  • taskType: string
  • value: number | string
  • fromRegion: string (e.g. KE)
  • toRegion: string (e.g. UG)
  • executionSteps: { id, label, payload?, timestamp? }[]
  • Optional: riskProfile, trustRequirements, route, metadataURI, title, description, existingIntentId

x402 Notes

  • x402 relay is optional by default.
  • If requireX402: true, SDK throws when endpoint/key are unavailable.
  • Env fallback keys supported:
    • Endpoint: NEXT_PUBLIC_THIRDWEB_X402_ENDPOINT, NEXT_PUBLIC_X402_ENDPOINT, THIRDWEB_X402_ENDPOINT, X402_ENDPOINT
    • API key: NEXT_PUBLIC_THIRDWEB_X402_API_KEY, NEXT_PUBLIC_X402_API_KEY, THIRDWEB_X402_API_KEY, X402_API_KEY

Build

npm run build

Publish

npm login
npm publish --access public

License

MIT