NEXUS Orchestrator

Chain multiple AI services into automated workflows - describe a goal and the orchestrator plans, executes, and summarizes

Security Scan

The skill's requirements (a single payment proof credential) and runtime instructions align with its stated purpose (a paid orchestrator API); no code, installs, or unrelated credentials are requested, but you should verify the remote service before sending payment proofs or signed transactions.

Purpose & Capability

The skill is an instruction-only wrapper for a paid remote orchestrator service. The declared primary env var (NEXUS_PAYMENT_PROOF) and the documented payment flows (x402 / MPP / X-Payment-Proof) are consistent with a paid API gateway/orchestrator. No unrelated binaries, credentials, or config paths are requested.

Instruction Scope

The SKILL.md instructs the agent to send requests and payment proofs to https://ai-service-hub-15.emergent.host and, for Stellar fee sponsorship, to POST signed XDRs to a sponsor endpoint. The document does not ask for filesystem or shell access (permissions state network:true, filesystem:false, shell:false), but it does direct transmission of sensitive payment artifacts (payment proofs, signed transaction envelopes). This is expected for a paid API, but it is a privacy/payment risk if you are not prepared to share those artifacts with the service.

Install Mechanism

Instruction-only skill with no install spec and no code files. Nothing is written to disk or downloaded by the skill itself, which minimizes installation risk.

Credentials

Only one required env var (NEXUS_PAYMENT_PROOF) is declared and used; this is proportionate given the documented payment-based API. No other credentials or secret environment variables are requested. Note: setting this env var exposes a payment credential to calls that the skill (or agent) will make to the remote service.

Persistence & Privilege

always is false and the skill does not request elevated or persistent system presence. It does not modify other skills or system configs and declares no filesystem/shell access.

Assessment

This skill appears internally consistent for calling a paid remote orchestrator, but take these precautions before installing or enabling it: - Verify the service/operator: the SKILL.md points to ai-service-hub-15.emergent.host but there is no homepage or source repo in the registry metadata. Confirm the provider's reputation, terms, and privacy policy before sending payments. - Payment credentials: NEXUS_PAYMENT_PROOF is a payment artifact — do not set this env var with real funds or your primary payment account until you trust the service. Use sandbox_test for trial calls. - Signed transactions: the docs instruct you to POST signed Stellar XDRs to a sponsor endpoint. Never share private keys; only send XDR envelopes you have signed intentionally from a wallet you control. Prefer using a dedicated/test account for sponsorship flows. - Minimize data sent: inputs are transmitted to the remote service. Avoid including sensitive PII, secrets, or proprietary code in requests unless you accept that they will be processed by the provider. - Ask for provenance: request a homepage, source repository, contact, and documented refund/cancellation policy from the author before using the paid features. If you want higher assurance, ask the publisher for source code or an official service page and test with the sandbox flow first.

Orchestrator Agent

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

When to use

Use when you need to chain multiple AI services into a multi-step workflow. Describe your goal and the orchestrator plans and executes the steps.

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/orchestrator \
  -H "Content-Type: application/json" \
  -H "X-Payment-Proof: $NEXUS_PAYMENT_PROOF" \
  -d '{"goal": "Research AI safety, summarize findings, translate to Spanish", "max_steps": 5}'

Endpoint: https://ai-service-hub-15.emergent.host/api/original-services/orchestrator 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

URL	Method	Data Sent
https://ai-service-hub-15.emergent.host/api/original-services/orchestrator	POST	Input 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