apiosk-publish

Use this skill for API publishing and lifecycle management on https://gateway.apiosk.com.

When to use

• - 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.

Required tools and files

• - INLINECODE4
• INLINECODE5
• INLINECODE6 (Foundry)
• Wallet:

Management endpoints

• - INLINECODE12
• INLINECODE13
• INLINECODE14
• INLINECODE15

Signed wallet auth

All management calls require:

• - INLINECODE16
• INLINECODE17
• INLINECODE18
• INLINECODE19

Canonical message to sign:

CODEBLOCK0

Action/resource mapping:

• - register: action=register_api, INLINECODE21
• update: action=update_api, INLINECODE23
• mine: action=my_apis, INLINECODE25
• delete: action=delete_api, INLINECODE27

Listing groups and categories

Discovery groups in gateway:

• - INLINECODE28
• INLINECODE29
• INLINECODE30

Register payload currently uses category (not explicit listing_type).
Use this mapping:

• - api -> INLINECODE34
• INLINECODE35 -> INLINECODE36
• INLINECODE37 -> INLINECODE38

Register payload

INLINECODE39:

CODEBLOCK1

Agent behavior requirements

• - 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.