Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Publish and manage Apiosk gateway listings with signed wallet authentication, listing-group aware categorization, and update/delete operations.
Publish and manage Apiosk gateway listings with signed wallet authentication, listing-group aware categorization, and update/delete operations.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Use this skill for API publishing and lifecycle management on https://gateway.apiosk.com.
You need to register a new paid API on Apiosk. You need to update, list, or deactivate your published API. You need to map an API to the latest listing groups (api, datasets, compute). You need to send correctly signed wallet-auth headers for management endpoints.
curl jq cast (Foundry) Wallet: ~/.apiosk/wallet.json (preferred, includes address + private_key) or APIOSK_PRIVATE_KEY env var or --private-key flag
POST /v1/apis/register GET /v1/apis/mine?wallet=0x... POST /v1/apis/:slug DELETE /v1/apis/:slug?wallet=0x...
All management calls require: x-wallet-address x-wallet-signature x-wallet-timestamp x-wallet-nonce Canonical message to sign: Apiosk auth action:<action> wallet:<lowercase_wallet> resource:<resource> timestamp:<unix_seconds> nonce:<nonce> Action/resource mapping: register: action=register_api, resource=register:<slug> update: action=update_api, resource=update:<slug> mine: action=my_apis, resource=mine:<wallet> delete: action=delete_api, resource=delete:<slug>
Discovery groups in gateway: api datasets compute Register payload currently uses category (not explicit listing_type). Use this mapping: api -> data datasets -> dataset compute -> compute
POST /v1/apis/register: { "name": "My API", "slug": "my-api", "endpoint_url": "https://example.com", "price_usd": 0.01, "description": "My paid API", "owner_wallet": "0x...", "category": "dataset" }
Always sign management requests; unsigned calls should be treated as invalid. Keep wallet value lowercased inside the signed message, even if header uses checksum case. If Unauthorized, regenerate timestamp + nonce and re-sign once. Validate HTTPS endpoint before register/update. Use listing-group mapping above so new listings appear in the right discovery surfaces.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.