Create payout
Starts binding one of the caller org's wallets as the wallet it is paid into: answers a challenge naming the org, the wallet and its address, to be signed with that wallet within fifteen minutes and sent to POST /v1/marketplace/seller/payout/verify.
POST /v1/marketplace/seller/payout
| Address | https://api.hanzo.ai/v1/marketplace/seller/payout |
| Method | POST |
| Operation | post_marketplace_seller_payout |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Starts binding one of the caller org's wallets as the wallet it is paid into: answers a challenge naming the org, the wallet and its address, to be signed with that wallet within fifteen minutes and sent to POST /v1/marketplace/seller/payout/verify. A newer challenge replaces an older one. An org admin binds.
Request
1 field, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
wallet | body | string | — | Wallet is one of the caller org's wallets. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | marketplace.PayoutChallenge | ok |
default | problem-details | refused |
200 body — 5 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
address | body | string | — | Address is its address, which the signature must recover to. |
digest | body | string | — | Digest is the EIP-191 hash of Message, 0x hex: what POST /v1/wallet/{id}/sign signs, for a wallet the platform holds. |
expires | body | integer (int64) | — | Expires is when the challenge may no longer be signed, unix seconds. |
message | body | string | — | Message is the text to sign with the wallet (EIP-191 personal_sign). |
wallet | body | string | — | Wallet is the wallet to prove. |
Failure carries the platform error shape — see Errors.
Examples
hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.
import { Configuration, MarketplaceApi } from 'hanzoai';
const api = new MarketplaceApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postMarketplaceSellerPayout({ wallet: "<wallet>" });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import MarketplaceApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = MarketplaceApi(client).post_marketplace_seller_payout(wallet="<wallet>")cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.MarketplaceAPI.PostMarketplaceSellerPayout(context.Background()).Execute()
if err != nil {
return err
}use hanzo_client::apis::{configuration::Configuration, marketplace_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = marketplace_api::post_marketplace_seller_payout(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.MarketplaceApi;
ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));
var result = new MarketplaceApi(client).postMarketplaceSellerPayout();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl -X POST https://api.hanzo.ai/v1/marketplace/seller/payout \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"wallet": "<wallet>"
}'MCP reaches marketplace through the marketplace tool, which names its 6 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "get_marketplace"
}
}
}'How is this guide?