Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(skills): document the OpenAPI/repo skill importer and changelog it
nirholas7c28d186c47b
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 4778907fa..673097988 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -16,6 +16,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Agent-to-agent hires now carry a signed fulfillment record, and it feeds reputation and pricing**: Every settled a2a-hire (api/agents/a2a-hire.js) now writes exactly one signed attestation row: {hire_id, payment_signature, outcome, evidence_hash, signed_by}, outcome one of delivered, failed, or disputed, signed off-chain with the same platform attestation key api/_lib/attest-event.js uses for on-chain provenance memos. A client-side timeout is recorded as disputed, never inferred as delivered, since x402's verify-then-settle means the provider may already have been paid server-side. The resulting recency-weighted fulfillment rate (30-day half-life, minimum 5 attestations before it counts) is now a real input to the free Financial reputation score on every agent's Trust tab: the Settlement reliability pillar's detail line reports the rate alongside its sample size, for example '90% hire fulfillment over 12 hires', or how many hires are attested so far if the minimum has not been met yet. Providers can also opt a service into an optional x402 pricing discount for well-reputed hirers (agent_paid_services.reputation_discount_enabled, off by default): the hiring agent's reputation tier mints a short-lived, slug-scoped, signature-verified voucher, never a caller-supplied claim, so the paywall always fails closed to full price on anything unsigned, expired, or mis-scoped. (`/agents`) `[feature, security]`- **Payment sessions gain blocked hosts, an approval threshold, and a per-rail daily cap, all with tamper-evident verdicts**: Agent payment sessions get three new governance knobs, settable at creation and editable while a session is active: blocked_hosts (a denylist checked after the allowlist, so an explicit block always wins over a broad allow, even with no allowlist set), approval_threshold_usd (a call priced above this amount now gets a distinct requires_approval verdict instead of either settling or silently failing), and per_rail_daily_usd (a rolling 24h spend cap per settlement network, reserved atomically the same way the session budget already is, closing the race a naive sum-of-past-executions check would leave open). Every governance verdict, allow or reject, now carries a policy_digest (a sha256 hash of the exact policy it was judged against) and an HMAC signature over the verdict, digest, request, and timestamp, stored with the execution: editing a session's policy after the fact changes the digest and breaks the signature on every verdict that preceded the edit, so a verdict record can be trusted even after the policy it was judged against has since moved. The dry-run simulator at /api/pay/simulate now predicts all three new rules through the exact same shared policy module the real enforcer calls, so a simulated verdict and an enforced one can never disagree; that parity is pinned by a new test running both over identical scenarios. The payments page gained matching fields in both the session creation and edit modals, with inline validation and a collapsed 'Advanced spend policy' section so the common case (budget, expiry, host allowlist) stays uncluttered. (`/docs/payment-sessions`) `[feature, security]`- **Receipt Vault gains an Outbound tab: what your agents spent elsewhere, verified against the chain itself**: The Receipt Vault at /receipts now has two tabs. Inbound is unchanged (what three.ws billed your wallet); the new Outbound tab answers the other question: what did your agents spend at OTHER x402 merchants while running on an Agent Payment Session. Each settled Solana execution is resolved against the settlement transaction's own token-balance change the first time anyone views it (payer, payee, mint, amount, fee, slot, time), independent of whatever the merchant's response claimed, then cached so later views are free; a 'verified' badge marks a row that matched the chain, 'pending' while resolution is still in flight, and 'unverified' if the lookup failed permanently. The tab is account-session gated (the same credential /payments uses, not a wallet signature, since Payment Sessions are account-scoped, not wallet-scoped), filters by network and merchant host, and exports to CSV alongside the existing JSON receipt downloads. New endpoint: GET /api/x402/outbound-receipts. (`/receipts`) `[feature]`+- **Turn any public OpenAPI spec or GitHub repo into a draft agent skill**: New importer at /skills/import (From an API tab) and POST /api/skills/import: point at an OpenAPI/Swagger URL or a GitHub repo and every operation becomes a tools.json entry with a generated handlers.js function calling ctx.fetch, SKILL.md prose written from the spec's own descriptions, and Swagger 2.0 upgraded to OpenAPI 3 automatically. A README-only repo becomes a declarative skill instead, prose only, no tools. Every import lands as a disabled draft, owner-scoped and labelled untrusted: enabled only ever flips via the dedicated PATCH /api/skills/import/:id route, never at creation, and nothing is installed onto any agent automatically. Generated handlers fill auth from the skill's declared secrets, never a hardcoded credential. Also available from the CLI: three-ws skills import <url> and three-ws skills drafts. New package: @three-ws/skill-import. (`/skills/import`) `[feature]`## 2026-10-14diff --git a/STRUCTURE.md b/STRUCTURE.mdindex d9f1533f2..0ea1694fd 100644--- a/STRUCTURE.md+++ b/STRUCTURE.md@@ -123,6 +123,7 @@ packages, a generated standalone GitHub mirror). See| Agent payment sessions (`/payments`) | [pages/payments.html](pages/payments.html) `-> /payments`, API [api/pay/session.js](api/pay/session.js) (`POST`/`GET`/`PATCH`/`DELETE /api/pay/session`, `GET /api/pay/session/:id/executions`), spend rail [api/pay/execute.js](api/pay/execute.js) + [api/pay/simulate.js](api/pay/simulate.js), engine [api/_lib/pay/payment-session.js](api/_lib/pay/payment-session.js) + governor [api/_lib/pay/spend-governor.js](api/_lib/pay/spend-governor.js), expiry sweep [api/cron/payment-session-sweep.js](api/cron/payment-session-sweep.js) | Live | The dashboard for platform-managed spend envelopes: fund a budget out of `/credits`, get a one-time `pss_` bearer token, and hand it to an agent that pays x402 endpoints without ever holding a private key (the platform's Solana wallet signs, and the governor enforces budget, host allowlist and per-tx cap atomically on every call). Each card carries the budget bar, remaining balance, expiry countdown, host allowlist, per-tx cap, an inline execution ledger from `GET /api/pay/session/:id/executions` with a Solscan link per settled payment, an env-var-referencing MCP config for [packages/agentcore-payments-mcp](packages/agentcore-payments-mcp), and cancel-and-refund. Press `N` for the create dialog. Docs: [docs/payment-sessions.md](docs/payment-sessions.md), [docs/tutorials/agent-spending-envelope.md](docs/tutorials/agent-spending-envelope.md). Tests: [tests/payment-session-governor.test.js](tests/payment-session-governor.test.js), [tests/payment-session-sweep.test.js](tests/payment-session-sweep.test.js) || Skill bundles (seller builder + evidence pricing) | [pages/bundles.html](pages/bundles.html) `→ /bundles`, API [api/agents/[id]/bundles.js](api/agents/%5Bid%5D/bundles.js), arithmetic [api/_lib/bundle-pricing.js](api/_lib/bundle-pricing.js), checkout [api/marketplace/purchase-bundle.js](api/marketplace/purchase-bundle.js) | Live (seller side); no buyer-facing browser view yet | Sell several of one agent's skills as one purchase. The price is derived from the agent's own ledger rather than a rule of thumb: the public `?action=pricing` endpoint finds every buyer who already bought 2+ of the selected skills, suggests the median of what they really paid (`basis: median_basket`), and backtests any candidate price against those same baskets; with no such buyer yet it falls back to 20% off the sum of the parts and labels itself `discount_off_list` so a default is never read as a finding. Every amount is an atomic integer carried as a BigInt end to end, because a 9-decimal mint puts real sums past `Number.MAX_SAFE_INTEGER`. Checkout settles on-chain and writes one `skill_purchases` row per skill (`kind = 'bundle'`, amount 0) so one bundle sale is never counted as N skill sales. Docs: [docs/skill-bundles.md](docs/skill-bundles.md). Tests: [tests/bundle-pricing.test.js](tests/bundle-pricing.test.js), [tests/vercel-agents-subpath-routes.test.js](tests/vercel-agents-subpath-routes.test.js) || External skill import (browse, scan, approve, fork, publish) | [pages/skills-import.html](pages/skills-import.html) `→ /skills/import` + [src/skills-import.js](src/skills-import.js), REST [api/skill-imports.js](api/skill-imports.js) `→ /api/skill-imports/*`, registries and pinning [api/_lib/skill-import-sources.js](api/_lib/skill-import-sources.js), scanner [api/_lib/skill-import-scan.js](api/_lib/skill-import-scan.js), store [api/_lib/skill-import-store.js](api/_lib/skill-import-store.js), chat spend gate [api/_lib/skill-import-gate.js](api/_lib/skill-import-gate.js), MCP [api/_mcp/tools/skill-imports.js](api/_mcp/tools/skill-imports.js), migration [api/_lib/migrations/20261011013000_skill_imports.sql](api/_lib/migrations/20261011013000_skill_imports.sql) | Live | Installs `SKILL.md` skills from any public GitHub repository or registry manifest (built in: the three.ws community repo, the public Anthropic agent skills repo, and skills published on three.ws). Each skill is pinned to its commit or sha256, licence-checked, scanned, and installed only after the owner approves; skills that ask to spend, sign or message are gated. Updates arrive as a diff the owner approves. Docs [docs/skill-import.md](docs/skill-import.md), manifest spec [specs/SKILL_REGISTRY_MANIFEST.md](specs/SKILL_REGISTRY_MANIFEST.md), live check [scripts/skill-import-live-check.mjs](scripts/skill-import-live-check.mjs). |+| Skill import from an OpenAPI spec or GitHub repo | Package [packages/skill-import/](packages/skill-import/README.md) (parser, operation classifier, handler/manifest/SKILL.md generators), REST [api/skills/import.js](api/skills/import.js) `→ POST/GET /api/skills/import`, [api/skills/import/[id].js](api/skills/import/%5Bid%5D.js) `→ GET/PATCH/DELETE` (enable/disable/delete, owner-scoped), bundle host [api/skills/import/[id]/[...file].js](api/skills/import/%5Bid%5D/%5B...file%5D.js), store [api/_lib/openapi-skill-imports.js](api/_lib/openapi-skill-imports.js), migration [api/_lib/migrations/20261015130000_openapi_skill_imports.sql](api/_lib/migrations/20261015130000_openapi_skill_imports.sql), UI tab "From an API" in [pages/skills-import.html](pages/skills-import.html) `→ /skills/import` + [src/skills-import.js](src/skills-import.js), CLI `three-ws skills import <url>` / `three-ws skills drafts` in [packages/three-ws-cli/src/commands/skills.js](packages/three-ws-cli/src/commands/skills.js) | Live | Point at any public OpenAPI/Swagger URL or GitHub repo and get a generated skill bundle: every operation becomes a `tools.json` entry and a `handlers.js` function that calls `ctx.fetch`, with auth placeholders filled from the skill's declared secrets, never hardcoded. A README-only repo becomes a declarative skill instead. Every import lands as a disabled draft, owner-scoped and labelled untrusted; `enabled` only ever flips via the dedicated `PATCH` route, never at creation. Docs: [docs/skills.md](docs/skills.md#importing-a-skill-from-an-openapi-spec-or-a-github-repo). Tests: [packages/skill-import/tests/](packages/skill-import/tests), [tests/openapi-skill-import.test.js](tests/openapi-skill-import.test.js), [packages/three-ws-cli/tests/skills.test.js](packages/three-ws-cli/tests/skills.test.js) || Marketplace analytics & trial funnel | [pages/marketplace-analytics.html](pages/marketplace-analytics.html) `→ /marketplace/analytics`, renderer [src/marketplace-analytics.js](src/marketplace-analytics.js), backend [api/marketplace/analytics.js](api/marketplace/analytics.js) | Live | Public transparency page for the skill marketplace: paid sales, volume, top skills/agents, and the trial conversion funnel. **Every money aggregate gates on `status = 'confirmed'` alone.** Counting `status IN ('confirmed','trial')` as a sale published 10,454 "sales" and 6.2M $THREE of "volume" on 2026-07-30 against a table holding zero confirmed purchases, because a `trial` row is a free grant whose `amount` is only the list price it would have cost. Free trials now render as their own stat and as a four-stage funnel (granted → used → exhausted → converted), which also names the two shapes that mean a wiring fault rather than weak demand: trials never spent, or trials exhausted with nothing converting. Docs: [docs/marketplace.md](docs/marketplace.md), tutorial [docs/tutorials/sell-a-skill-with-a-trial.md](docs/tutorials/sell-a-skill-with-a-trial.md). Tests: [tests/marketplace-analytics-paid-only.test.js](tests/marketplace-analytics-paid-only.test.js) || OKX.AI marketplace services | [api/okx/3d/[service].js](api/okx/3d/%5Bservice%5D.js) `→ /api/okx/3d/*` | Live | 3D services sold to other agents on OKX.AI (agent #2632). The **listed** line-up (rebuilt 2026-08-22) is **three.ws Forge**: four paid A2MCP rows (`forge-draft` $0.01 / `forge-standard` $0.05 / `forge-hd` $0.25 / `forge-image` $0.25) plus a free `forge-status` poll, tools in [api/_okx3d/forge.js](api/_okx3d/forge.js). Each row is a real MCP Streamable HTTP server whose paid `forge_3d` tool 402s with `eip155:196` leading; the buyer receives exactly what the ChatGPT custom GPT receives (GLB + concept image + viewer + AR link), because both fronts shape responses through [api/_mcp-studio/studio-shape.js](api/_mcp-studio/studio-shape.js). Agent Identity Studio and the single-capability REST endpoints are on the **back burner**: `listed: false` keeps them out of the listing and the submission payload while they stay deployed and payable. Catalog source of truth: [api/_lib/okx-catalog.js](api/_lib/okx-catalog.js); pipeline: [api/_okx3d/](api/_okx3d); showcase: [pages/agent-identities.html](pages/agent-identities.html) `→ /agent-identities` + [src/agent-identities.js](src/agent-identities.js), fed at runtime by [api/agent-identities.js](api/agent-identities.js) `→ /api/agent-identities` (demo runs from `data/agent-identities.json` merged with the live catalog row, so the price the page quotes is the price the paid endpoint charges); docs: [docs/okx-marketplace.md](docs/okx-marketplace.md), [docs/agent-identities.md](docs/agent-identities.md). Tests: [tests/api/okx-forge.test.js](tests/api/okx-forge.test.js) || OKX.AI marketplace chat bot host | [workers/okx-chat-bot/](workers/okx-chat-bot) (Cloud Run service `okx-chat-bot`), local revive [scripts/okx-bot-revive.mjs](scripts/okx-bot-revive.mjs) `→ npm run okx:bot`, session seeding [scripts/okx-bot-seed-state.mjs](scripts/okx-bot-seed-state.mjs) `→ npm run okx:bot:seed-state` | Live · Cloud Run since 2026-09-04, replies blocked on AI funding | Always-on host for the XMTP chat behind agent #2632. Supervises the `okx-a2a` daemon plus the `onchainos` wallet session, persists the wallet/XMTP identity to GCS across revisions, and rebuilds the AI subsession's briefing from [api/_lib/okx-chat-briefing.js](api/_lib/okx-chat-briefing.js) on every boot so quoted prices can never drift from the catalog. It exists because the stack used to live on a codespace that sleeps, and its outage mode is silent: an expired wallet session leaves the process healthy while no chat is delivered, which flagged the listing offline once. Health reaches the platform as the `okx_chat_bot` subsystem on `/api/healthz` via a `bot_heartbeat` row; a logged-out session pages with the exact login commands. The AI credential is probed against the provider rather than assumed present ([workers/okx-chat-bot/provider.js](workers/okx-chat-bot/provider.js)), because a key the provider refuses is indistinguishable from a working one until a buyer's message goes unanswered. The AI credential is an ordered chain rather than one lane (`vertex` on GCP credits, then an Anthropic key, then an Anthropic-wire-format gateway, then an interactive grant, then an OpenAI key): [electProvider()](workers/okx-chat-bot/provider.js) probes every rung on its own env overlay every 15 minutes and serves on the first that answers, so a lane the owner funds is picked up with no deploy and a refused one is never elected. Live state as of 2026-09-09, readable from the `bot_heartbeat` row when `gcloud` is not authenticated: the host has been up since 2026-09-04 with the wallet session logged in and one XMTP client serving, so buyer chat IS delivered, and every lane is refused for lack of funds (Vertex `Lightning dunning decision is deny`, OpenAI `billing_not_active`, OpenRouter `402`), so no reply can be authored. The running revision predates the chain, which its heartbeat meta shows by carrying no `providerLane` / `providerChain` keys. Deploy: [workers/okx-chat-bot/cloudbuild.yaml](workers/okx-chat-bot/cloudbuild.yaml) (`--max-instances=1` is load-bearing, one GCS state writer). Tests: [tests/okx-chat-bot.test.js](tests/okx-chat-bot.test.js) |diff --git a/data/changelog.json b/data/changelog.jsonindex e4d0849d3..52d61fe63 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,25 +1,42 @@{"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security, desktop (desktop entries become the desktop app's release notes). `link` is optional and must be a live three.ws path.","entries": [+ {+ "date": "2026-10-15",+ "title": "Turn any public OpenAPI spec or GitHub repo into a draft agent skill",+ "summary": "New importer at /skills/import (From an API tab) and POST /api/skills/import: point at an OpenAPI/Swagger URL or a GitHub repo and every operation becomes a tools.json entry with a generated handlers.js function calling ctx.fetch, SKILL.md prose written from the spec's own descriptions, and Swagger 2.0 upgraded to OpenAPI 3 automatically. A README-only repo becomes a declarative skill instead, prose only, no tools. Every import lands as a disabled draft, owner-scoped and labelled untrusted: enabled only ever flips via the dedicated PATCH /api/skills/import/:id route, never at creation, and nothing is installed onto any agent automatically. Generated handlers fill auth from the skill's declared secrets, never a hardcoded credential. Also available from the CLI: three-ws skills import <url> and three-ws skills drafts. New package: @three-ws/skill-import.",+ "tags": [+ "feature"+ ],+ "link": "/skills/import"+ },{"date": "2026-10-15","title": "Agent-to-agent hires now carry a signed fulfillment record, and it feeds reputation and pricing","summary": "Every settled a2a-hire (api/agents/a2a-hire.js) now writes exactly one signed attestation row: {hire_id, payment_signature, outcome, evidence_hash, signed_by}, outcome one of delivered, failed, or disputed, signed off-chain with the same platform attestation key api/_lib/attest-event.js uses for on-chain provenance memos. A client-side timeout is recorded as disputed, never inferred as delivered, since x402's verify-then-settle means the provider may already have been paid server-side. The resulting recency-weighted fulfillment rate (30-day half-life, minimum 5 attestations before it counts) is now a real input to the free Financial reputation score on every agent's Trust tab: the Settlement reliability pillar's detail line reports the rate alongside its sample size, for example '90% hire fulfillment over 12 hires', or how many hires are attested so far if the minimum has not been met yet. Providers can also opt a service into an optional x402 pricing discount for well-reputed hirers (agent_paid_services.reputation_discount_enabled, off by default): the hiring agent's reputation tier mints a short-lived, slug-scoped, signature-verified voucher, never a caller-supplied claim, so the paywall always fails closed to full price on anything unsigned, expired, or mis-scoped.",- "tags": ["feature", "security"],+ "tags": [+ "feature",+ "security"+ ],"link": "/agents"},{"date": "2026-10-15","title": "Receipt Vault gains an Outbound tab: what your agents spent elsewhere, verified against the chain itself","summary": "The Receipt Vault at /receipts now has two tabs. Inbound is unchanged (what three.ws billed your wallet); the new Outbound tab answers the other question: what did your agents spend at OTHER x402 merchants while running on an Agent Payment Session. Each settled Solana execution is resolved against the settlement transaction's own token-balance change the first time anyone views it (payer, payee, mint, amount, fee, slot, time), independent of whatever the merchant's response claimed, then cached so later views are free; a 'verified' badge marks a row that matched the chain, 'pending' while resolution is still in flight, and 'unverified' if the lookup failed permanently. The tab is account-session gated (the same credential /payments uses, not a wallet signature, since Payment Sessions are account-scoped, not wallet-scoped), filters by network and merchant host, and exports to CSV alongside the existing JSON receipt downloads. New endpoint: GET /api/x402/outbound-receipts.",- "tags": ["feature"],+ "tags": [+ "feature"+ ],"link": "/receipts"},{"date": "2026-10-15","title": "17 named commerce tools and a spending report land in the x402 MCP buyer, hosted and self-custodial","summary": "The self-custodial x402 buyer (@three-ws/x402-mcp, npx -y @three-ws/x402-mcp) and the hosted agent wallet (https://three.ws/api/mcp-agent) both gained 17 named tools, one per fixed three.ws x402 service: weather_forecast, weather_go_no_go, carbon_now, carbon_best_window, domain_rdap_check, domain_rdap_check_bulk, research_search, research_paper, research_bibliography, book_search, book_read, news_wire_search, news_wire_poll, transit_plan, transit_delays, places_search and places_detail. Each carries a fixed input schema and states its price in its description, so a model calls it correctly far more often than it composes the equivalent raw pay_and_call(url) call. On the hosted side every named tool has a matching <name>_quote read tool that prices it without paying, and the shared tool-policy runtime (@three-ws/mcp-policy) gates payment on that exact quote (one service's quote can never unlock a different service's payment). The stdio package also gained spending_report, which totals everything pay_and_call and the named tools have paid, by merchant and by day, from a local append-only ledger (X402_MCP_LEDGER_PATH).",- "tags": ["feature", "sdk"],+ "tags": [+ "feature",+ "sdk"+ ],"link": "/docs/mcp"},{diff --git a/docs/skills.md b/docs/skills.mdindex ab62cbd6f..ef31b554d 100644--- a/docs/skills.md+++ b/docs/skills.md@@ -704,6 +704,40 @@ For IPFS publishing, the CID of the directory becomes the stable URI. Agents can---+## Importing a skill from an OpenAPI spec or a GitHub repo++Writing a bundle by hand is not the only path. `@three-ws/skill-import` turns a public OpenAPI/Swagger spec URL, or a GitHub repo, directly into a draft bundle: every operation becomes a `tools.json` entry and a generated `handlers.js` function that calls it, `SKILL.md` prose is written from the spec's own descriptions, and Swagger 2.0 specs are upgraded to OpenAPI 3 automatically. A repo whose only content is a README becomes a declarative skill (prose only, no tools), the same shape as a hand-written `SKILL.md`-only bundle.++```bash+curl -s -X POST https://three.ws/api/skills/import \+ -H "authorization: Bearer $THREE_WS_API_KEY" \+ -H "content-type: application/json" \+ -d '{"url": "https://petstore3.swagger.io/api/v3/openapi.json"}' | jq '.data | {id, kind, bundleUri, tools: .manifest.provides.tools}'+```++```json+{+ "id": "a96ddb60-...",+ "kind": "openapi",+ "bundleUri": "/api/skills/import/a96ddb60-.../",+ "tools": ["updatePet", "addPet", "findPetsByStatus", "getPetById", "..."]+}+```++The CLI wraps the same endpoint:++```bash+three-ws skills import https://petstore3.swagger.io/api/v3/openapi.json+three-ws skills import sindresorhus/is-up # owner/repo shorthand also works+three-ws skills drafts # list your generated drafts+```++Every import lands as a **disabled draft, owner-scoped and labelled untrusted**: it is never enabled automatically and never installed onto any agent. `GET /api/skills/import` lists your drafts, `GET /api/skills/import/:id` fetches one, and the generated bundle itself is served at `bundleUri` (`manifest.json`, `SKILL.md`, `tools.json`, `handlers.js`) so you can inspect every generated tool call before trusting it. `PATCH /api/skills/import/:id` with `{ "enabled": true }` is the only way a draft's `enabled` flag ever changes; `DELETE /api/skills/import/:id` removes it. The same flow is available from the UI at [/skills/import](https://three.ws/skills/import), under the **From an API** tab: paste a spec URL or repo, review the generated tool list in the result card, then enable or delete each draft from your drafts list.++Generated handlers call `ctx.fetch` with auth placeholders filled from the skill's declared secrets (an API key header, a bearer token, etc.), never a hardcoded credential, so the skill's eventual owner supplies the real secret at install time, the same as any other skill with a `secrets` declaration in its manifest.++---+## Marketplace skills: install once, applied in every chatAlongside URI-addressed bundles, the platform hosts a community catalog at [/marketplace?tab=skills](https://three.ws/marketplace?tab=skills). A marketplace skill is a database-backed record with a description, category, tags, ratings, and either:diff --git a/public/changelog-recent.json b/public/changelog-recent.jsonindex f6f247770..945d9fed9 100644--- a/public/changelog-recent.json+++ b/public/changelog-recent.json@@ -1,11 +1,11 @@{- "generated_at": "2026-10-15T08:14:33.806Z",+ "generated_at": "2026-10-15T09:19:08.798Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},- "total": 4106,+ "total": 4107,"complete": false,"full_feed": "/changelog.json","entries": [@@ -114,6 +114,16 @@"feature"]},+ {+ "date": "2026-10-15",+ "type": "update",+ "title": "Turn any public OpenAPI spec or GitHub repo into a draft agent skill",+ "summary": "New importer at /skills/import (From an API tab) and POST /api/skills/import: point at an OpenAPI/Swagger URL or a GitHub repo and every operation becomes a tools.json entry with a generated handlers.js function calling ctx.fetch, SKILL.md prose written from the spec's own descriptions, and Swagger 2.0 upgraded to OpenAPI 3 automatically. A README-only repo becomes a declarative skill instead, prose only, no tools. Every import lands as a disabled draft, owner-scoped and labelled untrusted: enabled only ever flips via the dedicated PATCH /api/skills/import/:id route, never at creation, and nothing is installed onto any agent automatically. Generated handlers fill auth from the skill's declared secrets, never a hardcoded credential. Also available from the CLI: three-ws skills import <url> and three-ws skills drafts. New package: @three-ws/skill-import.",+ "link": "/skills/import",+ "tags": [+ "feature"+ ]+ },{"date": "2026-10-14","type": "update",@@ -1550,16 +1560,6 @@"tags": ["launch"]- },- {- "date": "2026-10-10",- "type": "launch",- "title": "Event Markets: call the winner of every three.ws event",- "summary": "Live, closing-soon and resolved markets for every three.ws event. Free-to-play points, crowd-set odds, and shareable cards for each call.",- "link": "/event-markets",- "tags": [- "launch"- ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex 19043ff46..20a7536e8 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-10-15T08:14:33.785Z",+ "generated_at": "2026-10-15T09:19:08.777Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -111,6 +111,16 @@"feature"]},+ {+ "date": "2026-10-15",+ "type": "update",+ "title": "Turn any public OpenAPI spec or GitHub repo into a draft agent skill",+ "summary": "New importer at /skills/import (From an API tab) and POST /api/skills/import: point at an OpenAPI/Swagger URL or a GitHub repo and every operation becomes a tools.json entry with a generated handlers.js function calling ctx.fetch, SKILL.md prose written from the spec's own descriptions, and Swagger 2.0 upgraded to OpenAPI 3 automatically. A README-only repo becomes a declarative skill instead, prose only, no tools. Every import lands as a disabled draft, owner-scoped and labelled untrusted: enabled only ever flips via the dedicated PATCH /api/skills/import/:id route, never at creation, and nothing is installed onto any agent automatically. Generated handlers fill auth from the skill's declared secrets, never a hardcoded credential. Also available from the CLI: three-ws skills import <url> and three-ws skills drafts. New package: @three-ws/skill-import.",+ "link": "/skills/import",+ "tags": [+ "feature"+ ]+ },{"date": "2026-10-14","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 4d69f08e1..7ceb6f781 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -86,6 +86,14 @@<category>feature</category><description>The Receipt Vault at /receipts now has two tabs. Inbound is unchanged (what three.ws billed your wallet); the new Outbound tab answers the other question: what did your agents spend at OTHER x402 merchants while running on an Agent Payment Session. Each settled Solana execution is resolved against the settlement transaction's own token-balance change the first time anyone views it (payer, payee, mint, amount, fee, slot, time), independent of whatever the merchant's response claimed, then cached so later views are free; a 'verified' badge marks a row that matched the chain, 'pending' while resolution is still in flight, and 'unverified' if the lookup failed permanently. The tab is account-session gated (the same credential /payments uses, not a wallet signature, since Payment Sessions are account-scoped, not wallet-scoped), filters by network and merchant host, and exports to CSV alongside the existing JSON receipt downloads. New endpoint: GET /api/x402/outbound-receipts.</description></item>+ <item>+ <title>Turn any public OpenAPI spec or GitHub repo into a draft agent skill</title>+ <link>https://three.ws/skills/import</link>+ <guid isPermaLink="false">2026-10-15:Turn any public OpenAPI spec or GitHub repo into a draft agent skill</guid>+ <pubDate>Thu, 15 Oct 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>New importer at /skills/import (From an API tab) and POST /api/skills/import: point at an OpenAPI/Swagger URL or a GitHub repo and every operation becomes a tools.json entry with a generated handlers.js function calling ctx.fetch, SKILL.md prose written from the spec's own descriptions, and Swagger 2.0 upgraded to OpenAPI 3 automatically. A README-only repo becomes a declarative skill instead, prose only, no tools. Every import lands as a disabled draft, owner-scoped and labelled untrusted: enabled only ever flips via the dedicated PATCH /api/skills/import/:id route, never at creation, and nothing is installed onto any agent automatically. Generated handlers fill auth from the skill's declared secrets, never a hardcoded credential. Also available from the CLI: three-ws skills import <url> and three-ws skills drafts. New package: @three-ws/skill-import.</description>+ </item><item><title>8 keyless live-data services join the x402 paid API: weather, grid carbon, domains, research, books, news, transit, places</title><link>https://three.ws/docs/x402-endpoints</link>diff --git a/public/features.json b/public/features.jsonindex bec17859e..c8723c46a 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-10-15T08:14:33.772Z",+ "generated_at": "2026-10-15T09:19:08.763Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",