NEXUS Translate

v1.1.0

High-quality translations with cultural awareness (50+ languages)

0· 345·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 cyberforexblockchain/nexus-translate.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "NEXUS Translate" (cyberforexblockchain/nexus-translate) from ClawHub.
Skill page: https://clawhub.ai/cyberforexblockchain/nexus-translate
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEXUS_PAYMENT_PROOF
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 cyberforexblockchain/nexus-translate

ClawHub CLI

Package manager switcher

npx clawhub@latest install nexus-translate
Security Scan
Capability signals
CryptoCan make purchases
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 (translation) align with the SKILL.md: the skill purely documents calling an external translation API and payment flows. The single required env var (NEXUS_PAYMENT_PROOF) maps to the documented X-Payment-Proof/Authorization header and is coherent with a paid service.
Instruction Scope
Instructions tell the agent to POST input to https://ai-service-hub-15.emergent.host and to include payment headers/credentials. They do not instruct reading unrelated files or system paths. Note: the skill asks users to POST signed Stellar XDRs to a sponsorship endpoint — this requires caution but does not itself ask the agent to access private keys (it expects a pre-signed XDR).
Install Mechanism
Instruction-only; no install spec and no code is written to disk. This minimizes installation risk.
Credentials
Only a single env var (NEXUS_PAYMENT_PROOF) is required, which is proportionate for a paywalled API. However the variable is a secret-like artifact: if it represents a live payment credential, exposing it to the agent (or storing it in shared environment) could enable charges. The SKILL.md shows it being sent verbatim in request headers.
Persistence & Privilege
always is false and the skill has no install/persistence behavior. It does request network access in its instructions (expected for an external API). Autonomous invocation is allowed by default on the platform — not a problem here but note it could trigger network calls that consume the provided payment proof.
Assessment
This skill is coherent: it simply wraps a paywalled translation API and requires a payment-proof value (NEXUS_PAYMENT_PROOF) which it sends to https://ai-service-hub-15.emergent.host. Before installing: 1) Verify and trust the external host (ai-service-hub-15.emergent.host) and the platform’s docs; there is no homepage provided in the package, so confirm the service independently. 2) Treat NEXUS_PAYMENT_PROOF as sensitive — use a sandbox/test token (the docs mention sandbox_test) for evaluation and avoid placing real payment credentials in shared agent env. 3) Consider the data you will send: all input is transmitted to the external service over HTTPS, so avoid sending PII or secrets. 4) If you will use the Stellar sponsorship flow, only POST signed XDRs you created with your own wallet; do not expose private keys to the agent. 5) Monitor usage and billing (price noted: $0.12/request) and restrict agent triggers if you are concerned about automated/unsupervised invocations consuming credits. 6) The README tags include unrelated terms (e.g., health-monitoring) — likely harmless but worth noting as sloppy metadata. If you need stronger assurance, ask the publisher for verifiable documentation or a canonical homepage and test with sandbox_test before providing any real payment proof.

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

Runtime requirements

Clawdis
EnvNEXUS_PAYMENT_PROOF
Primary envNEXUS_PAYMENT_PROOF
aivk97ebmwyjpbm0ha6v68a442c5984gqjacardanovk97ebmwyjpbm0ha6v68a442c5984gqjalatestvk97ebmwyjpbm0ha6v68a442c5984gqjastellarvk97ebmwyjpbm0ha6v68a442c5984gqjax402vk97ebmwyjpbm0ha6v68a442c5984gqja
345downloads
0stars
2versions
Updated 2w ago
v1.1.0
MIT-0

AI Translation Service

NEXUS Agent-as-a-Service on Cardano + Stellar | Price: $0.12/request | Accepts: ADA, DJED, iUSD, USDCx, USDM (Cardano) + USDC, XLM (Stellar)

When to use

Use when you need to translate text between languages.

Steps

Option A: x402 Standard (Recommended)

  1. Call the service endpoint without payment headers.
  2. Receive HTTP 402 with WWW-Authenticate: Payment header AND x402 accepts[] array in response body.
  3. Select a paymentRequirement from accepts[] matching your preferred network + asset.
  4. Networks: cardano:mainnet (ADA, DJED, iUSD, USDCx, USDM), stellar:pubnet (USDC, XLM), sandbox (free).
  5. Send payment to the payTo address for maxAmountRequired in the specified asset.
  6. Stellar fee sponsorship: POST your signed XDR to https://ai-service-hub-15.emergent.host/api/mpp/stellar/sponsor — NEXUS pays gas, you need 0 XLM.
  7. Retry with X-PAYMENT: <base64url JSON {x402Version:1, scheme:"exact", network, payload:{tx_hash, currency}}> header.
  8. Parse the JSON response and X-PAYMENT-RESPONSE header.

Option B: MPP Standard

  1. Call the service endpoint without payment headers.
  2. Receive HTTP 402 with WWW-Authenticate: Payment header listing all accepted currencies and amounts.
  3. Pick your preferred chain + currency: Cardano (ADA, stablecoins) or Stellar (USDC, XLM).
  4. Create payment: Masumi escrow (Cardano) or direct Stellar transfer.
  5. Stellar fee sponsorship: POST your signed XDR to https://ai-service-hub-15.emergent.host/api/mpp/stellar/sponsor — NEXUS pays gas, you need 0 XLM.
  6. Retry with Authorization: Payment <base64url-credential> header.
  7. Parse the JSON response and Payment-Receipt header.

Option C: Legacy Header

  1. Send a POST request to the NEXUS API endpoint with your input.
  2. Include the X-Payment-Proof header (Masumi payment ID or sandbox_test for testing).
  3. Parse the JSON response and return the result.

API Call

curl -X POST https://ai-service-hub-15.emergent.host/api/original-services/translate \
  -H "Content-Type: application/json" \
  -H "X-Payment-Proof: $NEXUS_PAYMENT_PROOF" \
  -d '{"text": "Hello, how are you?", "target_language": "ja"}'

Endpoint: https://ai-service-hub-15.emergent.host/api/original-services/translate Method: POST Headers:

  • Content-Type: application/json
  • X-PAYMENT: <base64url JSON> (x402 standard — recommended)
  • Authorization: Payment <credential> (MPP standard)
  • X-Payment-Proof: <masumi_payment_id> (legacy — use sandbox_test for free testing)

Accepted Currencies: ADA, DJED, iUSD, USDCx, USDM (Cardano) | USDC, XLM (Stellar) x402 Discovery: GET https://ai-service-hub-15.emergent.host/api/mpp/x402 (all services in native x402 format) MPP Discovery: GET https://ai-service-hub-15.emergent.host/api/mpp/discover Stablecoin Registry: GET https://ai-service-hub-15.emergent.host/api/mpp/stablecoins (includes on-chain policy IDs) Stellar Info: GET https://ai-service-hub-15.emergent.host/api/mpp/stellar (assets, recipient, fee sponsorship) Fee Sponsorship: POST https://ai-service-hub-15.emergent.host/api/mpp/stellar/sponsor (NEXUS pays Stellar gas — agents need 0 XLM)

External Endpoints

URLMethodData Sent
https://ai-service-hub-15.emergent.host/api/original-services/translatePOSTInput parameters as JSON body

Security & Privacy

  • All data is sent to https://ai-service-hub-15.emergent.host over HTTPS/TLS.
  • No data is stored permanently; requests are processed and discarded.
  • Payment proofs are verified on the Cardano blockchain via the Masumi Protocol.
  • No filesystem access or shell execution required.

Model Invocation Note

This skill calls the NEXUS AI service API which uses LLM models (GPT-5.2, Claude Sonnet 4.5, GPT-4o) to process requests. The AI processes your input server-side and returns a structured response. You may opt out by not installing this skill.

Trust Statement

By using this skill, your input data is sent to NEXUS (https://ai-service-hub-15.emergent.host) for AI processing. Payments are non-custodial via the Masumi Protocol on Cardano. Only install if you trust NEXUS as a service provider. Visit https://ai-service-hub-15.emergent.host for full documentation.

Tags

machine-learning, artificial-intelligence, free-trial, agent-to-agent, health-monitoring, budget

Comments

Loading comments...