Venly (NFT API) ACTION
Create Contract
Deploys a new NFT contract, or collection, on a specific blockchain. See the documentation
- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Venly (NFT API) account once, then configure and run Create Contract from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "venly-create-contract",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
venly: { authProvisionId: "apn_xxxxxxx" },
name: "Name",
symbol: "Symbol",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "venly-create-contract",
"configured_props": {
"venly": { "authProvisionId": "apn_xxxxxxx" },
"name": "Name",
"symbol": "Symbol"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "venly",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "venly-create-contract",
arguments: {
name: "Name",
symbol: "Symbol",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
name Name | string | The name of the contract/collection Required |
symbol Symbol | string | The symbol for the contract such as VENS Required |
description Description | string | The description of the contract/collection Required |
image Image URL | string | The URL of the image that will be displayed for your collection Required |
externalUrl External URL | string | You can add an external URL to your collection. This can be anything such as a link to your website Required |
media Media | object | This is the media object where you can add an optional key-value pair Optional |
owner Owner | string | The wallet address which will have admin access to the contract. The owner can call the admin right functions on the contract. If not specified, the contract will be managed by Venly. Optional |
autoApprovedAddressesLocked Auto Approved Addresses Locked | boolean | Optional |
storageType Storage Type | string | This object holds the storage details for the metadata of the item being created Optional |
storageLocation Storage Location | string | Location of the NFT metadata. This property is mandatory only if Storage Type is set to custom Optional |
chain Blockchain | string | The blockchain on which your contract/collection will be created Required Dynamic |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- venly-create-contract
- Version
- 0.0.3
- App
- Venly (NFT API)
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗