NagentArtefacts
Dev & Technology
Enterprise and White Glove
Company
Owl Protocol connects to a Nagent workspace with an API key. Once it is connected, agents can call 3 Owl Protocol actions: "Get Project Details", "List Projects" and "Deploy ERC721 Collection". Nothing is enabled on connect: each action is allowed one at a time, and an action with side effects runs or waits for a person according to the agent's level.
Every operation an agent can call against Owl Protocol, with input parameters and output schema.
OWL_PROTOCOL_DEPLOY_COLLECTIONTool to deploy a new ERC721 collection contract. Use after creating a project to programmatically deploy the collection on a specified blockchain.
Input parameters
Constructor arguments for the contract.
Display name for the ERC721 collection.
Symbol for the collection (token ticker).
Blockchain network chain ID.
Transaction parameters to override (e.g., gasLimit).
Project identifier.
Name of the contract to deploy.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OWL_PROTOCOL_GET_PROJECT_DETAILSTool to retrieve details of a specific project. Use when you need metadata about a project after authenticating with your API key.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
OWL_PROTOCOL_LIST_PROJECTSTool to list all projects. Use when you need to retrieve all projects accessible by the authenticated user.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
Agents can call 3 Owl Protocol actions on Nagent: "Get Project Details", "List Projects" and "Deploy ERC721 Collection". Get Project Details: Retrieve details of a specific project. Each action is listed on this page with its input parameters and its output.
Owl Protocol connects with an API key, under your workspace's own connection. Nothing is enabled on connect: each action is allowed one at a time and can be scoped to the agents that need it.
It returns data, error and successful.