NEXUS Document Extract

Extract structured data from text documents

Security Scan

The skill's requirements and runtime instructions are internally consistent: it forwards user input to the listed NEXUS API and legitimately needs a payment-proof credential for authorized requests, but you should still verify and trust the external service before sending sensitive data or secrets.

Purpose & Capability

Name/description ('Extract structured data from text documents') align with the instructions: the SKILL.md tells the agent to POST inputs to an external document-extract API. Requiring a payment proof credential (NEXUS_PAYMENT_PROOF) fits the payment-based API flow described.

Instruction Scope

Runtime instructions are narrowly scoped: they describe HTTP calls to a single external endpoint and payment flows (x402 / MPP / legacy header). The SKILL.md does not instruct reading arbitrary files, shell execution, or other environment variables beyond the declared payment credential.

Install Mechanism

No install spec or bundled code — instruction-only skill. This minimizes disk/write/execute risk; nothing will be downloaded or installed by the skill itself.

Credentials

Only one env var is required (NEXUS_PAYMENT_PROOF), which matches the declared primary credential and the API's payment/Authorization headers. This is proportionate to a paid remote API, but storing payment credentials as an environment variable is sensitive—treat it like a secret. Also note the skill will send whatever input you provide to a third-party service (possible sensitive data).

Persistence & Privilege

always is false and the skill does not request system persistence or special privileges. Autonomous invocation is allowed (platform default) but not combined here with any other concerning privileges.

Assessment

This skill is coherent: it simply forwards your input to a NEXUS API and requires a payment-proof credential to authorize requests. Before installing or using it: (1) Verify the external endpoint (https://ai-service-hub-15.emergent.host) and the provider's reputation and documentation; (2) Do not send highly sensitive or regulated data (PHI, PII, secrets) unless you trust the service and its privacy guarantees—tags include 'health-monitoring' which could imply sensitive data; (3) Protect the NEXUS_PAYMENT_PROOF env var as a secret (use a secure secret store), and prefer using the sandbox test value (sandbox_test) to validate functionality; (4) Confirm you accept the per-request charge ($0.30) and payment flows described; and (5) If you need stronger assurance, ask the publisher for a homepage, official documentation, or a verifiable publisher identity before proceeding.

Document Extractor

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

When to use

Use when you need to extract structured data from text documents.

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/document-extract \
  -H "Content-Type: application/json" \
  -H "X-Payment-Proof: $NEXUS_PAYMENT_PROOF" \
  -d '{
  "input": "Example input for Document Extractor"
}'

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