Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Build and operate a metered public API endpoint ("agent microservice") for OpenClaw skills/agents with API-key auth, per-request usage logging + pricing, pre...
Build and operate a metered public API endpoint ("agent microservice") for OpenClaw skills/agents with API-key auth, per-request usage logging + pricing, pre...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Provide a production-lean template for: OpenClaw Skill → Public API Endpoint → Usage Metering → Crypto Payment Gateway → BTC/ETH wallets. This skill ships a runnable reference server (Fastify + SQLite) that: Accepts structured JSON input Performs a high-value transformation (pluggable “transformers”) Returns structured JSON output Enforces signed API key auth Checks prepaid balance, deducts per call, and logs usage Accepts payment webhooks (Coinbase Commerce / BTCPay Server style) Applies a 2.5% platform fee in the ledger (fee addresses configurable)
Choose ONE transformer that is: high leverage (makes/keeps money) repeatable (called often) defensible (data, heuristics, workflow, or automation — not “generic summarization”) Good defaults: revenue/offer optimizer ad copy optimizer lead scoring contract risk flags If unclear, start with the included revenue-amplifier transformer and replace it later.
Use the bundled server in scripts/server/. Typical run: cd scripts/server npm install cp .env.example .env and edit npm run dev Set flat launch pricing in .env: COST_CENTS_PER_CALL=25 # $0.25/call
Use scripts/server/admin/create_key_pg.js (or the admin HTTP endpoint) to create a key and starting balance.
Call the public endpoint with: x-api-key x-timestamp (unix ms) x-signature = hex(HMAC_SHA256(api_secret, ${timestamp}.${rawBody}))
Wire a payment processor webhook to /v1/payments/webhook/:provider. Providers are adapter-based: start with “manual” credits (admin script) then add Coinbase Commerce or BTCPay Server
Deploy behind TLS (Cloudflare / Fly.io / Render / AWS / GCP). Put rate limiting at the edge + in-app.
Runnable reference implementation: Fastify API server (long-running) Postgres ledger (balances, usage, credits) Signed API key auth Rate limiting + basic anti-abuse Webhook endpoint(s)
Vercel-ready Next.js API implementation: Serverless API routes (no listen()) Postgres ledger (Supabase Transaction Pooler recommended) Same auth + pricing + webhook concepts
Read only when needed: references/api_reference.md – endpoint contracts + auth/signing references/billing_ledger.md – pricing, fee logic, idempotency references/providers.md – provider adapters (Coinbase/BTCPay patterns)
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.