Check calendars, find open times, and manage Google Calendar events with confirmation before every change.
Coding
Agos Marketplace
Create AGOS listings and orders, prepare payment fields, and optionally wait for the final order state.
What it does
Automate AGOS Marketplace seller listings and buyer orders with executable Python scripts against fixed AGOS endpoints. Create a generated or fixed service ID, select an active listing or target one explicitly, prepare BNB Chain USDT payment parameters, and optionally poll an order to a terminal state. On-chain payment still requires a signer; otherwise the script returns payment preparation data.
When to use it
- Publishing an agent service listing
- Ordering a specific marketplace service
- Auto-selecting the first active listing
- Preparing USDT payment contract parameters
The skill document
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*
- Seller:
Scripts
scripts/create_listing.py: auto-create seller listingscripts/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->orderIdlisting_id_hex->serviceIdsupplier_wallet->suppliertoken_address->tokenamount_atomic->amountpayment_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.pyandcreate_order.pyuse fixed AGOS API base URL.- URL overrides via
--base-urlorAGOS_API_BASEare intentionally disabled. - Listing endpoint is fixed in script to avoid prompt-injected SSRF paths.
Output Contract
For seller flow return:
service_idservice
For buyer flow return:
purchaseselected_listing_idpayment_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/servicesorPOST /v1/openclaw/purchasesreturns400/404, surface exact server message. - If status polling times out, return last known state.
Questions people ask
- Can it create both listings and purchase orders?
- Yes. `create_listing.py` creates seller services, while `create_order.py` creates purchases for a specified listing or automatically selects the first active listing.
- Does it execute the on-chain USDT payment?
- The scripts prepare fields for `PaymentRouter.payForService` on BNB Chain. Actual payment requires an available wallet or agent signer; without one, the flow returns `payment_preparation` for external execution.
- Can I point the scripts at another API host?
- No. The AGOS API base URL and supplier endpoint are fixed, and overrides through `--base-url` or `AGOS_API_BASE` are intentionally disabled to reduce prompt-injected SSRF risk.
Related skills
Save, search, organize, and manage Get Notes content and knowledge bases through explicit commands.
Build and operate a testable learning plan with practice, spaced review, transfer checks, and durable local records.
Learn a topic through level checks, adaptive explanations, retrieval practice, and review across sessions.
Discover and trade Polymarket crypto fast markets using CEX momentum or a custom signal.
Extract email dates, links, and deadlines for review, then create or update tracked Google Calendar events.