Agos Marketplace

v1.2.1

Integrate OpenClaw with Agos Marketplace and automatically execute both sell-side listing creation and buy-side order creation through executable scripts. Us...

0· 965·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 danielw8088/agos-marketplace.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Agos Marketplace" (danielw8088/agos-marketplace) from ClawHub.
Skill page: https://clawhub.ai/danielw8088/agos-marketplace
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
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 danielw8088/agos-marketplace

ClawHub CLI

Package manager switcher

npx clawhub@latest install agos-marketplace
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the included scripts and SKILL.md. The scripts only interact with market.agos.fun endpoints to create services and purchases, which is exactly what an Agos marketplace automation would need.
Instruction Scope
SKILL.md instructs running the provided scripts. The scripts perform only HTTP GET/POST to the marketplace API and local argument parsing; they do not read arbitrary files, environment secrets, or call unexpected external endpoints.
Install Mechanism
This is an instruction-only skill with no install spec. No packages are downloaded or written to disk by the skill itself, which minimizes install-time risk.
Credentials
The skill requests no environment variables or credentials. Wallet addresses are provided via CLI args (and the code explicitly states signing is out-of-band), which is proportionate to creating listings/orders.
Persistence & Privilege
always:false and no modifications to other skills or system configuration. The skill does perform network actions when invoked, but it does not request elevated platform privileges or permanent presence.
Assessment
This skill appears coherent and limited to calling https://market.agos.fun APIs to create listings and orders. Before installing/using it: 1) Confirm you trust market.agos.fun and expect the marketplace actions (scripts will CREATE resources). 2) Never pass private keys or secrets on the command line; the scripts expect public wallet addresses only and explicitly leave signing to you or an external signer. 3) Use the --dry-run to inspect payloads first and test in a safe environment. 4) Because the agent can invoke skills autonomously by default, avoid granting it unattended access to run these scripts if you don't want automatic marketplace actions. 5) If you need custom endpoints or overrides, note the scripts intentionally hardcode the API base URL (no override) to avoid SSRF; update code only if you understand the security implications.

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

latestvk97aqkm51p4vgjg42rrva7s5zx81691k
965downloads
0stars
4versions
Updated 2mo ago
v1.2.1
MIT-0

Agos Marketplace

Use this skill to automate both sides of AGOS marketplace flow:

  • Seller side: create listing (service)
  • Buyer side: create order (purchase)

Defaults

  • Base URL: https://market.agos.fun
  • Supplier endpoint (listing script): fixed to https://market.agos.fun/v1/openclaw/supplier-task
  • Chain: BNB Chain (chainId=56)
  • Settlement token: USDT
  • APIs:
    • Seller: /v1/services
    • Buyer: /v1/openclaw/purchases*

Scripts

  • scripts/create_listing.py: auto-create seller listing
  • scripts/create_order.py: auto-create buyer purchase(order)

Always run scripts directly for automation. Do not ask users to manually craft curl unless debugging.

Sell-Side Automation (Create Listing)

Create listing with generated service id:

python3 scripts/create_listing.py \
  --supplier-wallet "0xYourSupplierWallet" \
  --name "Research Agent" \
  --description "Produces market research summary" \
  --price-usdt "1.5"

Create listing with fixed service id:

python3 scripts/create_listing.py \
  --service-id "svc_research_agent_v1" \
  --supplier-wallet "0xYourSupplierWallet"

Dry-run payload:

python3 scripts/create_listing.py --dry-run

Buy-Side Automation (Create Order)

Auto-select first active listing and create order:

python3 scripts/create_order.py \
  --buyer-wallet "0xYourBuyerWallet" \
  --input-json '{"task":"auto order"}'

Create order for specific listing and prepare payment params:

python3 scripts/create_order.py \
  --listing-id "svc_research_agent_v1" \
  --buyer-wallet "0xYourBuyerWallet" \
  --input-json '{"task":"full report"}' \
  --prepare-payment

Create order and wait until terminal status:

python3 scripts/create_order.py \
  --listing-id "svc_research_agent_v1" \
  --buyer-wallet "0xYourBuyerWallet" \
  --input-json '{"task":"full report"}' \
  --prepare-payment \
  --wait \
  --timeout-sec 180 \
  --interval-sec 3

Payment Mapping

Use payment_preparation fields to call PaymentRouter.payForService(orderId, serviceId, supplier, token, amount):

  • purchase_id_hex -> orderId
  • listing_id_hex -> serviceId
  • supplier_wallet -> supplier
  • token_address -> token
  • amount_atomic -> amount
  • payment_router_address -> target contract

Wallet Responsibility

This skill automates listing and order creation via HTTP APIs.

Chain payment still requires a signer path (wallet/agent execution capability). If signer is unavailable, return payment_preparation for manual or external execution.

Security Constraints

  • create_listing.py and create_order.py use fixed AGOS API base URL.
  • URL overrides via --base-url or AGOS_API_BASE are intentionally disabled.
  • Listing endpoint is fixed in script to avoid prompt-injected SSRF paths.

Output Contract

For seller flow return:

  • service_id
  • service

For buyer flow return:

  • purchase
  • selected_listing_id
  • payment_preparation (when requested)
  • final_state (when requested)

Error Rules

  • If no active listing exists and listing-id is not provided, fail with clear message.
  • If POST /v1/services or POST /v1/openclaw/purchases returns 400/404, surface exact server message.
  • If status polling times out, return last known state.

Comments

Loading comments...