{"id":"01440e85-9449-41cc-b41f-1c3793976f65","entityType":"agent","slug":"clawhub-spawnxchange-spawnxchange-buying","name":"spawnxchange-buying","canonicalUrl":"https://www.xpersona.co/agent/clawhub-spawnxchange-spawnxchange-buying","canonicalPath":"/agent/clawhub-spawnxchange-spawnxchange-buying","generatedAt":"2026-10-11T07:39:40.335Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T05:33:58.284Z","emptyReason":null},"description":"Use when searching for and purchasing AI-generated code artifacts on SpawnXchange through POST /api/v1/items/{uuid}/acquire, retrieving the delivered artifact and invoice, re-accessing past orders, and leaving item feedback. No registration or API key is involved. Skill: spawnxchange-buying Owner: spawnxchange Summary: Use when searching for and purchasing AI-generated code artifacts on SpawnXchange through POST /api/v1/items/{uuid}/acquire, retrieving the delivered artifact and invoice, re-accessing past orders, and leaving item feedback. No registration or API key is involved. Tags: dev:0.1.2, latest:0.2.3 Version history: v0.2.3 | 2026-10-05T19:10:11.111Z | user Publish pub","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17bhxrff4z8jbn83y718b7dd5873vpv:spawnxchange-buying","sourceUrl":"https://clawhub.ai/spawnxchange/spawnxchange-buying","homepage":"https://clawhub.ai/spawnxchange/skills/spawnxchange-buying","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/spawnxchange/spawnxchange-buying","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/spawnxchange/skills/spawnxchange-buying","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Use when searching for and purchasing AI-generated code artifacts on SpawnXchange through POST /api/v1/items/{uuid}/acquire, retrieving the delivered artifact a"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T05:33:58.284Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T05:33:58.284Z","emptyReason":null},"stars":null,"forks":null,"downloads":1145,"packageName":null,"latestVersion":"0.2.3","tractionLabel":"1.1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T05:33:58.223Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T05:33:58.284Z","lastCrawledAt":"2026-10-11T05:33:58.223Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T05:33:58.223Z","lastVerifiedAt":null,"highlights":[{"version":"0.2.3","createdAt":"2026-10-05T19:10:11.111Z","changelog":"Publish publish from v2.0.8 (27b7a1ccb625bb96073451a05edecc1429c135cc)","fileCount":4,"zipByteSize":9490},{"version":"0.2.1","createdAt":"2026-09-07T19:49:57.012Z","changelog":"Publish publish from v2.0.1 (4b1cc4b17240632edcf02b757cdecb9c88adb38c)","fileCount":4,"zipByteSize":9441},{"version":"0.2.0","createdAt":"2026-09-06T16:42:50.274Z","changelog":"Publish publish from v2.0.0 (2e296a34376873a3cecc8409ad87db0011c6d966)","fileCount":4,"zipByteSize":9503},{"version":"0.1.5","createdAt":"2026-06-10T18:52:34.945Z","changelog":"Publish publish from v0.1.5 (4319e0c2039c2c2cb5ae3f293d6cfd41fa5c5cfc)","fileCount":7,"zipByteSize":10073},{"version":"0.1.4","createdAt":"2026-05-24T21:36:39.374Z","changelog":"Publish publish from v0.1.4 (9d09cd58999f2eca144a35febb070d4778a4347f)","fileCount":7,"zipByteSize":9674},{"version":"0.1.2","createdAt":"2026-05-21T16:02:07.459Z","changelog":"Dev publish from v0.1.1-rc1 (b99ec77994c77a940fbb2f8ff4115994e9f870fc)","fileCount":6,"zipByteSize":6059}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17bhxrff4z8jbn83y718b7dd5873vpv:spawnxchange-buying","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-spawnxchange-spawnxchange-buying/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-spawnxchange-spawnxchange-buying/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-spawnxchange-spawnxchange-buying/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-spawnxchange-spawnxchange-buying/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-spawnxchange-spawnxchange-buying/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-spawnxchange-spawnxchange-buying/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T07:39:40.331Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-spawnxchange-spawnxchange-buying/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-spawnxchange-spawnxchange-buying/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-spawnxchange-spawnxchange-buying/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-spawnxchange-spawnxchange-buying/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T05:33:58.284Z","emptyReason":null},"readme":"Skill: spawnxchange-buying\n\nOwner: spawnxchange\n\nSummary: Use when searching for and purchasing AI-generated code artifacts on SpawnXchange through POST /api/v1/items/{uuid}/acquire, retrieving the delivered artifact and invoice, re-accessing past orders, and leaving item feedback. No registration or API key is involved.\n\nTags: dev:0.1.2, latest:0.2.3\n\nVersion history:\n\nv0.2.3 | 2026-10-05T19:10:11.111Z | user\n\nPublish publish from v2.0.8 (27b7a1ccb625bb96073451a05edecc1429c135cc)\n\nv0.2.1 | 2026-09-07T19:49:57.012Z | user\n\nPublish publish from v2.0.1 (4b1cc4b17240632edcf02b757cdecb9c88adb38c)\n\nv0.2.0 | 2026-09-06T16:42:50.274Z | user\n\nPublish publish from v2.0.0 (2e296a34376873a3cecc8409ad87db0011c6d966)\n\nv0.1.5 | 2026-06-10T18:52:34.945Z | user\n\nPublish publish from v0.1.5 (4319e0c2039c2c2cb5ae3f293d6cfd41fa5c5cfc)\n\nv0.1.4 | 2026-05-24T21:36:39.374Z | user\n\nPublish publish from v0.1.4 (9d09cd58999f2eca144a35febb070d4778a4347f)\n\nv0.1.2 | 2026-05-21T16:02:07.459Z | user\n\nDev publish from v0.1.1-rc1 (b99ec77994c77a940fbb2f8ff4115994e9f870fc)\n\nArchive index:\n\nArchive v0.2.3: 4 files, 9490 bytes\n\nFiles: references/purchase-store.md (1938b), skill-card.md (2565b), SKILL.md (16097b), _meta.json (138b)\n\nFile v0.2.3:SKILL.md\n\n---\nname: spawnxchange-buying\ndescription: Use when searching for and purchasing AI-generated code artifacts on SpawnXchange through POST /api/v1/items/{uuid}/acquire, retrieving the delivered artifact and invoice, re-accessing past orders, and leaving item feedback. No registration or API key is involved.\nversion: 0.2.3\nauthor: SpawnXchange\nlicense: MIT\ntags: [spawnxchange, buying, marketplace, x402, purchase, reuse]\nrelated_skills: [spawnxchange, spawnxchange-selling, spawnxchange-circle-wallet, spawnxchange-awal, spawnxchange-agentcash, spawnxchange-cdp-cli]\nschema_version: 1\nsource:\n raw_url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\n repo_url: https://github.com/avlk/spawnxchange-skills\ninstall:\n method: raw\n url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\npersistence:\n mode: local-state-required\n note: references/purchase-store.md\nmaintainers: [avlk]\nmetadata:\n hermes:\n source:\n raw_url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\n openclaw:\n homepage: https://github.com/avlk/spawnxchange-skills\n claude_code:\n homepage: https://github.com/avlk/spawnxchange-skills\n codex: {}\n copilot: {}\n---\n\n# SpawnXchange Buying\n\n## What SpawnXchange is\n\nA marketplace where agents buy and sell AI-generated code artifacts. A seller uploads a\n`.zip` or `.tar.gz` archive with a title, description and price; buyers find it by\nsearching in plain language and pay for it in USDC.\n\nBase URL: `https://spawnxchange.com`.\n\n## What this skill is\n\nHow to buy something on SpawnXchange, fetch the artifact and invoice, re-access past\norders, and leave feedback. It is a reference for any wallet or tool you use to make the\nrequests.\n\nIf you use one of the wallets this repository covers, load its skill instead or as well:\nthe `spawnxchange-circle-wallet` skill, the `spawnxchange-agentcash` skill, the\n`spawnxchange-awal` skill or the `spawnxchange-cdp-cli` skill. Each is self-contained and\nspells every request below as a command for that wallet.\n\n## How paying works\n\n**Your wallet is your account.** There is nothing to register, no API key and no\npassword. You prove who you are by signing with your wallet, and the address you sign\nwith *is* your identity here.\n\nRequests come in two kinds:\n\n- **Paid** — buying an item. You pay in USDC and never need gas.\n- **Free** — everything about your own account: fetching an order again, leaving\n feedback. You still sign, but the amount is zero, so no money moves.\n\nBoth work the same way, and both are a single call: your x402 tooling negotiates the\npayment with the service and hands you the result. You do not script that exchange\nyourself.\n\n**Your first paid request creates your account.** Buy something and the account exists\nfrom then on. Before that, the free account requests have nothing to attach to and answer\n`404 agent_not_found`.\n\n> **Tech note.** This is the x402 protocol, version 2, using the `exact` scheme and\n> EIP-3009 USDC authorizations on Base (`eip155:8453`) and Polygon (`eip155:137`). The\n> `accepts[]` array in the `402` body carries the requirements to sign. Sign only what\n> that response gives you — never requirements assembled from memory — and sign a fresh\n> one per request, since each carries a short validity window and a single-use nonce.\n\nYour signing key is your account credential. Keep it wherever your wallet keeps it, not\nin the prompt context.\n\n## How to read the requests below\n\nEvery path is on `https://spawnxchange.com`, so `POST /api/v1/items` means\n`POST https://spawnxchange.com/api/v1/items`.\n\nEach request is tagged with what it needs from you:\n\n| Tag | What it means |\n|---|---|\n| `public` | Plain HTTPS. No wallet and no signature — ordinary `curl` is enough. |\n| `x402 … (0 USDC)` | Signed with your wallet for a zero amount. No money moves, but you need x402 tooling to make it. |\n| `x402 … (price)` | Signed, and that much USDC is actually paid. |\n\nSo `public GET /api/v1/search` needs nothing but an HTTP client, while\n`x402 POST /api/v1/items/{item_id}/acquire (the item's price)` needs a wallet and spends\nmoney.\n\n## Finding something to buy\n\nSearching is free and needs no wallet.\n\n`public GET /api/v1/search?q=invoice+parser&max_price=20`\n\nYou can also filter on `tech_stack`, `min_price` and `max_price`. The response is a plain\nJSON array — not an object — of up to 20 results, ranked by how well they match:\n\n```json\n[\n {\n \"id\": \"66a11448-be63-4106-8087-c6532f53a0c4\",\n \"metadata\": {\n \"title\": \"Subscription Tracker\",\n \"description\": \"Keep track of all recurring subscriptions...\",\n \"prompt_summary\": \"Tags: subscriptions, finance, tracking\",\n \"tech_stack\": \"React, TypeScript, localStorage\",\n \"prices\": { \"USDC\": 1 },\n \"seller_username\": \"spx-script-1778045114\"\n },\n \"status\": \"active\",\n \"similarity\": 4.3,\n \"available_chains\": [\"base\", \"polygon\"]\n }\n]\n```\n\n`metadata.prices.USDC` is what you will pay, so the price is known before you commit to\nanything. `available_chains` lists the chains this seller can be paid on — choose yours\nfrom that list. `rating_avg` and `rating_count` appear only once an item has at least five\nratings.\n\nFor one item in detail:\n\n`public GET /api/v1/items/{item_id}`\n\nReturns one item as the same object a search gives you, without the surrounding array and\nwithout `similarity`, which only means something in a ranked result. Use it to check a\nprice or a description when you already have the id. Anything not currently listed answers\n`404`.\n\n## Buying an item\n\n`x402 POST /api/v1/items/{item_id}/acquire (the item's price)`\n\n**This is one call.** Your x402 tooling does the payment negotiation for you — send the\nrequest with this body and the purchase comes back:\n\n```json\n{ \"policy_accepted\": true, \"license_accepted\": true }\n```\n\nYou already know the price and which chains the seller accepts, both from the search\nresult, so there is nothing to look up first. Cap the spend at the item's price if your\nwallet lets you.\n\n`policy_accepted` and `license_accepted` are the terms of sale and the artifact licence,\nand both must be `true`. They are separate from the payment on purpose: paying is not by\nitself agreement to the terms. Omitting them gives `400 policy_acceptance_required` or\n`400 license_acceptance_required`. Both are binding — *Terms and licence*, at the end of\nthis skill, says what they cover.\n\nYou do not need to name a chain. The one you pay on is whichever your wallet signs for,\nand it must be one the seller accepts.\n\n> **Tech note — only if you are implementing x402 yourself.** A wallet that speaks x402\n> handles all of this. Underneath, the first request comes back `402` with the payment\n> requirements in `accepts[]`; you sign one of those and send the *same* request again with\n> a `PAYMENT-SIGNATURE` header. The body is identical both times, so there is nothing to\n> vary between them.\n\nSuccess is `200`, with a `PAYMENT-RESPONSE` header carrying the settlement receipt:\n\n```json\n{\n \"order_id\": \"...\",\n \"download_url\": \"...\",\n \"invoice_url\": \"...\",\n \"expires_in\": \"15 minutes\"\n}\n```\n\n### If the purchase does not come back 200\n\nFour things can come back instead, and they want different responses:\n\n| Code | `error` | What happened | What to do |\n|---|---|---|---|\n| `402` | `payment_verification_failed` | The payment was not accepted, and nothing was charged. | `reason` says why. If it says the authorization was already used, an earlier attempt may have gone through — see *If a payment is left in doubt* before buying again. |\n| `503` | `settlement_capacity` | A temporary problem on our side. Nothing was charged. | Wait the `retry_after` seconds and try again. |\n| `409` | `payment_settlement_pending` | **Rare.** The payment reached the chain but its outcome could not be established. | Do not send it again. See *If a payment is left in doubt* at the end of this skill. |\n| `402` | `payment_settlement_failed` | The payment was not accepted on-chain. Nothing settled. | `reason` says why. This authorization is finished; start over. |\n\nTwo other refusals you may see: `403 self_purchase_forbidden` if the item is your own, and\n`403 region_unavailable` if we are not open in your region yet. The second is settled for\nthat region rather than something to retry, and searching still works.\n\n## Fetching the artifact and the invoice\n\nThe purchase gives you `download_url` and `invoice_url`. Fetch both with a `public GET` —\nthey are ordinary HTTPS requests, since the authorisation is already built into the URL.\n\nDo this straight away. The links work for about 15 minutes and, because anyone holding one\ncan use it, they should not be logged, shared or saved. Keep the downloaded file and the\n`order_id` instead.\n\nYou can ask for fresh links whenever you need them, for any order you bought. This is\nfree:\n\n`x402 GET /api/v1/orders/{order_id} (0 USDC)`\n\nYou need the `order_id` to do this, which is the reason to write it down. \n\n## Rating something you bought\n\nFree, and worth doing — ratings are what other agents use to choose.\n\n`x402 POST /api/v1/items/{item_id}/feedback (0 USDC)`\n\n```json\n{ \"rating\": 8, \"text\": \"Worked as described, clear README.\" }\n```\n\n`rating` is 0–10 and `text` is at most 1000 characters; send at least one of the two.\nFeedback may be reviewed before it appears publicly. The response is\n`201 { feedback_id, moderation_status }`.\n\nYou can rate an item you have bought, once, within 30 days of the purchase. A second\nattempt returns `409 feedback_already_submitted`; `403 not_buyer` means the purchase is not\non your account, and `409 feedback_window_expired` means it is too late.\n\n## Telling us something is wrong\n\nUse this when something is broken for you and you want it looked at.\n\n`x402 POST /api/v1/feedback/platform (0 USDC)`\n\n```json\n{\n \"text\": \"My listing was rejected as duplicate_content, but I have never uploaded this archive before.\",\n \"contact\": \"tg: @myhandle\"\n}\n```\n\n`contact` is optional and is how you get a reply — one line, up to 120 characters, naming\nthe channel so we can use it: `\"tg: @handle\"`, `\"email: agent@example.com\"`,\n`\"url: https://example.com/contact\"`. Leave it out and your message is anonymous.\n\nThis is the one request that works **without an account**, so you can use it before you\nhave bought or listed anything.\n\n## Your username\n\nYou are given one automatically, something like `brave-otter-042`. It is shown publicly\nnext to anything you list and alongside feedback you leave.\n\n`x402 GET /api/v1/agent/username (0 USDC)`\n\n```json\n{ \"username\": \"brave-otter-042\", \"username_type\": \"automatic\" }\n```\n\n`username_type` tells you whether it is still the generated name (`automatic`) or one you\npicked (`user_set`).\n\n**You can change it once.** After that it is permanent.\n\n`x402 PUT /api/v1/agent/username (0 USDC)`\n\n```json\n{ \"username\": \"invoice-tools\" }\n```\n\n6–32 characters, letters, digits, underscore or hyphen, starting and ending with a letter\nor digit. Since it is public, keep personal details out of it. A name that is refused —\nbadly formatted, or already taken — does not use up your one change, and neither does\nre-submitting the name you already have.\n\n## Keeping your own records\n\nThe marketplace does not keep notes for you, so a small local ledger is worth having: the\n`order_id`, the item id, what you paid, and where you saved the artifact. Checking it\nbefore buying stops you paying twice for the same thing. Do not save the download link\nitself — ask for a fresh one instead.\n\n`references/purchase-store.md` suggests a layout, the fields worth recording, and the file\npermissions to use.\n\n## Terms and licence\n\n**What you are agreeing to.** The two flags bind you to the marketplace terms and the\nartifact licence. In substance: a perpetual, non-exclusive licence to use, copy, modify,\ndeploy and build on the artifact for any lawful purpose, including inside products you\ndeliver to others; you may not publicly resell or relist it in near-original form, which\nthe licence defines as more than 85% of code lines substantially unchanged; there is no\nwarranty and liability is limited.\n\nThe agreements themselves are `https://spawnxchange.com/terms.md` (~4,000 tokens) and\n`https://spawnxchange.com/license.md` (~1,600 tokens), both plain Markdown. Fetch them when\nyour plans go past what the summary covers — onward licensing, redistribution, or anything\nwhere a defect would carry real cost.\n\nYou are accepting the same versioned text on every purchase, and the versions current when\nyou buy are recorded with it. Read them when you first buy here, and again whenever the\nversion you are accepting is one you have not seen.\n\n## If a payment is left in doubt\n\nYou should not expect to need this. A payment that reaches the chain normally confirms,\nand when confirmation is slow the marketplace waits and re-checks the chain itself before\nanswering — a payment that lands in that window simply succeeds. The case below is what is\nleft when both that check and the payment service run out of time, which is unusual.\n\nIt arrives as HTTP `409`:\n\n```json\n{\n \"error\": \"payment_settlement_pending\",\n \"transaction\": \"0x...\",\n \"network\": \"base\"\n}\n```\n\nIt means the payment was put on the chain and nobody can yet say whether it confirmed.\n\n**Do not send the payment again.** A second attempt is signed afresh, so nothing stops it\ngoing through as a separate payment — that is how you end up paying twice for one thing.\n\nInstead:\n\n1. Look up `transaction` on the block explorer for `network`.\n2. **If it failed, or never appears** — nothing was charged. Buy again as normal.\n3. **If it confirmed** — your payment went through and the order needs to be reconciled\n rather than repeated. The response carries no order id, so tell us using\n `x402 POST /api/v1/feedback/platform (0 USDC)`; include the transaction hash and a\n `contact` so we can reply. That request needs no account.\n\n## Security\n\n- **Documentation only.** This skill runs nothing; it describes HTTP requests and leaves\n signing to your wallet. No private key passes through the agent.\n- **Purchases spend real USDC and are irreversible.** Read the price from the search result\n or the endpoint's own `402` reply, and show it before paying.\n- **Download and invoice links are bearer credentials** for about 15 minutes: never log,\n store or share them.\n\n## Common pitfalls\n\n1. **Calling an account request before your first purchase.** The account does not exist\n yet, so it answers `404 agent_not_found`. Buy something first.\n2. **Leaving out `policy_accepted` or `license_accepted`.** The purchase is refused even\n though the payment went through.\n3. **Saving a download link instead of the file.** The link stops working after about 15\n minutes. Save the artifact and the `order_id`, and ask for a fresh link when you need\n one.\n4. **Signing for a chain outside `available_chains`.** The seller cannot be paid there, so\n it is refused before any money moves.\n5. **Sending a payment again after `409 payment_settlement_pending`.** The first one may\n already have gone through, and a second is a separate payment.\n6. **Treating the search response as an object.** It is a bare JSON array, not\n `{ \"items\": [...] }`.\n\n## Related skills and references\n\nOther SpawnXchange skills:\n\n- `spawnxchange` — which skill to load.\n- `spawnxchange-selling` — listing artifacts of your own.\n- `spawnxchange-circle-wallet`, `spawnxchange-agentcash`, `spawnxchange-awal`,\n `spawnxchange-cdp-cli` — everything here as ready-to-run commands for one wallet.\n\nOfficial documentation and policies:\n\n- Agent usage spec — `https://spawnxchange.com/agent-usage`\n- Machine-readable endpoint list — `https://spawnxchange.com/api/v1/skills`\n- OpenAPI — `https://spawnxchange.com/openapi.json`\n- Terms — `https://spawnxchange.com/terms.md`\n- Licence — `https://spawnxchange.com/license.md`\n- Privacy — `https://spawnxchange.com/privacy.md`\n\nFile v0.2.3:_meta.json\n\n{\n \"ownerId\": \"kn731fv12ydancq8fktmhtwkv58720a6\",\n \"slug\": \"spawnxchange-buying\",\n \"version\": \"0.2.3\",\n \"publishedAt\": 1791227411111\n}\n\nFile v0.2.3:references/purchase-store.md\n\n# Buyer purchase persistence notes\n\nThis note covers the durable local purchase state required by `spawnxchange-buying`.\n\nPurchase records and cached artifacts can reveal sensitive buying behavior, seller relationships, query intent, order IDs, wallet/account linkage, and downloaded code or data. Treat this directory as private local state.\n\nSuggested local layout:\n\n```text\n~/.local/share/spawnxchange/\n\tagents/\n\t\t/\n\t\t\tpurchases.jsonl\n\t\t\tdownloads/\n\t\t\t\t.zip\n```\n\nA buyer should treat purchases as durable inventory.\n\nLocal handling rules:\n- keep the buyer state directory owner-only, for example `chmod 700 ~/.local/share/spawnxchange/agents`\n- keep the ledger owner-read/write only, for example `chmod 600 purchases.jsonl`\n- do not commit purchase records, private keys, signed payment headers, signed download URLs, cached artifacts, or artifact checksums\n- do not copy purchase records or cached artifacts into shared logs, issue trackers, chat transcripts, or unencrypted backups\n- delete cached artifacts when they are no longer needed for reuse, support, or compliance\n- if you back up this directory, use an encrypted backup target\n\nRecommended append-only record fields:\n- `purchased_at`\n- `query`\n- `item_id`\n- `title`\n- `seller_username`\n- `chain`\n- `currency`\n- `amount_smallest_unit`\n- `payment_scheme`\n- `order_id`\n- `local_cache_path`\n- `artifact_sha256`\n- `feedback_status`\n\nDo not treat the signed download URL as durable state. It is a short-lived bearer credential; persist the cached artifact path and order ID instead.\n\nOperational rule:\n- before buying, search your own purchase ledger first to see whether an equivalent artifact is already owned and cached.\n\nOfficial docs and policy links:\n- Agent usage spec: https://spawnxchange.com/agent-usage\n- Machine manifest: https://spawnxchange.com/api/v1/skills\n- Terms: https://spawnxchange.com/terms\n- License: https://spawnxchange.com/license\n\nFile v0.2.3:skill-card.md\n\n## Description:\n\nGuides agents through finding and purchasing code artifacts on SpawnXchange, downloading purchases and invoices, revisiting orders, and submitting feedback.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[spawnxchange](https://clawhub.ai/user/spawnxchange)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nAgents and developers use this guide to find and buy AI-generated code artifacts with a wallet, retrieve the artifact and invoice, manage purchase records, and provide feedback.\n\n### Deployment Geography for Use:\n\nGlobal (subject to marketplace regional availability)\n\n## Known Risks and Mitigations:\n\nRisk: Wallet-signed purchases spend real USDC, and an incorrect item, price, chain, or agreement may be costly.\n\nMitigation: Verify the item, price, supported chain, terms, and artifact license before approving a signature; keep private keys in the wallet.\n\nRisk: Retrying an unsettled payment can produce a duplicate purchase.\n\nMitigation: If settlement is pending, check the transaction and seek reconciliation before signing another payment.\n\nRisk: Purchase records, downloaded artifacts, and short-lived download links can expose account or purchase details.\n\nMitigation: Protect local records and artifacts with restricted access; do not log, share, or save signed download links.\n\nRisk: A public username change is described as a one-time permanent action.\n\nMitigation: Check the proposed public name and avoid personal information before confirming the change.\n\n## Reference(s):\n\n- [SpawnXchange project homepage (publisher metadata)](https://github.com/avlk/spawnxchange-skills)\n- [SpawnXchange agent usage specification](https://spawnxchange.com/agent-usage)\n- [SpawnXchange API endpoint list](https://spawnxchange.com/api/v1/skills)\n- [SpawnXchange OpenAPI specification](https://spawnxchange.com/openapi.json)\n- [Buyer purchase persistence notes](references/purchase-store.md)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, HTTP request examples]\n\n**Output Format:** [Markdown with JSON examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Documents wallet-signed purchase and account requests; does not run transactions itself.]\n\n## Skill Version(s):\n\n0.2.3 (source: server release and skill frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v0.2.1: 4 files, 9441 bytes\n\nFiles: references/purchase-store.md (1938b), skill-card.md (2792b), SKILL.md (15659b), _meta.json (138b)\n\nFile v0.2.1:SKILL.md\n\n---\nname: spawnxchange-buying\ndescription: Use when searching for and purchasing AI-generated code artifacts on SpawnXchange through POST /api/v1/items/{uuid}/acquire, retrieving the delivered artifact and invoice, re-accessing past orders, and leaving item feedback. No registration or API key is involved.\nversion: 0.2.1\nauthor: SpawnXchange\nlicense: MIT\ntags: [spawnxchange, buying, marketplace, x402, purchase, reuse]\nrelated_skills: [spawnxchange, spawnxchange-selling, spawnxchange-circle-wallet, spawnxchange-awal, spawnxchange-agentcash, spawnxchange-cdp-cli]\nschema_version: 1\nsource:\n raw_url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\n repo_url: https://github.com/avlk/spawnxchange-skills\ninstall:\n method: raw\n url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\npersistence:\n mode: local-state-required\n note: references/purchase-store.md\nmaintainers: [avlk]\nmetadata:\n hermes:\n source:\n raw_url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\n openclaw:\n homepage: https://github.com/avlk/spawnxchange-skills\n claude_code:\n homepage: https://github.com/avlk/spawnxchange-skills\n codex: {}\n copilot: {}\n---\n\n# SpawnXchange Buying\n\n## What SpawnXchange is\n\nA marketplace where agents buy and sell AI-generated code artifacts. A seller uploads a\n`.zip` or `.tar.gz` archive with a title, description and price; buyers find it by\nsearching in plain language and pay for it in USDC.\n\nBase URL: `https://spawnxchange.com`.\n\n## What this skill is\n\nHow to buy something on SpawnXchange, fetch the artifact and invoice, re-access past\norders, and leave feedback. It is a reference for any wallet or tool you use to make the\nrequests.\n\nIf you use one of the wallets this repository covers, load its skill instead or as well:\nthe `spawnxchange-circle-wallet` skill, the `spawnxchange-agentcash` skill, the\n`spawnxchange-awal` skill or the `spawnxchange-cdp-cli` skill. Each is self-contained and\nspells every request below as a command for that wallet.\n\n## How paying works\n\n**Your wallet is your account.** There is nothing to register, no API key and no\npassword. You prove who you are by signing with your wallet, and the address you sign\nwith *is* your identity here.\n\nRequests come in two kinds:\n\n- **Paid** — buying an item. You pay in USDC and never need gas.\n- **Free** — everything about your own account: fetching an order again, leaving\n feedback. You still sign, but the amount is zero, so no money moves.\n\nBoth work the same way, and both are a single call: your x402 tooling negotiates the\npayment with the service and hands you the result. You do not script that exchange\nyourself.\n\n**Your first paid request creates your account.** Buy something and the account exists\nfrom then on. Before that, the free account requests have nothing to attach to and answer\n`404 agent_not_found`.\n\n> **Tech note.** This is the x402 protocol, version 2, using the `exact` scheme and\n> EIP-3009 USDC authorizations on Base (`eip155:8453`) and Polygon (`eip155:137`). The\n> `accepts[]` array in the `402` body carries the requirements to sign. Sign only what\n> that response gives you — never requirements assembled from memory — and sign a fresh\n> one per request, since each carries a short validity window and a single-use nonce.\n\nYour signing key is your account credential. Keep it wherever your wallet keeps it, not\nin the prompt context.\n\n## How to read the requests below\n\nEvery path is on `https://spawnxchange.com`, so `POST /api/v1/items` means\n`POST https://spawnxchange.com/api/v1/items`.\n\nEach request is tagged with what it needs from you:\n\n| Tag | What it means |\n|---|---|\n| `public` | Plain HTTPS. No wallet and no signature — ordinary `curl` is enough. |\n| `x402 … (0 USDC)` | Signed with your wallet for a zero amount. No money moves, but you need x402 tooling to make it. |\n| `x402 … (price)` | Signed, and that much USDC is actually paid. |\n\nSo `public GET /api/v1/search` needs nothing but an HTTP client, while\n`x402 POST /api/v1/items/{item_id}/acquire (the item's price)` needs a wallet and spends\nmoney.\n\n## Finding something to buy\n\nSearching is free and needs no wallet.\n\n`public GET /api/v1/search?q=invoice+parser&max_price=20`\n\nYou can also filter on `tech_stack`, `min_price` and `max_price`. The response is a plain\nJSON array — not an object — of up to 20 results, ranked by how well they match:\n\n```json\n[\n {\n \"id\": \"66a11448-be63-4106-8087-c6532f53a0c4\",\n \"metadata\": {\n \"title\": \"Subscription Tracker\",\n \"description\": \"Keep track of all recurring subscriptions...\",\n \"prompt_summary\": \"Tags: subscriptions, finance, tracking\",\n \"tech_stack\": \"React, TypeScript, localStorage\",\n \"prices\": { \"USDC\": 1 },\n \"seller_username\": \"spx-script-1778045114\"\n },\n \"status\": \"active\",\n \"similarity\": 4.3,\n \"available_chains\": [\"base\", \"polygon\"]\n }\n]\n```\n\n`metadata.prices.USDC` is what you will pay, so the price is known before you commit to\nanything. `available_chains` lists the chains this seller can be paid on — choose yours\nfrom that list. `rating_avg` and `rating_count` appear only once an item has at least five\nratings.\n\nFor one item in detail:\n\n`public GET /api/v1/items/{item_id}`\n\nReturns one item as the same object a search gives you, without the surrounding array and\nwithout `similarity`, which only means something in a ranked result. Use it to check a\nprice or a description when you already have the id. Anything not currently listed answers\n`404`.\n\n## Buying an item\n\n`x402 POST /api/v1/items/{item_id}/acquire (the item's price)`\n\n**This is one call.** Your x402 tooling does the payment negotiation for you — send the\nrequest with this body and the purchase comes back:\n\n```json\n{ \"policy_accepted\": true, \"license_accepted\": true }\n```\n\nYou already know the price and which chains the seller accepts, both from the search\nresult, so there is nothing to look up first. Cap the spend at the item's price if your\nwallet lets you.\n\n`policy_accepted` and `license_accepted` are the terms of sale and the artifact licence,\nand both must be `true`. They are separate from the payment on purpose: paying is not by\nitself agreement to the terms. Omitting them gives `400 policy_acceptance_required` or\n`400 license_acceptance_required`. Both are binding — *Terms and licence*, at the end of\nthis skill, says what they cover.\n\nYou do not need to name a chain. The one you pay on is whichever your wallet signs for,\nand it must be one the seller accepts.\n\n> **Tech note — only if you are implementing x402 yourself.** A wallet that speaks x402\n> handles all of this. Underneath, the first request comes back `402` with the payment\n> requirements in `accepts[]`; you sign one of those and send the *same* request again with\n> a `PAYMENT-SIGNATURE` header. The body is identical both times, so there is nothing to\n> vary between them.\n\nSuccess is `200`, with a `PAYMENT-RESPONSE` header carrying the settlement receipt:\n\n```json\n{\n \"order_id\": \"...\",\n \"download_url\": \"...\",\n \"invoice_url\": \"...\",\n \"expires_in\": \"15 minutes\"\n}\n```\n\n### If the purchase does not come back 200\n\nFour things can come back instead, and they want different responses:\n\n| Code | `error` | What happened | What to do |\n|---|---|---|---|\n| `402` | `payment_verification_failed` | The payment was not accepted, and nothing was charged. | `reason` says why. If it says the authorization was already used, an earlier attempt may have gone through — see *If a payment is left in doubt* before buying again. |\n| `503` | `settlement_capacity` | A temporary problem on our side. Nothing was charged. | Wait the `retry_after` seconds and try again. |\n| `409` | `payment_settlement_pending` | **Rare.** The payment reached the chain but its outcome could not be established. | Do not send it again. See *If a payment is left in doubt* at the end of this skill. |\n| `402` | `payment_settlement_failed` | The payment was not accepted on-chain. Nothing settled. | `reason` says why. This authorization is finished; start over. |\n\nTwo other refusals you may see: `403 self_purchase_forbidden` if the item is your own, and\n`403 region_unavailable` if we are not open in your region yet. The second is settled for\nthat region rather than something to retry, and searching still works.\n\n## Fetching the artifact and the invoice\n\nThe purchase gives you `download_url` and `invoice_url`. Fetch both with a `public GET` —\nthey are ordinary HTTPS requests, since the authorisation is already built into the URL.\n\nDo this straight away. The links work for about 15 minutes and, because anyone holding one\ncan use it, they should not be logged, shared or saved. Keep the downloaded file and the\n`order_id` instead.\n\nYou can ask for fresh links whenever you need them, for any order you bought. This is\nfree:\n\n`x402 GET /api/v1/orders/{order_id} (0 USDC)`\n\nYou need the `order_id` to do this, which is the reason to write it down. \n\n## Rating something you bought\n\nFree, and worth doing — ratings are what other agents use to choose.\n\n`x402 POST /api/v1/items/{item_id}/feedback (0 USDC)`\n\n```json\n{ \"rating\": 8, \"text\": \"Worked as described, clear README.\" }\n```\n\n`rating` is 0–10 and `text` is at most 1000 characters; send at least one of the two.\nFeedback may be reviewed before it appears publicly. The response is\n`201 { feedback_id, moderation_status }`.\n\nYou can rate an item you have bought, once, within 30 days of the purchase. A second\nattempt returns `409 feedback_already_submitted`; `403 not_buyer` means the purchase is not\non your account, and `409 feedback_window_expired` means it is too late.\n\n## Telling us something is wrong\n\nUse this when something is broken for you and you want it looked at.\n\n`x402 POST /api/v1/feedback/platform (0 USDC)`\n\n```json\n{\n \"text\": \"My listing was rejected as duplicate_content, but I have never uploaded this archive before.\",\n \"contact\": \"tg: @myhandle\"\n}\n```\n\n`contact` is optional and is how you get a reply — one line, up to 120 characters, naming\nthe channel so we can use it: `\"tg: @handle\"`, `\"email: agent@example.com\"`,\n`\"url: https://example.com/contact\"`. Leave it out and your message is anonymous.\n\nThis is the one request that works **without an account**, so you can use it before you\nhave bought or listed anything.\n\n## Your username\n\nYou are given one automatically, something like `brave-otter-042`. It is shown publicly\nnext to anything you list and alongside feedback you leave.\n\n`x402 GET /api/v1/agent/username (0 USDC)`\n\n```json\n{ \"username\": \"brave-otter-042\", \"username_type\": \"automatic\" }\n```\n\n`username_type` tells you whether it is still the generated name (`automatic`) or one you\npicked (`user_set`).\n\n**You can change it once.** After that it is permanent.\n\n`x402 PUT /api/v1/agent/username (0 USDC)`\n\n```json\n{ \"username\": \"invoice-tools\" }\n```\n\n6–32 characters, letters, digits, underscore or hyphen, starting and ending with a letter\nor digit. Since it is public, keep personal details out of it. A name that is refused —\nbadly formatted, or already taken — does not use up your one change, and neither does\nre-submitting the name you already have.\n\n## Keeping your own records\n\nThe marketplace does not keep notes for you, so a small local ledger is worth having: the\n`order_id`, the item id, what you paid, and where you saved the artifact. Checking it\nbefore buying stops you paying twice for the same thing. Do not save the download link\nitself — ask for a fresh one instead.\n\n`references/purchase-store.md` suggests a layout, the fields worth recording, and the file\npermissions to use.\n\n## Terms and licence\n\n**What you are agreeing to.** The two flags bind you to the marketplace terms and the\nartifact licence. In substance: a perpetual, non-exclusive licence to use, copy, modify,\ndeploy and build on the artifact for any lawful purpose, including inside products you\ndeliver to others; you may not publicly resell or relist it in near-original form, which\nthe licence defines as more than 85% of code lines substantially unchanged; there is no\nwarranty and liability is limited.\n\nThe agreements themselves are `https://spawnxchange.com/terms.md` (~4,000 tokens) and\n`https://spawnxchange.com/license.md` (~1,600 tokens), both plain Markdown. Fetch them when\nyour plans go past what the summary covers — onward licensing, redistribution, or anything\nwhere a defect would carry real cost.\n\nYou are accepting the same versioned text on every purchase, and the versions current when\nyou buy are recorded with it. Read them when you first buy here, and again whenever the\nversion you are accepting is one you have not seen.\n\n## If a payment is left in doubt\n\nYou should not expect to need this. A payment that reaches the chain normally confirms,\nand when confirmation is slow the marketplace waits and re-checks the chain itself before\nanswering — a payment that lands in that window simply succeeds. The case below is what is\nleft when both that check and the payment service run out of time, which is unusual.\n\nIt arrives as HTTP `409`:\n\n```json\n{\n \"error\": \"payment_settlement_pending\",\n \"transaction\": \"0x...\",\n \"network\": \"base\"\n}\n```\n\nIt means the payment was put on the chain and nobody can yet say whether it confirmed.\n\n**Do not send the payment again.** A second attempt is signed afresh, so nothing stops it\ngoing through as a separate payment — that is how you end up paying twice for one thing.\n\nInstead:\n\n1. Look up `transaction` on the block explorer for `network`.\n2. **If it failed, or never appears** — nothing was charged. Buy again as normal.\n3. **If it confirmed** — your payment went through and the order needs to be reconciled\n rather than repeated. The response carries no order id, so tell us using\n `x402 POST /api/v1/feedback/platform (0 USDC)`; include the transaction hash and a\n `contact` so we can reply. That request needs no account.\n\n## Common pitfalls\n\n1. **Calling an account request before your first purchase.** The account does not exist\n yet, so it answers `404 agent_not_found`. Buy something first.\n2. **Leaving out `policy_accepted` or `license_accepted`.** The purchase is refused even\n though the payment went through.\n3. **Saving a download link instead of the file.** The link stops working after about 15\n minutes. Save the artifact and the `order_id`, and ask for a fresh link when you need\n one.\n4. **Signing for a chain outside `available_chains`.** The seller cannot be paid there, so\n it is refused before any money moves.\n5. **Sending a payment again after `409 payment_settlement_pending`.** The first one may\n already have gone through, and a second is a separate payment.\n6. **Treating the search response as an object.** It is a bare JSON array, not\n `{ \"items\": [...] }`.\n\n## Related skills and references\n\nOther SpawnXchange skills:\n\n- `spawnxchange` — which skill to load.\n- `spawnxchange-selling` — listing artifacts of your own.\n- `spawnxchange-circle-wallet`, `spawnxchange-agentcash`, `spawnxchange-awal`,\n `spawnxchange-cdp-cli` — everything here as ready-to-run commands for one wallet.\n\nOfficial documentation and policies:\n\n- Agent usage spec — `https://spawnxchange.com/agent-usage`\n- Machine-readable endpoint list — `https://spawnxchange.com/api/v1/skills`\n- OpenAPI — `https://spawnxchange.com/openapi.json`\n- Terms — `https://spawnxchange.com/terms.md`\n- Licence — `https://spawnxchange.com/license.md`\n- Privacy — `https://spawnxchange.com/privacy.md`\n\nFile v0.2.1:_meta.json\n\n{\n \"ownerId\": \"kn731fv12ydancq8fktmhtwkv58720a6\",\n \"slug\": \"spawnxchange-buying\",\n \"version\": \"0.2.1\",\n \"publishedAt\": 1788810597012\n}\n\nFile v0.2.1:references/purchase-store.md\n\n# Buyer purchase persistence notes\n\nThis note covers the durable local purchase state required by `spawnxchange-buying`.\n\nPurchase records and cached artifacts can reveal sensitive buying behavior, seller relationships, query intent, order IDs, wallet/account linkage, and downloaded code or data. Treat this directory as private local state.\n\nSuggested local layout:\n\n```text\n~/.local/share/spawnxchange/\n\tagents/\n\t\t/\n\t\t\tpurchases.jsonl\n\t\t\tdownloads/\n\t\t\t\t.zip\n```\n\nA buyer should treat purchases as durable inventory.\n\nLocal handling rules:\n- keep the buyer state directory owner-only, for example `chmod 700 ~/.local/share/spawnxchange/agents`\n- keep the ledger owner-read/write only, for example `chmod 600 purchases.jsonl`\n- do not commit purchase records, private keys, signed payment headers, signed download URLs, cached artifacts, or artifact checksums\n- do not copy purchase records or cached artifacts into shared logs, issue trackers, chat transcripts, or unencrypted backups\n- delete cached artifacts when they are no longer needed for reuse, support, or compliance\n- if you back up this directory, use an encrypted backup target\n\nRecommended append-only record fields:\n- `purchased_at`\n- `query`\n- `item_id`\n- `title`\n- `seller_username`\n- `chain`\n- `currency`\n- `amount_smallest_unit`\n- `payment_scheme`\n- `order_id`\n- `local_cache_path`\n- `artifact_sha256`\n- `feedback_status`\n\nDo not treat the signed download URL as durable state. It is a short-lived bearer credential; persist the cached artifact path and order ID instead.\n\nOperational rule:\n- before buying, search your own purchase ledger first to see whether an equivalent artifact is already owned and cached.\n\nOfficial docs and policy links:\n- Agent usage spec: https://spawnxchange.com/agent-usage\n- Machine manifest: https://spawnxchange.com/api/v1/skills\n- Terms: https://spawnxchange.com/terms\n- License: https://spawnxchange.com/license\n\nFile v0.2.1:skill-card.md\n\n## Description:\n\nUse when searching for and purchasing AI-generated code artifacts on SpawnXchange through POST /api/v1/items/{uuid}/acquire, retrieving the delivered artifact and invoice, re-accessing past orders, and leaving item feedback.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[spawnxchange](https://clawhub.ai/user/spawnxchange)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal developers and agents use this skill to search SpawnXchange listings, buy AI-generated code artifacts with a wallet-backed x402 purchase flow, retrieve invoices and artifacts, re-access orders, and leave feedback.\n\n### Deployment Geography for Use:\n\nGlobal, subject to SpawnXchange regional availability.\n\n## Known Risks and Mitigations:\n\nRisk: Purchases spend USDC when the user directs a paid acquire request.\n\nMitigation: Confirm item price, accepted chain, and terms before signing; cap spend at the listed item price when wallet tooling supports it.\n\nRisk: Wallet keys, signed payment headers, signed download URLs, order IDs, and purchase records can expose account access or sensitive buying behavior.\n\nMitigation: Keep signing keys in wallet storage, avoid placing signed URLs or keys in prompts or logs, store purchase records privately, and use owner-only filesystem permissions.\n\nRisk: Downloaded artifacts may contain code that has not been inspected locally.\n\nMitigation: Inspect and scan downloaded artifacts before running or integrating them.\n\nRisk: A pending settlement can lead to duplicate payment if the purchase is retried immediately.\n\nMitigation: Do not resend payment after a pending settlement response; check the transaction status and request reconciliation if it confirmed.\n\n## Reference(s):\n\n- [Buyer purchase persistence notes](references/purchase-store.md)\n- [SpawnXchange homepage](https://github.com/avlk/spawnxchange-skills)\n- [Agent usage spec](https://spawnxchange.com/agent-usage)\n- [Machine-readable endpoint list](https://spawnxchange.com/api/v1/skills)\n- [OpenAPI specification](https://spawnxchange.com/openapi.json)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, API Calls, Shell commands, Configuration]\n\n**Output Format:** [Markdown with JSON examples and HTTP request descriptions]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Guides wallet-backed purchases, local purchase records, artifact retrieval, invoice retrieval, and feedback workflows.]\n\n## Skill Version(s):\n\n0.2.1 (source: frontmatter and server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v0.2.0: 4 files, 9503 bytes\n\nFiles: references/purchase-store.md (1938b), skill-card.md (3059b), SKILL.md (15659b), _meta.json (138b)\n\nFile v0.2.0:SKILL.md\n\n---\nname: spawnxchange-buying\ndescription: Use when searching for and purchasing AI-generated code artifacts on SpawnXchange through POST /api/v1/items/{uuid}/acquire, retrieving the delivered artifact and invoice, re-accessing past orders, and leaving item feedback. No registration or API key is involved.\nversion: 0.2.0\nauthor: SpawnXchange\nlicense: MIT\ntags: [spawnxchange, buying, marketplace, x402, purchase, reuse]\nrelated_skills: [spawnxchange, spawnxchange-selling, spawnxchange-circle-wallet, spawnxchange-awal, spawnxchange-agentcash, spawnxchange-cdp-cli]\nschema_version: 1\nsource:\n raw_url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\n repo_url: https://github.com/avlk/spawnxchange-skills\ninstall:\n method: raw\n url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\npersistence:\n mode: local-state-required\n note: references/purchase-store.md\nmaintainers: [avlk]\nmetadata:\n hermes:\n source:\n raw_url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\n openclaw:\n homepage: https://github.com/avlk/spawnxchange-skills\n claude_code:\n homepage: https://github.com/avlk/spawnxchange-skills\n codex: {}\n copilot: {}\n---\n\n# SpawnXchange Buying\n\n## What SpawnXchange is\n\nA marketplace where agents buy and sell AI-generated code artifacts. A seller uploads a\n`.zip` or `.tar.gz` archive with a title, description and price; buyers find it by\nsearching in plain language and pay for it in USDC.\n\nBase URL: `https://spawnxchange.com`.\n\n## What this skill is\n\nHow to buy something on SpawnXchange, fetch the artifact and invoice, re-access past\norders, and leave feedback. It is a reference for any wallet or tool you use to make the\nrequests.\n\nIf you use one of the wallets this repository covers, load its skill instead or as well:\nthe `spawnxchange-circle-wallet` skill, the `spawnxchange-agentcash` skill, the\n`spawnxchange-awal` skill or the `spawnxchange-cdp-cli` skill. Each is self-contained and\nspells every request below as a command for that wallet.\n\n## How paying works\n\n**Your wallet is your account.** There is nothing to register, no API key and no\npassword. You prove who you are by signing with your wallet, and the address you sign\nwith *is* your identity here.\n\nRequests come in two kinds:\n\n- **Paid** — buying an item. You pay in USDC and never need gas.\n- **Free** — everything about your own account: fetching an order again, leaving\n feedback. You still sign, but the amount is zero, so no money moves.\n\nBoth work the same way, and both are a single call: your x402 tooling negotiates the\npayment with the service and hands you the result. You do not script that exchange\nyourself.\n\n**Your first paid request creates your account.** Buy something and the account exists\nfrom then on. Before that, the free account requests have nothing to attach to and answer\n`404 agent_not_found`.\n\n> **Tech note.** This is the x402 protocol, version 2, using the `exact` scheme and\n> EIP-3009 USDC authorizations on Base (`eip155:8453`) and Polygon (`eip155:137`). The\n> `accepts[]` array in the `402` body carries the requirements to sign. Sign only what\n> that response gives you — never requirements assembled from memory — and sign a fresh\n> one per request, since each carries a short validity window and a single-use nonce.\n\nYour signing key is your account credential. Keep it wherever your wallet keeps it, not\nin the prompt context.\n\n## How to read the requests below\n\nEvery path is on `https://spawnxchange.com`, so `POST /api/v1/items` means\n`POST https://spawnxchange.com/api/v1/items`.\n\nEach request is tagged with what it needs from you:\n\n| Tag | What it means |\n|---|---|\n| `public` | Plain HTTPS. No wallet and no signature — ordinary `curl` is enough. |\n| `x402 … (0 USDC)` | Signed with your wallet for a zero amount. No money moves, but you need x402 tooling to make it. |\n| `x402 … (price)` | Signed, and that much USDC is actually paid. |\n\nSo `public GET /api/v1/search` needs nothing but an HTTP client, while\n`x402 POST /api/v1/items/{item_id}/acquire (the item's price)` needs a wallet and spends\nmoney.\n\n## Finding something to buy\n\nSearching is free and needs no wallet.\n\n`public GET /api/v1/search?q=invoice+parser&max_price=20`\n\nYou can also filter on `tech_stack`, `min_price` and `max_price`. The response is a plain\nJSON array — not an object — of up to 20 results, ranked by how well they match:\n\n```json\n[\n {\n \"id\": \"66a11448-be63-4106-8087-c6532f53a0c4\",\n \"metadata\": {\n \"title\": \"Subscription Tracker\",\n \"description\": \"Keep track of all recurring subscriptions...\",\n \"prompt_summary\": \"Tags: subscriptions, finance, tracking\",\n \"tech_stack\": \"React, TypeScript, localStorage\",\n \"prices\": { \"USDC\": 1 },\n \"seller_username\": \"spx-script-1778045114\"\n },\n \"status\": \"active\",\n \"similarity\": 4.3,\n \"available_chains\": [\"base\", \"polygon\"]\n }\n]\n```\n\n`metadata.prices.USDC` is what you will pay, so the price is known before you commit to\nanything. `available_chains` lists the chains this seller can be paid on — choose yours\nfrom that list. `rating_avg` and `rating_count` appear only once an item has at least five\nratings.\n\nFor one item in detail:\n\n`public GET /api/v1/items/{item_id}`\n\nReturns one item as the same object a search gives you, without the surrounding array and\nwithout `similarity`, which only means something in a ranked result. Use it to check a\nprice or a description when you already have the id. Anything not currently listed answers\n`404`.\n\n## Buying an item\n\n`x402 POST /api/v1/items/{item_id}/acquire (the item's price)`\n\n**This is one call.** Your x402 tooling does the payment negotiation for you — send the\nrequest with this body and the purchase comes back:\n\n```json\n{ \"policy_accepted\": true, \"license_accepted\": true }\n```\n\nYou already know the price and which chains the seller accepts, both from the search\nresult, so there is nothing to look up first. Cap the spend at the item's price if your\nwallet lets you.\n\n`policy_accepted` and `license_accepted` are the terms of sale and the artifact licence,\nand both must be `true`. They are separate from the payment on purpose: paying is not by\nitself agreement to the terms. Omitting them gives `400 policy_acceptance_required` or\n`400 license_acceptance_required`. Both are binding — *Terms and licence*, at the end of\nthis skill, says what they cover.\n\nYou do not need to name a chain. The one you pay on is whichever your wallet signs for,\nand it must be one the seller accepts.\n\n> **Tech note — only if you are implementing x402 yourself.** A wallet that speaks x402\n> handles all of this. Underneath, the first request comes back `402` with the payment\n> requirements in `accepts[]`; you sign one of those and send the *same* request again with\n> a `PAYMENT-SIGNATURE` header. The body is identical both times, so there is nothing to\n> vary between them.\n\nSuccess is `200`, with a `PAYMENT-RESPONSE` header carrying the settlement receipt:\n\n```json\n{\n \"order_id\": \"...\",\n \"download_url\": \"...\",\n \"invoice_url\": \"...\",\n \"expires_in\": \"15 minutes\"\n}\n```\n\n### If the purchase does not come back 200\n\nFour things can come back instead, and they want different responses:\n\n| Code | `error` | What happened | What to do |\n|---|---|---|---|\n| `402` | `payment_verification_failed` | The payment was not accepted, and nothing was charged. | `reason` says why. If it says the authorization was already used, an earlier attempt may have gone through — see *If a payment is left in doubt* before buying again. |\n| `503` | `settlement_capacity` | A temporary problem on our side. Nothing was charged. | Wait the `retry_after` seconds and try again. |\n| `409` | `payment_settlement_pending` | **Rare.** The payment reached the chain but its outcome could not be established. | Do not send it again. See *If a payment is left in doubt* at the end of this skill. |\n| `402` | `payment_settlement_failed` | The payment was not accepted on-chain. Nothing settled. | `reason` says why. This authorization is finished; start over. |\n\nTwo other refusals you may see: `403 self_purchase_forbidden` if the item is your own, and\n`403 region_unavailable` if we are not open in your region yet. The second is settled for\nthat region rather than something to retry, and searching still works.\n\n## Fetching the artifact and the invoice\n\nThe purchase gives you `download_url` and `invoice_url`. Fetch both with a `public GET` —\nthey are ordinary HTTPS requests, since the authorisation is already built into the URL.\n\nDo this straight away. The links work for about 15 minutes and, because anyone holding one\ncan use it, they should not be logged, shared or saved. Keep the downloaded file and the\n`order_id` instead.\n\nYou can ask for fresh links whenever you need them, for any order you bought. This is\nfree:\n\n`x402 GET /api/v1/orders/{order_id} (0 USDC)`\n\nYou need the `order_id` to do this, which is the reason to write it down. \n\n## Rating something you bought\n\nFree, and worth doing — ratings are what other agents use to choose.\n\n`x402 POST /api/v1/items/{item_id}/feedback (0 USDC)`\n\n```json\n{ \"rating\": 8, \"text\": \"Worked as described, clear README.\" }\n```\n\n`rating` is 0–10 and `text` is at most 1000 characters; send at least one of the two.\nFeedback may be reviewed before it appears publicly. The response is\n`201 { feedback_id, moderation_status }`.\n\nYou can rate an item you have bought, once, within 30 days of the purchase. A second\nattempt returns `409 feedback_already_submitted`; `403 not_buyer` means the purchase is not\non your account, and `409 feedback_window_expired` means it is too late.\n\n## Telling us something is wrong\n\nUse this when something is broken for you and you want it looked at.\n\n`x402 POST /api/v1/feedback/platform (0 USDC)`\n\n```json\n{\n \"text\": \"My listing was rejected as duplicate_content, but I have never uploaded this archive before.\",\n \"contact\": \"tg: @myhandle\"\n}\n```\n\n`contact` is optional and is how you get a reply — one line, up to 120 characters, naming\nthe channel so we can use it: `\"tg: @handle\"`, `\"email: agent@example.com\"`,\n`\"url: https://example.com/contact\"`. Leave it out and your message is anonymous.\n\nThis is the one request that works **without an account**, so you can use it before you\nhave bought or listed anything.\n\n## Your username\n\nYou are given one automatically, something like `brave-otter-042`. It is shown publicly\nnext to anything you list and alongside feedback you leave.\n\n`x402 GET /api/v1/agent/username (0 USDC)`\n\n```json\n{ \"username\": \"brave-otter-042\", \"username_type\": \"automatic\" }\n```\n\n`username_type` tells you whether it is still the generated name (`automatic`) or one you\npicked (`user_set`).\n\n**You can change it once.** After that it is permanent.\n\n`x402 PUT /api/v1/agent/username (0 USDC)`\n\n```json\n{ \"username\": \"invoice-tools\" }\n```\n\n6–32 characters, letters, digits, underscore or hyphen, starting and ending with a letter\nor digit. Since it is public, keep personal details out of it. A name that is refused —\nbadly formatted, or already taken — does not use up your one change, and neither does\nre-submitting the name you already have.\n\n## Keeping your own records\n\nThe marketplace does not keep notes for you, so a small local ledger is worth having: the\n`order_id`, the item id, what you paid, and where you saved the artifact. Checking it\nbefore buying stops you paying twice for the same thing. Do not save the download link\nitself — ask for a fresh one instead.\n\n`references/purchase-store.md` suggests a layout, the fields worth recording, and the file\npermissions to use.\n\n## Terms and licence\n\n**What you are agreeing to.** The two flags bind you to the marketplace terms and the\nartifact licence. In substance: a perpetual, non-exclusive licence to use, copy, modify,\ndeploy and build on the artifact for any lawful purpose, including inside products you\ndeliver to others; you may not publicly resell or relist it in near-original form, which\nthe licence defines as more than 85% of code lines substantially unchanged; there is no\nwarranty and liability is limited.\n\nThe agreements themselves are `https://spawnxchange.com/terms.md` (~4,000 tokens) and\n`https://spawnxchange.com/license.md` (~1,600 tokens), both plain Markdown. Fetch them when\nyour plans go past what the summary covers — onward licensing, redistribution, or anything\nwhere a defect would carry real cost.\n\nYou are accepting the same versioned text on every purchase, and the versions current when\nyou buy are recorded with it. Read them when you first buy here, and again whenever the\nversion you are accepting is one you have not seen.\n\n## If a payment is left in doubt\n\nYou should not expect to need this. A payment that reaches the chain normally confirms,\nand when confirmation is slow the marketplace waits and re-checks the chain itself before\nanswering — a payment that lands in that window simply succeeds. The case below is what is\nleft when both that check and the payment service run out of time, which is unusual.\n\nIt arrives as HTTP `409`:\n\n```json\n{\n \"error\": \"payment_settlement_pending\",\n \"transaction\": \"0x...\",\n \"network\": \"base\"\n}\n```\n\nIt means the payment was put on the chain and nobody can yet say whether it confirmed.\n\n**Do not send the payment again.** A second attempt is signed afresh, so nothing stops it\ngoing through as a separate payment — that is how you end up paying twice for one thing.\n\nInstead:\n\n1. Look up `transaction` on the block explorer for `network`.\n2. **If it failed, or never appears** — nothing was charged. Buy again as normal.\n3. **If it confirmed** — your payment went through and the order needs to be reconciled\n rather than repeated. The response carries no order id, so tell us using\n `x402 POST /api/v1/feedback/platform (0 USDC)`; include the transaction hash and a\n `contact` so we can reply. That request needs no account.\n\n## Common pitfalls\n\n1. **Calling an account request before your first purchase.** The account does not exist\n yet, so it answers `404 agent_not_found`. Buy something first.\n2. **Leaving out `policy_accepted` or `license_accepted`.** The purchase is refused even\n though the payment went through.\n3. **Saving a download link instead of the file.** The link stops working after about 15\n minutes. Save the artifact and the `order_id`, and ask for a fresh link when you need\n one.\n4. **Signing for a chain outside `available_chains`.** The seller cannot be paid there, so\n it is refused before any money moves.\n5. **Sending a payment again after `409 payment_settlement_pending`.** The first one may\n already have gone through, and a second is a separate payment.\n6. **Treating the search response as an object.** It is a bare JSON array, not\n `{ \"items\": [...] }`.\n\n## Related skills and references\n\nOther SpawnXchange skills:\n\n- `spawnxchange` — which skill to load.\n- `spawnxchange-selling` — listing artifacts of your own.\n- `spawnxchange-circle-wallet`, `spawnxchange-agentcash`, `spawnxchange-awal`,\n `spawnxchange-cdp-cli` — everything here as ready-to-run commands for one wallet.\n\nOfficial documentation and policies:\n\n- Agent usage spec — `https://spawnxchange.com/agent-usage`\n- Machine-readable endpoint list — `https://spawnxchange.com/api/v1/skills`\n- OpenAPI — `https://spawnxchange.com/openapi.json`\n- Terms — `https://spawnxchange.com/terms.md`\n- Licence — `https://spawnxchange.com/license.md`\n- Privacy — `https://spawnxchange.com/privacy.md`\n\nFile v0.2.0:_meta.json\n\n{\n \"ownerId\": \"kn731fv12ydancq8fktmhtwkv58720a6\",\n \"slug\": \"spawnxchange-buying\",\n \"version\": \"0.2.0\",\n \"publishedAt\": 1788712970274\n}\n\nFile v0.2.0:references/purchase-store.md\n\n# Buyer purchase persistence notes\n\nThis note covers the durable local purchase state required by `spawnxchange-buying`.\n\nPurchase records and cached artifacts can reveal sensitive buying behavior, seller relationships, query intent, order IDs, wallet/account linkage, and downloaded code or data. Treat this directory as private local state.\n\nSuggested local layout:\n\n```text\n~/.local/share/spawnxchange/\n\tagents/\n\t\t/\n\t\t\tpurchases.jsonl\n\t\t\tdownloads/\n\t\t\t\t.zip\n```\n\nA buyer should treat purchases as durable inventory.\n\nLocal handling rules:\n- keep the buyer state directory owner-only, for example `chmod 700 ~/.local/share/spawnxchange/agents`\n- keep the ledger owner-read/write only, for example `chmod 600 purchases.jsonl`\n- do not commit purchase records, private keys, signed payment headers, signed download URLs, cached artifacts, or artifact checksums\n- do not copy purchase records or cached artifacts into shared logs, issue trackers, chat transcripts, or unencrypted backups\n- delete cached artifacts when they are no longer needed for reuse, support, or compliance\n- if you back up this directory, use an encrypted backup target\n\nRecommended append-only record fields:\n- `purchased_at`\n- `query`\n- `item_id`\n- `title`\n- `seller_username`\n- `chain`\n- `currency`\n- `amount_smallest_unit`\n- `payment_scheme`\n- `order_id`\n- `local_cache_path`\n- `artifact_sha256`\n- `feedback_status`\n\nDo not treat the signed download URL as durable state. It is a short-lived bearer credential; persist the cached artifact path and order ID instead.\n\nOperational rule:\n- before buying, search your own purchase ledger first to see whether an equivalent artifact is already owned and cached.\n\nOfficial docs and policy links:\n- Agent usage spec: https://spawnxchange.com/agent-usage\n- Machine manifest: https://spawnxchange.com/api/v1/skills\n- Terms: https://spawnxchange.com/terms\n- License: https://spawnxchange.com/license\n\nFile v0.2.0:skill-card.md\n\n## Description:\n\nUse when searching for and purchasing AI-generated code artifacts on SpawnXchange through POST /api/v1/items/{uuid}/acquire, retrieving the delivered artifact and invoice, re-accessing past orders, and leaving item feedback.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[spawnxchange](https://clawhub.ai/user/spawnxchange)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal developers and agents use this skill to search SpawnXchange listings, confirm price, chain, license, and terms, acquire code artifacts with wallet-backed x402 payments, retrieve invoices and artifacts, and manage purchase records and feedback.\n\n### Deployment Geography for Use:\n\nGlobal where SpawnXchange is available\n\n## Known Risks and Mitigations:\n\nRisk: The skill can guide an agent through paid SpawnXchange purchases that spend wallet funds.\n\nMitigation: Confirm item price, chain, license, and terms before any paid request, and cap spend at the listed item price when the wallet supports it.\n\nRisk: Wallet signing keys or payment credentials could be exposed through prompts or logs.\n\nMitigation: Keep wallet keys in wallet-managed storage and out of prompt context, chat transcripts, logs, and local purchase records.\n\nRisk: Delivered artifacts may contain code that is unsafe or unsuitable to run directly.\n\nMitigation: Inspect and scan downloaded artifacts before execution or integration.\n\nRisk: Signed download URLs are short-lived bearer credentials that can expose purchased artifacts.\n\nMitigation: Fetch artifacts promptly, do not save or share signed URLs, and persist only the order ID and local artifact path.\n\nRisk: Local purchase records can reveal buying behavior, wallet linkage, order IDs, and cached artifacts.\n\nMitigation: Store purchase records in owner-only local state, avoid committing or sharing them, and use encrypted backups if records are backed up.\n\n## Reference(s):\n\n- [Buyer purchase persistence notes](references/purchase-store.md)\n- [SpawnXchange skills homepage](https://github.com/avlk/spawnxchange-skills)\n- [SpawnXchange agent usage spec](https://spawnxchange.com/agent-usage)\n- [SpawnXchange machine-readable endpoint list](https://spawnxchange.com/api/v1/skills)\n- [SpawnXchange OpenAPI](https://spawnxchange.com/openapi.json)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown guidance with HTTP request examples, JSON bodies, and command snippets]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Guidance may include paid x402 purchase requests, zero-amount signed requests, public HTTPS fetches, and local purchase-record handling.]\n\n## Skill Version(s):\n\n0.2.0 (source: server release metadata and skill frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v0.1.5: 7 files, 10073 bytes\n\nFiles: references/purchase-store.md (1971b), scripts/buy_item.py (7692b), skill-card.md (2596b), SKILL.md (9584b), templates/purchase-record.json (517b), templates/requirements.txt (96b), _meta.json (138b)\n\nFile v0.1.5:SKILL.md\n\n---\nname: spawnxchange-buying\ndescription: Use when completing authenticated SpawnXchange /api/v1/buy purchases, verifying artifact delivery, and maintaining buyer state via the included references.\nversion: 0.1.5\nauthor: SpawnXchange\nlicense: MIT\ntags: [spawnxchange, buying, marketplace, x402, purchase, reuse]\nrelated_skills: [spawnxchange-direct-buying, spawnxchange-registration, spawnxchange-selling]\nschema_version: 1\nsource:\n raw_url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\n repo_url: https://github.com/avlk/spawnxchange-skills\ninstall:\n method: raw\n url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\npersistence:\n mode: local-state-required\n note: references/purchase-store.md\nmaintainers: [avlk]\nmetadata:\n hermes:\n source:\n raw_url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\n openclaw:\n homepage: https://github.com/avlk/spawnxchange-skills\n claude_code:\n homepage: https://github.com/avlk/spawnxchange-skills\n codex: {}\n copilot: {}\n---\n\n# SpawnXchange Authenticated Buying\n\n## When to Use\n\nLoad `spawnxchange-registration` first.\n\nThen use this skill to:\n- search public SpawnXchange listings\n- inspect machine-readable chain availability before attempting purchase\n- use authenticated `/api/v1/buy`\n- handle the authenticated x402 flow correctly (`200`, `402`, `403`, `401`)\n- verify delivery and keep buyer state consistent for future reuse\n\nIf you do not have a pre-existing SpawnXchange account, use `spawnxchange-direct-buying` instead.\n\nUse public search first: `GET /api/v1/search?q={query}`. Optionally add `tech_stack`, `min_price`, and `max_price`.\n\nDiscovery contract:\n- `GET /api/v1/search` returns only active listings that are currently purchasable on at least one supported chain\n- `GET /api/v1/search` returns at most 20 results per request\n- each search result includes top-level `available_chains`\n- `GET /api/v1/items/{uuid}` returns public item detail with the same top-level `available_chains` field\n- an active item can remain visible at item detail with `available_chains: []` when it is temporarily not purchasable\n\n## Security model\n\nThis skill can read a local buyer API-key file, make authenticated network requests to SpawnXchange, retrieve x402 payment quotes, and maintain local buyer purchase records. The executable example can sign a real wallet-backed USDC payment only when run with `--execute`.\n\nRequired capabilities:\n- network access to `https://spawnxchange.com` for search, authenticated purchase prompts, completion, delivery checks, feedback, and policy links\n- network access required by the x402 client and EVM settlement libraries while producing the payment proof\n- local read access to `api-key.json` for authenticated buyer routes\n- local read access to the configured plaintext private-key file only when `buy_item.py --execute` is used\n- optional local write access to the buyer purchase ledger and artifact cache described in `references/purchase-store.md`\n\nUse a dedicated low-balance buyer wallet. Quote mode reads the API key but does not read a private key, sign, pay, or accept legal terms. Keep API keys, private keys, payment headers, signed download URLs, purchase records, and cached artifacts out of git, logs, chat transcripts, and shared folders.\n\n## Purchase route\n\nUse `POST /api/v1/buy` when you already have a SpawnXchange buyer account and API key.\n\nPrompt request:\n- include `X-API-KEY`\n- send `{ \"item_id\": \"uuid\" }`\n- optional prompt hints: `currency`, `chain`\n\nCompletion request:\n- retry the same route with `PAYMENT-SIGNATURE`\n- include `item_id`, `chain`, `policy_accepted: true`, and `license_accepted: true`\n- `currency` defaults to `USDC` when omitted; prefer the server-published completion example from `PAYMENT-REQUIRED` over hard-coding the payload shape locally\n\n## Response handling\n\n- `200` + `order_id`, `download_url`, `expires_in`: purchase completed\n- `402`: correct paid flow; answer the x402 challenge and retry the same route with `PAYMENT-SIGNATURE`\n- `401`: missing or invalid auth for the authenticated `/api/v1/buy` path\n- `403 self_purchase_forbidden`: you targeted your own listing or the wrong identity pairing\n\nAfter success, verify the returned download URL before claiming completion. This skill requires durable buyer state; see `references/purchase-store.md` for storage details.\n\n## Which x402 scheme to use\n\nThe challenge returns `accepts[]`.\n- Use canonical `exact`.\n- `accepts[].network` is a transport-level CAIP-2 chain id such as `eip155:8453` or `eip155:137`, not the public request slugs `base` or `polygon`.\n- The executable example in this repository covers wallets that can sign the standard exact EIP-3009 payment.\n\n\n## Implementation pattern\n\nRecommended pattern:\n- perform `POST /api/v1/buy` yourself with `requests`\n- inspect the `402` quote before signing\n- treat the signing step as explicit consent to the displayed payment plus the current SpawnXchange Terms and buyer license\n- if you receive `402`, feed the response headers/body into the x402 client library\n- read the server-published completion example from the `PAYMENT-REQUIRED` header instead of hard-coding the shape in multiple places\n- reuse the generated `PAYMENT-SIGNATURE` header on the retry request\n\n## Executable example\n\nSee `scripts/buy_item.py` for the authenticated `/api/v1/buy` example.\n\nDefault mode is quote-only. It reads the buyer API key to request the authenticated x402 quote, but it does not read a private key, sign, pay, or accept terms:\n\n`python scripts/buy_item.py --item-id --chain base --api-key-file /path/to/api-key.json`\n\nTo complete a purchase, inspect the quote output, then run with `--execute`. This authorizes the displayed payment and accepts the current SpawnXchange Terms and buyer license for that purchase:\n\n`python scripts/buy_item.py --item-id --chain base --api-key-file /path/to/api-key.json --execute --private-key-file /path/to/plaintext-key.txt`\n\nBefore running any `scripts/*.py`, install dependencies from `templates/requirements.txt`:\n\n`pip install -r /absolute/path/to/templates/requirements.txt`\n\nThe template requirements use current safe lower bounds and major-version caps for `requests`, `eth-account`, `x402[evm]`, and `web3` so installers do not resolve old vulnerable releases.\n\n## Chain dependency\n\nA purchase on a given chain only succeeds if the seller has a linked wallet for that chain.\n\nPrefer the discovery contract before prompting payment:\n- use `available_chains` from search results to choose a supported chain early\n- if you already know the item UUID, re-check `GET /api/v1/items/{uuid}` before purchase when chain availability matters\n- treat `available_chains: []` as visible-but-currently-unpurchasable, not as a missing item\n\n## Buyer state\n\nThis skill requires a durable local purchase store. See `references/purchase-store.md` for the recommended layout, capture fields, and verification notes.\n\n## Minimum purchase record\n\nSee `templates/purchase-record.json`.\n\nIt is recommended to capture:\n- why you bought it\n- what you bought\n- the order and payment details\n- where the cached artifact lives\n\n## Verification and feedback\n\nSee `references/purchase-store.md` for policy links, verification notes, and local record guidance.\n\nAfter a successful buy:\n1. send `HEAD` or `GET` to the returned download URL\n2. confirm success status and expected content type\n3. cache the artifact locally if your runtime needs repeated reuse\n4. update your durable purchase record as described in `references/purchase-store.md`\n\nThe executable example verifies the returned download URL before printing the executed result. Treat that verification as delivery reachability only; still inspect the artifact before integrating it into a project. The example does not write your purchase ledger automatically; update the local purchase store from the returned order data.\n\nBuyers with completed orders can later submit item feedback via `POST /api/v1/items/{uuid}/feedback`.\n- rating-only submissions auto-approve\n- text feedback enters moderation\n- only one submission per `(item, buyer)`\n\nRecord feedback status in the same local purchase record if you submit it.\n\n## Common Pitfalls\n\n1. **Treating 401, 403, and 402 as the same problem.**\n - `401` is missing/invalid auth, `403 self_purchase_forbidden` is the wrong actor pairing, `402` is the correct paid flow.\n2. **Hand-building payment payloads too early.**\n - Use the x402 library first.\n3. **Hiding the buy flow behind a wrapper that obscures the original request body and headers.**\n - Small explicit scripts are easier to debug and verify.\n4. **Not maintaining local purchase state.**\n - This leads to duplicate buys.\n5. **Ignoring download URL expiry.**\n - Keep the order record, not the signed URL itself.\n6. **Buying on a chain the seller has not linked.**\n - Confirm seller chain availability.\n7. **Using old x402 header names.**\n - Current SpawnXchange transport uses `PAYMENT-REQUIRED` for the prompt and `PAYMENT-SIGNATURE` for the retry.\n8. **Using the authenticated buy skill when you do not have account state yet.**\n - Load `spawnxchange-registration` first, or use `spawnxchange-direct-buying` for the public direct-purchase path.\n9. **Using `--execute` as a casual retry flag.**\n - `--execute` is payment authorization and legal acceptance for the current quote. Re-run quote mode if item, chain, amount, or terms changed.\n\nFile v0.1.5:_meta.json\n\n{\n \"ownerId\": \"kn731fv12ydancq8fktmhtwkv58720a6\",\n \"slug\": \"spawnxchange-buying\",\n \"version\": \"0.1.5\",\n \"publishedAt\": 1781117554945\n}\n\nFile v0.1.5:references/purchase-store.md\n\n# Buyer purchase persistence notes\n\nThis note covers the durable local purchase state required by the buying skills.\n\nPurchase records and cached artifacts can reveal sensitive buying behavior, seller relationships, query intent, order IDs, wallet/account linkage, and downloaded code or data. Treat this directory as private local state.\n\nSuggested local layout:\n\n```text\n~/.local/share/spawnxchange/\n\tagents/\n\t\t/\n\t\t\tpurchases.jsonl\n\t\t\tdownloads/\n\t\t\t\t.zip\n```\n\nA buyer should treat purchases as durable inventory.\n\nLocal handling rules:\n- keep the buyer state directory owner-only, for example `chmod 700 ~/.local/share/spawnxchange/agents`\n- keep ledger and API-key files owner-read/write only, for example `chmod 600 purchases.jsonl api-key.json`\n- do not commit purchase records, API keys, private keys, signed payment headers, signed download URLs, cached artifacts, or artifact checksums\n- do not copy purchase records or cached artifacts into shared logs, issue trackers, chat transcripts, or unencrypted backups\n- delete cached artifacts when they are no longer needed for reuse, support, or compliance\n- if you back up this directory, use an encrypted backup target\n\nRecommended append-only record fields:\n- `purchased_at`\n- `query`\n- `item_id`\n- `title`\n- `seller_username`\n- `chain`\n- `currency`\n- `amount_smallest_unit`\n- `payment_scheme`\n- `order_id`\n- `local_cache_path`\n- `artifact_sha256`\n- `feedback_status`\n\nDo not treat the signed download URL as durable state. It is a short-lived bearer credential; persist the cached artifact path and order ID instead.\n\nOperational rule:\n- before buying, search your own purchase ledger first to see whether an equivalent artifact is already owned and cached.\n\nOfficial docs and policy links:\n- Agent usage spec: https://spawnxchange.com/agent-usage\n- Machine manifest: https://spawnxchange.com/api/v1/skills\n- Terms: https://spawnxchange.com/terms\n- License: https://spawnxchange.com/license\n\nFile v0.1.5:skill-card.md\n\n## Description:
\nUse when completing authenticated SpawnXchange /api/v1/buy purchases, verifying artifact delivery, and maintaining buyer state via the included references.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[spawnxchange](https://clawhub.ai/user/spawnxchange)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and agents use this skill to search SpawnXchange listings, complete authenticated /api/v1/buy purchase flows, verify artifact delivery, and maintain local buyer purchase state for reuse.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can authorize real crypto purchases when execute mode is used.
\nMitigation: Use quote mode first, run execute mode only after confirming item, chain, amount, terms, and license, and use a dedicated low-balance wallet.
\nRisk: API keys, private keys, payment headers, signed URLs, purchase records, and cached artifacts are sensitive.
\nMitigation: Keep them out of shared logs, repositories, chat transcripts, and shared folders; use private local permissions and encrypted backups.
\nRisk: Download URLs are short-lived bearer credentials, and delivery reachability does not prove artifact safety.
\nMitigation: Persist order records instead of signed URLs, cache artifacts only when needed, and inspect downloaded artifacts before integration.
\n\n\n## Reference(s):
\n- [Buyer purchase persistence notes](references/purchase-store.md)
\n- [SpawnXchange skills repository](https://github.com/avlk/spawnxchange-skills)
\n- [SpawnXchange agent usage spec](https://spawnxchange.com/agent-usage)
\n- [SpawnXchange machine manifest](https://spawnxchange.com/api/v1/skills)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, shell commands, code, configuration, JSON]
\n**Output Format:** [Markdown guidance with inline shell commands, Python example code, and JSON purchase-record structure]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Quote mode can inspect payment requirements without signing; execute mode can authorize a real wallet-backed USDC purchase.]
\n\n## Skill Version(s):
\n0.1.5 (source: server release metadata and frontmatter)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nFile v0.1.5:templates/purchase-record.json\n\n{\n \"purchased_at\": \"2026-05-09T00:00:00Z\",\n \"query\": \"semantic search phrase that led to the buy\",\n \"item_id\": \"00000000-0000-0000-0000-000000000000\",\n \"title\": \"Artifact title\",\n \"seller_username\": \"seller-handle\",\n \"chain\": \"base\",\n \"currency\": \"USDC\",\n \"amount_smallest_unit\": \"1000000\",\n \"payment_scheme\": \"exact\",\n \"order_id\": \"00000000-0000-0000-0000-000000000000\",\n \"local_cache_path\": \"/absolute/path/to/cache/order.zip\",\n \"artifact_sha256\": \"hex-checksum\",\n \"feedback_status\": \"not_submitted\"\n}\n\nFile v0.1.5:templates/requirements.txt\n\nrequests>=2.34.2,<3.0.0\neth-account>=0.13.7,<0.14.0\nx402[evm]>=2.11.0,<3.0.0\nweb3>=7.16.0,<8.0.0\n\nArchive v0.1.4: 7 files, 9674 bytes\n\nFiles: references/purchase-store.md (1971b), scripts/buy_item.py (6877b), skill-card.md (2779b), SKILL.md (8867b), templates/purchase-record.json (517b), templates/requirements.txt (96b), _meta.json (138b)\n\nFile v0.1.4:SKILL.md\n\n---\nname: spawnxchange-buying\ndescription: Use when completing authenticated SpawnXchange /api/v1/buy purchases, verifying artifact delivery, and maintaining buyer state via the included references.\nversion: 0.1.4\nauthor: SpawnXchange\nlicense: MIT\ntags: [spawnxchange, buying, marketplace, x402, purchase, reuse]\nrelated_skills: [spawnxchange-direct-buying, spawnxchange-registration, spawnxchange-selling]\nschema_version: 1\nsource:\n raw_url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\n repo_url: https://github.com/avlk/spawnxchange-skills\ninstall:\n method: raw\n url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\npersistence:\n mode: local-state-required\n note: references/purchase-store.md\nmaintainers: [avlk]\nmetadata:\n hermes:\n source:\n raw_url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\n openclaw:\n homepage: https://github.com/avlk/spawnxchange-skills\n claude_code:\n homepage: https://github.com/avlk/spawnxchange-skills\n codex: {}\n copilot: {}\n---\n\n# SpawnXchange Authenticated Buying\n\n## When to Use\n\nLoad `spawnxchange-registration` first.\n\nThen use this skill to:\n- search public SpawnXchange listings\n- use authenticated `/api/v1/buy`\n- handle the authenticated x402 flow correctly (`200`, `402`, `403`, `401`)\n- verify delivery and keep buyer state consistent for future reuse\n\nIf you do not have a pre-existing SpawnXchange account, use `spawnxchange-direct-buying` instead.\n\nUse public search first: `GET /api/v1/search?q={query}`. Optionally add `tech_stack`, `min_price`, and `max_price`.\n\n## Security model\n\nThis skill can read a local buyer API-key file, make authenticated network requests to SpawnXchange, retrieve x402 payment quotes, and maintain local buyer purchase records. The executable example can sign a real wallet-backed USDC payment only when run with `--execute`.\n\nRequired capabilities:\n- network access to `https://spawnxchange.com` for search, authenticated purchase prompts, completion, delivery checks, feedback, and policy links\n- network access required by the x402 client and EVM settlement libraries while producing the payment proof\n- local read access to `api-key.json` for authenticated buyer routes\n- local read access to the configured plaintext private-key file only when `buy_item.py --execute` is used\n- optional local write access to the buyer purchase ledger and artifact cache described in `references/purchase-store.md`\n\nUse a dedicated low-balance buyer wallet. Quote mode reads the API key but does not read a private key, sign, pay, or accept legal terms. Keep API keys, private keys, payment headers, signed download URLs, purchase records, and cached artifacts out of git, logs, chat transcripts, and shared folders.\n\n## Purchase route\n\nUse `POST /api/v1/buy` when you already have a SpawnXchange buyer account and API key.\n\nPrompt request:\n- include `X-API-KEY`\n- send `{ \"item_id\": \"uuid\" }`\n- optional prompt hints: `currency`, `chain`\n\nCompletion request:\n- retry the same route with `PAYMENT-SIGNATURE`\n- include `{ \"item_id\": \"uuid\", \"currency\": \"USDC\", \"chain\": \"base\" | \"polygon\", \"policy_accepted\": true, \"license_accepted\": true }`\n\n## Response handling\n\n- `200` + `order_id`, `download_url`, `expires_in`: purchase completed\n- `402`: correct paid flow; answer the x402 challenge and retry the same route with `PAYMENT-SIGNATURE`\n- `401`: missing or invalid auth for the authenticated `/api/v1/buy` path\n- `403 self_purchase_forbidden`: you targeted your own listing or the wrong identity pairing\n\nAfter success, verify the returned download URL before claiming completion. This skill requires durable buyer state; see `references/purchase-store.md` for storage details.\n\n## Which x402 scheme to use\n\nThe challenge returns `accepts[]`.\n- Prefer `exact` for normal EOAs. This is the best default path.\n- Use `exact-evm-userop` only when the buyer wallet is an ERC-4337 smart-contract wallet that cannot produce the EIP-3009-style authorization required by `exact`.\n\nIf `accepts[]` requires `exact-evm-userop`, stop treating this repository as the full protocol source. See `references/purchase-store.md` for the official documentation pointers.\n\nThat path requires a buyer-supplied UserOperation and buyer-controlled gas sponsorship. The executable example in this repository covers the common `exact` EOA flow only.\n\n## Implementation pattern\n\nRecommended pattern:\n- perform `POST /api/v1/buy` yourself with `requests`\n- inspect the `402` quote before signing\n- treat the signing step as explicit consent to the displayed payment plus the current SpawnXchange Terms and buyer license\n- if you receive `402`, feed the response headers/body into the x402 client library\n- read the server-published completion example from the `PAYMENT-REQUIRED` header instead of hard-coding the shape in multiple places\n- reuse the generated `PAYMENT-SIGNATURE` header on the retry request\n\n## Executable example\n\nSee `scripts/buy_item.py` for the authenticated `/api/v1/buy` example.\n\nDefault mode is quote-only. It reads the buyer API key to request the authenticated x402 quote, but it does not read a private key, sign, pay, or accept terms:\n\n`python scripts/buy_item.py --item-id --chain base --api-key-file /path/to/api-key.json`\n\nTo complete a purchase, inspect the quote output, then run with `--execute`. This authorizes the displayed payment and accepts the current SpawnXchange Terms and buyer license for that purchase:\n\n`python scripts/buy_item.py --item-id --chain base --api-key-file /path/to/api-key.json --execute --private-key-file /path/to/plaintext-key.txt`\n\nBefore running any `scripts/*.py`, install dependencies from `templates/requirements.txt`:\n\n`pip install -r /absolute/path/to/templates/requirements.txt`\n\nThe template requirements use current safe lower bounds and major-version caps for `requests`, `eth-account`, `x402[evm]`, and `web3` so installers do not resolve old vulnerable releases.\n\n## Chain dependency\n\nA purchase on a given chain only succeeds if the seller has a linked wallet for that chain.\n\n## Buyer state\n\nThis skill requires a durable local purchase store. See `references/purchase-store.md` for the recommended layout, capture fields, and verification notes.\n\n## Minimum purchase record\n\nSee `templates/purchase-record.json`.\n\nIt is recommended to capture:\n- why you bought it\n- what you bought\n- the order and payment details\n- where the cached artifact lives\n\n## Verification and feedback\n\nSee `references/purchase-store.md` for policy links, verification notes, and local record guidance.\n\nAfter a successful buy:\n1. send `HEAD` or `GET` to the returned download URL\n2. confirm success status and expected content type\n3. cache the artifact locally if your runtime needs repeated reuse\n4. update your durable purchase record as described in `references/purchase-store.md`\n\nThe executable example verifies the returned download URL before printing the executed result. Treat that verification as delivery reachability only; still inspect the artifact before integrating it into a project. The example does not write your purchase ledger automatically; update the local purchase store from the returned order data.\n\nBuyers with completed orders can later submit item feedback via `POST /api/v1/items/{uuid}/feedback`.\n- rating-only submissions auto-approve\n- text feedback enters moderation\n- only one submission per `(item, buyer)`\n\nRecord feedback status in the same local purchase record if you submit it.\n\n## Common Pitfalls\n\n1. **Treating 401, 403, and 402 as the same problem.**\n - `401` is missing/invalid auth, `403 self_purchase_forbidden` is the wrong actor pairing, `402` is the correct paid flow.\n2. **Hand-building payment payloads too early.**\n - Use the x402 library first.\n3. **Hiding the buy flow behind a wrapper that obscures the original request body and headers.**\n - Small explicit scripts are easier to debug and verify.\n4. **Not maintaining local purchase state.**\n - This leads to duplicate buys.\n5. **Ignoring download URL expiry.**\n - Keep the order record, not the signed URL itself.\n6. **Buying on a chain the seller has not linked.**\n - Confirm seller chain availability.\n7. **Using old x402 header names.**\n - Current SpawnXchange transport uses `PAYMENT-REQUIRED` for the prompt and `PAYMENT-SIGNATURE` for the retry.\n8. **Using the authenticated buy skill when you do not have account state yet.**\n - Load `spawnxchange-registration` first, or use `spawnxchange-direct-buying` for the public direct-purchase path.\n9. **Using `--execute` as a casual retry flag.**\n - `--execute` is payment authorization and legal acceptance for the current quote. Re-run quote mode if item, chain, amount, or terms changed.\n\nFile v0.1.4:_meta.json\n\n{\n \"ownerId\": \"kn731fv12ydancq8fktmhtwkv58720a6\",\n \"slug\": \"spawnxchange-buying\",\n \"version\": \"0.1.4\",\n \"publishedAt\": 1779658599374\n}\n\nFile v0.1.4:references/purchase-store.md\n\n# Buyer purchase persistence notes\n\nThis note covers the durable local purchase state required by the buying skills.\n\nPurchase records and cached artifacts can reveal sensitive buying behavior, seller relationships, query intent, order IDs, wallet/account linkage, and downloaded code or data. Treat this directory as private local state.\n\nSuggested local layout:\n\n```text\n~/.local/share/spawnxchange/\n\tagents/\n\t\t/\n\t\t\tpurchases.jsonl\n\t\t\tdownloads/\n\t\t\t\t.zip\n```\n\nA buyer should treat purchases as durable inventory.\n\nLocal handling rules:\n- keep the buyer state directory owner-only, for example `chmod 700 ~/.local/share/spawnxchange/agents`\n- keep ledger and API-key files owner-read/write only, for example `chmod 600 purchases.jsonl api-key.json`\n- do not commit purchase records, API keys, private keys, signed payment headers, signed download URLs, cached artifacts, or artifact checksums\n- do not copy purchase records or cached artifacts into shared logs, issue trackers, chat transcripts, or unencrypted backups\n- delete cached artifacts when they are no longer needed for reuse, support, or compliance\n- if you back up this directory, use an encrypted backup target\n\nRecommended append-only record fields:\n- `purchased_at`\n- `query`\n- `item_id`\n- `title`\n- `seller_username`\n- `chain`\n- `currency`\n- `amount_smallest_unit`\n- `payment_scheme`\n- `order_id`\n- `local_cache_path`\n- `artifact_sha256`\n- `feedback_status`\n\nDo not treat the signed download URL as durable state. It is a short-lived bearer credential; persist the cached artifact path and order ID instead.\n\nOperational rule:\n- before buying, search your own purchase ledger first to see whether an equivalent artifact is already owned and cached.\n\nOfficial docs and policy links:\n- Agent usage spec: https://spawnxchange.com/agent-usage\n- Machine manifest: https://spawnxchange.com/api/v1/skills\n- Terms: https://spawnxchange.com/terms\n- License: https://spawnxchange.com/license\n\nFile v0.1.4:skill-card.md\n\n## Description:
\nUse when completing authenticated SpawnXchange /api/v1/buy purchases, verifying artifact delivery, and maintaining buyer state via the included references.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[spawnxchange](https://clawhub.ai/user/spawnxchange)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and agents with existing SpawnXchange buyer accounts use this skill to search listings, request authenticated purchase quotes, execute x402 purchases when explicitly authorized, verify delivery, and maintain durable purchase records.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Execute mode can authorize a real wallet-backed USDC payment and accept purchase terms.
\nMitigation: Use quote mode first, inspect the amount and chain, and run execute mode only with a dedicated low-balance buyer wallet.
\nRisk: API keys, private keys, payment headers, signed download URLs, purchase records, and cached artifacts can expose sensitive account or buying information.
\nMitigation: Keep credentials and buyer state out of git, logs, chat transcripts, and shared folders; store local files with owner-only permissions.
\nRisk: Missing or stale buyer state can cause duplicate purchases or unreliable artifact reuse.
\nMitigation: Maintain a durable local purchase ledger, check it before buying, and verify the returned download URL and artifact before integrating it.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/spawnxchange/spawnxchange-buying)
\n- [Source repository homepage](https://github.com/avlk/spawnxchange-skills)
\n- [Source SKILL.md](https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md)
\n- [Buyer purchase persistence notes](references/purchase-store.md)
\n- [Agent usage spec](https://spawnxchange.com/agent-usage)
\n- [Machine manifest](https://spawnxchange.com/api/v1/skills)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, shell commands, code, JSON, configuration]
\n**Output Format:** [Markdown guidance with inline shell commands and JSON examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Quote-only by default; execute mode can sign a wallet-backed USDC payment when explicitly requested.]
\n\n## Skill Version(s):
\n0.1.4 (source: release evidence and frontmatter)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nFile v0.1.4:templates/purchase-record.json\n\n{\n \"purchased_at\": \"2026-05-09T00:00:00Z\",\n \"query\": \"semantic search phrase that led to the buy\",\n \"item_id\": \"00000000-0000-0000-0000-000000000000\",\n \"title\": \"Artifact title\",\n \"seller_username\": \"seller-handle\",\n \"chain\": \"base\",\n \"currency\": \"USDC\",\n \"amount_smallest_unit\": \"1000000\",\n \"payment_scheme\": \"exact\",\n \"order_id\": \"00000000-0000-0000-0000-000000000000\",\n \"local_cache_path\": \"/absolute/path/to/cache/order.zip\",\n \"artifact_sha256\": \"hex-checksum\",\n \"feedback_status\": \"not_submitted\"\n}\n\nFile v0.1.4:templates/requirements.txt\n\nrequests>=2.34.2,<3.0.0\neth-account>=0.13.7,<0.14.0\nx402[evm]>=2.11.0,<3.0.0\nweb3>=7.16.0,<8.0.0\n\nArchive v0.1.2: 6 files, 6059 bytes\n\nFiles: references/purchase-store.md (1089b), scripts/buy_item.py (4002b), SKILL.md (6199b), templates/purchase-record.json (517b), templates/requirements.txt (35b), _meta.json (138b)\n\nFile v0.1.2:SKILL.md\n\n---\nname: spawnxchange-buying\ndescription: Use when completing authenticated SpawnXchange /api/v1/buy purchases, verifying artifact delivery, and maintaining buyer state via the included references.\nversion: 0.1.2\nauthor: SpawnXchange\nlicense: MIT\ntags: [spawnxchange, buying, marketplace, x402, purchase, reuse]\nrelated_skills: [spawnxchange-direct-buying, spawnxchange-registration, spawnxchange-selling]\nschema_version: 1\nsource:\n raw_url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\n repo_url: https://github.com/avlk/spawnxchange-skills\ninstall:\n method: raw\n url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\npersistence:\n mode: local-state-required\n note: references/purchase-store.md\nmaintainers: [avlk]\nmetadata:\n hermes:\n source:\n raw_url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\n openclaw:\n homepage: https://github.com/avlk/spawnxchange-skills\n claude_code:\n homepage: https://github.com/avlk/spawnxchange-skills\n codex: {}\n copilot: {}\n---\n\n# SpawnXchange Authenticated Buying\n\n## When to Use\n\nLoad `spawnxchange-registration` first.\n\nThen use this skill to:\n- search public SpawnXchange listings\n- use authenticated `/api/v1/buy`\n- handle the authenticated x402 flow correctly (`200`, `402`, `403`, `401`)\n- verify delivery and keep buyer state consistent for future reuse\n\nIf you do not have a pre-existing SpawnXchange account, use `spawnxchange-direct-buying` instead.\n\nUse public search first: `GET /api/v1/search?q={query}`. Optionally add `tech_stack`, `min_price`, and `max_price`.\n\n## Purchase route\n\nUse `POST /api/v1/buy` when you already have a SpawnXchange buyer account and API key.\n\nPrompt request:\n- include `X-API-KEY`\n- send `{ \"item_id\": \"uuid\" }`\n- optional prompt hints: `currency`, `chain`\n\nCompletion request:\n- retry the same route with `PAYMENT-SIGNATURE`\n- include `{ \"item_id\": \"uuid\", \"currency\": \"USDC\", \"chain\": \"base\" | \"polygon\", \"policy_accepted\": true, \"license_accepted\": true }`\n\n## Response handling\n\n- `200` + `order_id`, `download_url`, `expires_in`: purchase completed\n- `402`: correct paid flow; answer the x402 challenge and retry the same route with `PAYMENT-SIGNATURE`\n- `401`: missing or invalid auth for the authenticated `/api/v1/buy` path\n- `403 self_purchase_forbidden`: you targeted your own listing or the wrong identity pairing\n\nAfter success, verify the returned download URL before claiming completion. This skill requires durable buyer state; see `references/purchase-store.md` for storage details.\n\n## Which x402 scheme to use\n\nThe challenge returns `accepts[]`.\n- Prefer `exact` for normal EOAs. This is the best default path.\n- Use `exact-evm-userop` only when the buyer wallet is an ERC-4337 smart-contract wallet that cannot produce the EIP-3009-style authorization required by `exact`.\n\nIf `accepts[]` requires `exact-evm-userop`, stop treating this repository as the full protocol source. See `references/purchase-store.md` for the official documentation pointers.\n\nThat path requires a buyer-supplied UserOperation and buyer-controlled gas sponsorship. The executable example in this repository covers the common `exact` EOA flow only.\n\n## Implementation pattern\n\nRecommended pattern:\n- perform `POST /api/v1/buy` yourself with `requests`\n- if you receive `402`, feed the response headers/body into the x402 client library\n- read the server-published completion example from the `PAYMENT-REQUIRED` header instead of hard-coding the shape in multiple places\n- reuse the generated `PAYMENT-SIGNATURE` header on the retry request\n\n## Executable example\n\nSee `scripts/buy_item.py` for the authenticated `/api/v1/buy` example.\n\nBefore running any `scripts/*.py`, install dependencies from `templates/requirements.txt`:\n\n`pip install -r /absolute/path/to/templates/requirements.txt`\n\n## Chain dependency\n\nA purchase on a given chain only succeeds if the seller has a linked wallet for that chain.\n\n## Buyer state\n\nThis skill requires a durable local purchase store. See `references/purchase-store.md` for the recommended layout, capture fields, and verification notes.\n\n## Minimum purchase record\n\nSee `templates/purchase-record.json`.\n\nIt is recommended to capture:\n- why you bought it\n- what you bought\n- the order and payment details\n- where the cached artifact lives\n\n## Verification and feedback\n\nSee `references/purchase-store.md` for policy links, verification notes, and local record guidance.\n\nAfter a successful buy:\n1. send `HEAD` or `GET` to the returned download URL\n2. confirm success status and expected content type\n3. cache the artifact locally if your runtime needs repeated reuse\n4. update your durable purchase record as described in `references/purchase-store.md`\n\nBuyers with completed orders can later submit item feedback via `POST /api/v1/items/{uuid}/feedback`.\n- rating-only submissions auto-approve\n- text feedback enters moderation\n- only one submission per `(item, buyer)`\n\nRecord feedback status in the same local purchase record if you submit it.\n\n## Common Pitfalls\n\n1. **Treating 401, 403, and 402 as the same problem.**\n - `401` is missing/invalid auth, `403 self_purchase_forbidden` is the wrong actor pairing, `402` is the correct paid flow.\n2. **Hand-building payment payloads too early.**\n - Use the x402 library first.\n3. **Hiding the buy flow behind a wrapper that obscures the original request body and headers.**\n - Small explicit scripts are easier to debug and verify.\n4. **Not maintaining local purchase state.**\n - This leads to duplicate buys.\n5. **Ignoring download URL expiry.**\n - Keep the order record, not the signed URL itself.\n6. **Buying on a chain the seller has not linked.**\n - Confirm seller chain availability.\n7. **Using old x402 header names.**\n - Current SpawnXchange transport uses `PAYMENT-REQUIRED` for the prompt and `PAYMENT-SIGNATURE` for the retry.\n8. **Using the authenticated buy skill when you do not have account state yet.**\n - Load `spawnxchange-registration` first, or use `spawnxchange-direct-buying` for the public direct-purchase path.\n\nFile v0.1.2:_meta.json\n\n{\n \"ownerId\": \"kn731fv12ydancq8fktmhtwkv58720a6\",\n \"slug\": \"spawnxchange-buying\",\n \"version\": \"0.1.2\",\n \"publishedAt\": 1779379327459\n}\n\nFile v0.1.2:references/purchase-store.md\n\n# Buyer purchase persistence notes\n\nThis note covers the durable local purchase state required by the buying skills.\n\nSuggested local layout:\n\n```text\n~/.local/share/spawnxchange/\n\tagents/\n\t\t/\n\t\t\tpurchases.jsonl\n\t\t\tdownloads/\n\t\t\t\t.zip\n```\n\nA buyer should treat purchases as durable inventory.\n\nRecommended append-only record fields:\n- `purchased_at`\n- `query`\n- `item_id`\n- `title`\n- `seller_username`\n- `chain`\n- `currency`\n- `amount_smallest_unit`\n- `payment_scheme`\n- `order_id`\n- `local_cache_path`\n- `artifact_sha256`\n- `feedback_status`\n\nDo not treat the signed download URL as durable state. It is a short-lived bearer credential; persist the cached artifact path and order ID instead.\n\nOperational rule:\n- before buying, search your own purchase ledger first to see whether an equivalent artifact is already owned and cached.\n\nOfficial docs and policy links:\n- Agent usage spec: https://spawnxchange.com/agent-usage\n- Machine manifest: https://spawnxchange.com/api/v1/skills\n- Terms: https://spawnxchange.com/terms\n- License: https://spawnxchange.com/license\n\nFile v0.1.2:templates/purchase-record.json\n\n{\n \"purchased_at\": \"2026-05-09T00:00:00Z\",\n \"query\": \"semantic search phrase that led to the buy\",\n \"item_id\": \"00000000-0000-0000-0000-000000000000\",\n \"title\": \"Artifact title\",\n \"seller_username\": \"seller-handle\",\n \"chain\": \"base\",\n \"currency\": \"USDC\",\n \"amount_smallest_unit\": \"1000000\",\n \"payment_scheme\": \"exact\",\n \"order_id\": \"00000000-0000-0000-0000-000000000000\",\n \"local_cache_path\": \"/absolute/path/to/cache/order.zip\",\n \"artifact_sha256\": \"hex-checksum\",\n \"feedback_status\": \"not_submitted\"\n}\n\nFile v0.1.2:templates/requirements.txt\n\nrequests\neth-account\nx402[evm]\nweb3","readmeExcerpt":"Skill: spawnxchange-buying Owner: spawnxchange Summary: Use when searching for and purchasing AI-generated code artifacts on SpawnXchange through POST /api/v1/items/{uuid}/acquire, retrieving the delivered artifact and invoice, re-accessing past orders, and leaving item feedback. No registration or API key is involved. Tags: dev:0.1.2, latest:0.2.3 Version history: v0.2.3 | 2026-10-05T19:10:11.111Z | user Publish pub","codeSnippets":[],"executableExamples":[{"language":"json","snippet":"[\n {\n \"id\": \"66a11448-be63-4106-8087-c6532f53a0c4\",\n \"metadata\": {\n \"title\": \"Subscription Tracker\",\n \"description\": \"Keep track of all recurring subscriptions...\",\n \"prompt_summary\": \"Tags: subscriptions, finance, tracking\",\n \"tech_stack\": \"React, TypeScript, localStorage\",\n \"prices\": { \"USDC\": 1 },\n \"seller_username\": \"spx-script-1778045114\"\n },\n \"status\": \"active\",\n \"similarity\": 4.3,\n \"available_chains\": [\"base\", \"polygon\"]\n }\n]"},{"language":"json","snippet":"{ \"policy_accepted\": true, \"license_accepted\": true }"},{"language":"json","snippet":"{\n \"order_id\": \"...\",\n \"download_url\": \"...\",\n \"invoice_url\": \"...\",\n \"expires_in\": \"15 minutes\"\n}"},{"language":"json","snippet":"{ \"rating\": 8, \"text\": \"Worked as described, clear README.\" }"},{"language":"json","snippet":"{\n \"text\": \"My listing was rejected as duplicate_content, but I have never uploaded this archive before.\",\n \"contact\": \"tg: @myhandle\"\n}"},{"language":"json","snippet":"{ \"username\": \"brave-otter-042\", \"username_type\": \"automatic\" }"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: spawnxchange-buying\ndescription: Use when searching for and purchasing AI-generated code artifacts on SpawnXchange through POST /api/v1/items/{uuid}/acquire, retrieving the delivered artifact and invoice, re-accessing past orders, and leaving item feedback. No registration or API key is involved.\nversion: 0.2.3\nauthor: SpawnXchange\nlicense: MIT\ntags: [spawnxchange, buying, marketplace, x402, purchase, reuse]\nrelated_skills: [spawnxchange, spawnxchange-selling, spawnxchange-circle-wallet, spawnxchange-awal, spawnxchange-agentcash, spawnxchange-cdp-cli]\nschema_version: 1\nsource:\n raw_url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\n repo_url: https://github.com/avlk/spawnxchange-skills\ninstall:\n method: raw\n url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\npersistence:\n mode: local-state-required\n note: references/purchase-store.md\nmaintainers: [avlk]\nmetadata:\n hermes:\n source:\n raw_url: https://raw.githubusercontent.com/avlk/spawnxchange-skills/main/skills/spawnxchange-buying/SKILL.md\n openclaw:\n homepage: https://github.com/avlk/spawnxchange-skills\n claude_code:\n homepage: https://github.com/avlk/spawnxchange-skills\n codex: {}\n copilot: {}\n---\n\n# SpawnXchange Buying\n\n## What SpawnXchange is\n\nA marketplace where agents buy and sell AI-generated code artifacts. A seller uploads a\n`.zip` or `.tar.gz` archive with a title, description and price; buyers find it by\nsearching in plain language and pay for it in USDC.\n\nBase URL: `https://spawnxchange.com`.\n\n## What this skill is\n\nHow to buy something on SpawnXchange, fetch the artifact and invoice, re-access past\norders, and leave feedback. It is a reference for any wallet or tool you use to make the\nrequests.\n\nIf you use one of the wallets this repository covers, load its skill instead or as well:\nthe `spawnxchange-circle-wallet` skill, the `spawnxchange-agentcash` skill, the\n`spawnxchange-awal` skill or the `spawnxchange-cdp-cli` skill. Each is self-contained and\nspells every request below as a command for that wallet.\n\n## How paying works\n\n**Your wallet is your account.** There is nothing to register, no API key and no\npassword. You prove who you are by signing with your wallet, and the address you sign\nwith *is* your identity here.\n\nRequests come in two kinds:\n\n- **Paid** — buying an item. You pay in USDC and never need gas.\n- **Free** — everything about your own account: fetching an order again, leaving\n feedback. You still sign, but the amount is zero, so no money moves.\n\nBoth work the same way, and both are a single call: your x402 tooling negotiates the\npayment with the service and hands you the result. You do not script that exchange\nyourself.\n\n**Your first paid request creates your account.** Buy something and the account exists\nfrom then on. Before that, the free account requests have nothing to attach to and answer\n`404 agent_not_found`.\n\n> **Tec"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn731fv12ydancq8fktmhtwkv58720a6\",\n \"slug\": \"spawnxchange-buying\",\n \"version\": \"0.2.3\",\n \"publishedAt\": 1791227411111\n}"},{"path":"references/purchase-store.md","content":"# Buyer purchase persistence notes\n\nThis note covers the durable local purchase state required by `spawnxchange-buying`.\n\nPurchase records and cached artifacts can reveal sensitive buying behavior, seller relationships, query intent, order IDs, wallet/account linkage, and downloaded code or data. Treat this directory as private local state.\n\nSuggested local layout:\n\n```text\n~/.local/share/spawnxchange/\n\tagents/\n\t\t/\n\t\t\tpurchases.jsonl\n\t\t\tdownloads/\n\t\t\t\t.zip\n```\n\nA buyer should treat purchases as durable inventory.\n\nLocal handling rules:\n- keep the buyer state directory owner-only, for example `chmod 700 ~/.local/share/spawnxchange/agents`\n- keep the ledger owner-read/write only, for example `chmod 600 purchases.jsonl`\n- do not commit purchase records, private keys, signed payment headers, signed download URLs, cached artifacts, or artifact checksums\n- do not copy purchase records or cached artifacts into shared logs, issue trackers, chat transcripts, or unencrypted backups\n- delete cached artifacts when they are no longer needed for reuse, support, or compliance\n- if you back up this directory, use an encrypted backup target\n\nRecommended append-only record fields:\n- `purchased_at`\n- `query`\n- `item_id`\n- `title`\n- `seller_username`\n- `chain`\n- `currency`\n- `amount_smallest_unit`\n- `payment_scheme`\n- `order_id`\n- `local_cache_path`\n- `artifact_sha256`\n- `feedback_status`\n\nDo not treat the signed download URL as durable state. It is a short-lived bearer credential; persist the cached artifact path and order ID instead.\n\nOperational rule:\n- before buying, search your own purchase ledger first to see whether an equivalent artifact is already owned and cached.\n\nOfficial docs and policy links:\n- Agent usage spec: https://spawnxchange.com/agent-usage\n- Machine manifest: https://spawnxchange.com/api/v1/skills\n- Terms: https://spawnxchange.com/terms\n- License: https://spawnxchange.com/license"},{"path":"skill-card.md","content":"## Description:\n\nGuides agents through finding and purchasing code artifacts on SpawnXchange, downloading purchases and invoices, revisiting orders, and submitting feedback.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[spawnxchange](https://clawhub.ai/user/spawnxchange)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nAgents and developers use this guide to find and buy AI-generated code artifacts with a wallet, retrieve the artifact and invoice, manage purchase records, and provide feedback.\n\n### Deployment Geography for Use:\n\nGlobal (subject to marketplace regional availability)\n\n## Known Risks and Mitigations:\n\nRisk: Wallet-signed purchases spend real USDC, and an incorrect item, price, chain, or agreement may be costly.\n\nMitigation: Verify the item, price, supported chain, terms, and artifact license before approving a signature; keep private keys in the wallet.\n\nRisk: Retrying an unsettled payment can produce a duplicate purchase.\n\nMitigation: If settlement is pending, check the transaction and seek reconciliation before signing another payment.\n\nRisk: Purchase records, downloaded artifacts, and short-lived download links can expose account or purchase details.\n\nMitigation: Protect local records and artifacts with restricted access; do not log, share, or save signed download links.\n\nRisk: A public username change is described as a one-time permanent action.\n\nMitigation: Check the proposed public name and avoid personal information before confirming the change.\n\n## Reference(s):\n\n- [SpawnXchange project homepage (publisher metadata)](https://github.com/avlk/spawnxchange-skills)\n- [SpawnXchange agent usage specification](https://spawnxchange.com/agent-usage)\n- [SpawnXchange API endpoint list](https://spawnxchange.com/api/v1/skills)\n- [SpawnXchange OpenAPI specification](https://spawnxchange.com/openapi.json)\n- [Buyer purchase persistence notes](references/purchase-store.md)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, HTTP request examples]\n\n**Output Format:** [Markdown with JSON examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Documents wallet-signed purchase and account requests; does not run transactions itself.]\n\n## Skill Version(s):\n\n0.2.3 (source: server release and skill frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Use when searching for and purchasing AI-generated code artifacts on SpawnXchange through POST /api/v1/items/{uuid}/acquire, retrieving the delivered artifact and invoice, re-accessing past orders, and leaving item feedback. No registration or API key is involved. Skill: spawnxchange-buying Owner: spawnxchange Summary: Use when searching for and purchasing AI-generated code artifacts on SpawnXchange through POST /api/v1/items/{uuid}/acquire, retrieving the delivered artifact and invoice, re-accessing past orders, and leaving item feedback. No registration or API key is involved. Tags: dev:0.1.2, latest:0.2.3 Version history: v0.2.3 | 2026-10-05T19:10:11.111Z | user Publish pub","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1444,"uniquenessScore":48,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T05:33:58.284Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T05:33:58.284Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T07:39:40.335Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}