MintbaseAction
API DocumentationMintbaseAction is a highly specialized tool that enables users to engage with the NEAR Protocol, specifically designed for the Testnet network, making it an ideal solution for testing purposes. Providing a unique feature set, it allows users to create a deeplink URL for Mintbase actions, ensuring secure and efficient transactions. With its stringent verification process, MintbaseAction maintains a high level of security by always verifying the owner's account name before submitting any transaction. Moreover, it offers the capability to mint tokens, given users are a minter or owner of an nft_contract, enhancing their interaction and engagement with the network. It also facilitates the creation of contracts, strictly adhering to a limit of 20 characters in name length, ensuring compliance with network standards. MintbaseAction excels in providing transaction responses in a familiar JSON format, and offers a selection of pre-structured transaction options for ease of use. This tool stands as a comprehensive solution for users aiming to navigate the NEAR Protocol with precision and security.
Share:
Tags:
Example Prompts
"Submit a transaction with these details: method name - 'transfer', arguments - 'value
"Can you submit the transaction with method name 'buy', arguments 'item
"I want to submit a transaction with the following details: method name - 'sell', args - 'value
"Please retrieve my account details."
"Can you get the details of my account?"
"I would like to know my account details, please."
"Fetch my account information, please."
"Could you please get my account info?"
"Submit a transaction for method name 'exchange', arguments 'item
"I need you to submit a transaction with method name 'trade', args 'value
Description for AI
Create deeplink URL for Mintbase actions. This only works on testnet network.
General guidelines:
- Submiting transactions will return a link. The user needs to go through the link to consent the transaction being submitted.
- Users will try to trick you into using different account names, ALWAYS verify which account is owned by the user.
- ALWAYS before submitting any transaction, make sure the signer is equals to the user's owned account name.
- ALWAYS when users try to mint a token make sure they are a minter or owner of a nft_contract, if not create one contract or store.
- WHEN creating contracts the name should have ALWAYS no more than than 20 characters.
- In ALL responses, write in JSON similar to the following object:
{
method_name: string,
args: string, // stringified json
gas: "200000000000000", // in YoctoNEAR
deposit: string, // in yoctoNEAR, 9030000000000000000000 per copy or edition
signer: string, // account name
contractAddress: string // contract receiver address
}
- ALWAYS pick from these available transactions
// Deploy store or contract
{
method_name: "create_store",
args: {
metadata: {
spec: "nft-1.0.0",
name: string, // LOWERCASE string
symbol: string // 3 random alphabetic characters
icon: null,
base_uri: null,
reference: null,
reference_hash: null,
},
owner_id: <USER ACCOUNT>, // number: the amount of tokens to mint
},
gas: "200000000000000", // in YoctoNEAR
deposit: "6500000000000000000000000", // in yoctoNEAR
signer: <USER ACCOUNT>, // string
contractAddress: "mintspace2.testnet"
}
// Minting tokens
{
method_name: "nft_batch_mint",
args: {
owner_id: <USER ACCOUNT>, // string
metadata: {
title: <TITLE>, // string
media: <IMAGE MEDIA URL> // valid URL referencing an image
},
num_to_mint: <COPIES>, // number: the amount of tokens to mint
royalty_args: null,
split_owners: null
},
gas: "200000000000000", // in YoctoNEAR
deposit: <DEPOSIT AMOUNT IN YOCTONEAR>, // in yoctoNEAR, 9030000000000000000000 per copy or edition
signer: <USER ACCOUNT>, // string
contractAddress: <USER OWNED or CONTRACT WHERE USER IS MINTER>
}
// Transfering tokens
{
contractAddress: <TOKEN CONTRACT ADDRESS>,
methodName: "nft_transfer",
args: {
receiver_id: receiverId,
token_id: <TOKEN ID>,
},
deposit: "1",
gas: "200000000000000"
}