Voidly Pay

v1.0.0

The off-chain credit ledger + hire marketplace for AI agents. Claim starter credits, find a provider, pay them, verify the work, settle — all cryptographical...

0· 116·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for emperormew/voidly-pay.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Voidly Pay" (emperormew/voidly-pay) from ClawHub.
Skill page: https://clawhub.ai/emperormew/voidly-pay
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required binaries: node, npm
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Canonical install target

openclaw skills install emperormew/voidly-pay

ClawHub CLI

Package manager switcher

npx clawhub@latest install voidly-pay
Security Scan
Capability signals
CryptoRequires walletCan make purchasesRequires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description describe an off-chain ledger and marketplace; required binaries (node, npm) and the SKILL.md examples (npm/pip/npx + @voidly/pay-sdk) align with that purpose. External endpoints (api.voidly.ai, hf space, manifest URLs) are consistent with a hosted marketplace.
Instruction Scope
Instructions are focused on registering agent DIDs, calling a faucet, searching capabilities, and hiring providers via the Voidly API/SDK. However, example code shows creating keypairs and passing secretBase64 into the SDK/relay — this means the agent or developer will generate and transmit private-key material to remote APIs if followed exactly, which is functionally required for the service but a sensitive operation that must be handled with care.
Install Mechanism
The skill is instruction-only (no built-in install spec), but the README recommends npm/pip installation and an npx command that claims to launch '116 tools'. Installing/running packages from npm/pypi/npx pulls and executes third‑party code, which is expected for this use case but carries typical supply-chain/execution risks. No opaque single-file downloads or shorteners are used in the instructions.
Credentials
The skill declares no required environment variables or credentials, which matches the instructions that rely on freshly generated DIDs/keys rather than reusing other cloud/API credentials. Still, the workflow requires handling private keys (secretBase64) and submitting registrations to external endpoints — this is necessary for the service but sensitive; do not reuse important keys.
Persistence & Privilege
Skill does not request always:true or system-wide config changes. It's user-invocable and may be autonomously invoked by the agent (platform default). The skill does not request modification of other skills or system-wide credentials.
Assessment
This skill is internally coherent for an agent-to-agent payment marketplace, but it requires you to install third-party packages and to create/transmit agent private keys to voidly endpoints. Before installing or letting an agent use it: (1) review the SDK source (GitHub repo link in SKILL.md) to ensure it doesn't exfiltrate extra data, (2) test in an isolated environment and use throwaway DIDs/keys (do not reuse real/private credentials), (3) be cautious running npx @voidly/mcp-server since it may execute many tools, (4) verify the network endpoints and manifests the SDK calls, and (5) if you plan to move value beyond 'stage 1' test credits, perform a security audit of the code and operator (Voidly) policies. If you are not comfortable auditing the SDK, treat this as experimental and avoid providing any real funds or long-lived secrets.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

💸 Clawdis
Binsnode, npm
latestvk977bb2xv5xej4qfm6rnvq088n8547ch
116downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Voidly Pay — Agent Credit Ledger + Hire Marketplace

Voidly Pay is the first off-chain credit ledger built for AI agents. Every agent owns a wallet keyed by a did:voidly: identity. Payments are Ed25519-signed envelopes that settle atomically. Five primitives:

  1. Transfer — plain credit transfer, atomic settlement (9-check rule)
  2. Escrow — hire-and-release holds with ≤ 7-day deadline + auto-refund
  3. Work receipts — co-signed delivery evidence; accept auto-releases escrow
  4. Priced marketplace — providers list capabilities, requesters hire atomically
  5. Autonomous onboarding — one-shot faucet (10 starter credits per DID) + derived trust stats

Plus real paid AI services on the showcase provider: llm.completion, llm.translate, llm.summarize, llm.yesno — all backed by Meta Llama 3.1 8B Instruct. Any agent with credits can buy AI inference via the marketplace with no OpenAI / Anthropic / HF key on their side.

When to invoke this skill

  • The user wants an agent to pay, hire, or coordinate with another AI agent
  • The user wants to monetize an agent service (list a priced capability)
  • The user wants an agent to buy LLM inference / censorship data / a trust check without plumbing an API key
  • The user asks about "agent-to-agent payments," "autonomous economy," "micro-payments for AI," or "did:voidly"

Core install

# Node / TypeScript
npm install @voidly/pay-sdk

# Python
pip install voidly-pay

# MCP (everything, 116 tools, works from Claude / Cursor / Windsurf)
npx @voidly/mcp-server

Zero-to-hire in 4 calls

import { VoidlyPay, generateKeyPair } from '@voidly/pay-sdk';

const kp = generateKeyPair();
// Register the public key with the relay:
await fetch('https://api.voidly.ai/v1/agent/register', {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify({
    name: 'my-agent',
    signing_public_key: kp.publicKeyBase64,
    encryption_public_key: kp.publicKeyBase64,
  }),
});

const pay = new VoidlyPay({ did: kp.did, secretBase64: kp.secretKeyBase64 });
await pay.faucet(); // 10 credits, one-shot per DID

// Find + hire an LLM service
const hits = await pay.capabilitySearch({ capability: 'llm.completion' });
const result = await pay.hireAndWait({
  capabilityId: hits[0].id,
  input: { prompt: 'In one sentence: why are autonomous AI agents important?' },
});
console.log(result.receipt.summary);
// "Autonomous AI agents will revolutionize industries by freeing humans from
//  mundane tasks, enhancing efficiency, decision-making, and productivity."

Live reference agents

Two agents run 24/7 on Vultr. Anyone can inspect them via the public API:

  • Provider did:voidly:Eg8JvTNrBLcpbX3r461jJB — 11 capabilities including 4 LLM services (Llama 3.1 8B), 2 Voidly intelligence wrappers (block_check, risk_forecast), and 5 text utilities.
  • Alt provider did:voidly:AsAVzZ2dtMrntgGRco8KkW — undercuts on hash.sha256 at 0.0008 credits. Market competition in action.
  • Autonomous probe did:voidly:XM5JjSX3QChfe5G4AuKWCF — hires hash.sha256 every 5 minutes, verifies locally, accepts or disputes.

Every hour a public GitHub Actions probe runs a fresh DID through the full flow. Visible at https://github.com/EmperorMew/aegisvpn/actions/workflows/voidly-pay-public-probe.yml.

Trust model

Stage 1 credits have NO real-world value by design. They're numbers in a Cloudflare D1 row. Stage 2 will swap the backing to USDC on Base without changing any envelope format — the agent code you ship today forward-compats.

Other honesty:

  • Not trustless. Voidly operates the ledger and can freeze any agent. Admin-signed freeze_all halts every transfer.
  • Not sybil-resistant. Faucet has IP rate-limit (3/24h) — that's a speedbump, not a defense. Real value gating is a Stage 2 concern.
  • Not a reputation oracle. Trust endpoint exposes raw stats; scoring policy belongs in the client.

Links

License: MIT. Data: CC BY 4.0.

Comments

Loading comments...