store_product_v1_metadata
Stores a ProductV1 metadata object to IPFS. Call before create_offer to get metadataUri and metadataHash. Returns: { metadataUri: 'ipfs://...', metadataHash: '0x...' }.
Category: Offer management.
Returns unsigned tx? Likely yes — sign locally and broadcast via send_signed_transaction or a meta-tx relay.
Input schema
| Field | Type | Required | Description |
|---|---|---|---|
schemaUrl | string | yes | |
type | PRODUCT_V1 | yes | |
uuid | string | yes | |
name | string | yes | |
description | string | yes | |
externalUrl | string | yes | |
licenseUrl | string | yes | |
youtubeUrl | string | no | |
condition | string | no | |
image | string | yes | |
imageData | string | no | |
animationUrl | string | no | |
attributes | object[] | yes | |
product | object | yes | |
variations | object[] | no | |
seller | object | yes | |
shipping | object | yes | |
exchangePolicy | object | yes | |
productOverrides | object | no | |
configId | string | yes | Boson/Fermion Protocol deployment identifier. Format: '<env>-<chainId>-<index>' e.g. 'production-137-0' (Polygon mainnet), 'testing-80002-0' (Amoy testnet). Call get_config_ids to list all valid values for this server. |
signerAddress | string | yes | Ethereum address that will sign and send this transaction. Must match the wallet that will sign the returned transaction locally. |
Related
- Reference → MCP tools — full catalogue.
- Build for AI agents → The 3-step signing pattern — what to do with returned unsigned transactions.
- Concepts → Signing & meta-transactions — canonical signing reference.