Learn how to practically implement Agent to Agent transactions from the proposed architecture in the ATCP/IP whitepaper.
Still new!
We are actively working on building out real examples for ATCP/IP using Story as its foundation. At its core, ATCP/IP is a standard for agent to agent interactions, and thus is an ongoing academic proposal for builders to implement and discover best practices through trial and error.
Below are details on how to actually implement the 2. An ATCP/IP Transaction section of the whitepaper below.
Below we will show how to implement each step of the ATCP/IP interaction flow as demonstrated by the image below.
In order to register an agent’s outputs (or really any IP) on Story, follow the How to Register IP on Story tutorial. The only difference is how you structure your IP Metadata, which should always follow the 📝 IPA Metadata Standard.
You can also check out more specific tutorials that demonstrate how to register images generated by DALL·E or Stability:
Here is an example of what the IP Metadata should look like for your generated IP (using a song as an example):
As described in the Whitepaper, agents will negotiate on what agreement terms are appropriate for the requested task:
Whitepaper Section
2 Terms formulation: The provider agent will consider the request and choose an appropriate set of
license terms for the information being requested. The terms system used should be programmable in
nature to facilitate the parsing and formulation of the terms, such as Story’s Programmable IP License
(PIL)[6].
3 Negotiation (optional): The agents may have an optional negotiation phase where terms may be
altered until they are deemed appropriate for both parties.
Once agents agree on the terms, they can be created and attached to the registered asset:
Learn how to attach terms to your IP using the SDK.
Learn how to attach terms to your IP using the Smart Contracts.
As stated in the Whitepaper, after agents have negotiated on a set of terms, the requester agent can mint a license from the provider agent with specific agreement terms attached:
Whitepaper Section
4 Acceptance: The requester agent will formally accept the terms by minting an immutable token (the
agreement token) that encapsulates the terms and rules by which the information being provided is
to be used. Once minted the agreement is binding and the agent should commit to memory all of the
terms associated with the information.
Once agreement terms are attached to an IP Asset, a License Token can be minted:
Learn how to mint a License Token using the SDK.
Learn how to mint a License Token using the Smart Contracts.
Now, the requesting agent has a License Token that can be held, giving it the rights to use the provided asset based on the attached terms.
Once the providing agent has been paid for their work (when the requesting agent minted a license that costed $), they can claim their due revenue:
Learn how to claim revenue using the SDK.
Learn how to claim revenue using the Smart Contracts.
We have implemented a Model Context Protocol (MCP) server that provides tools for interacting with Story’s protocol using the MCP Python SDK, and an AI Agent that uses those tools.
Run an MCP server locally that has tools for interacting with Story’s protocol to test Agent TCP/IP.
A LangGraph-based AI agent for creating, minting, and registering IP assets with Story using the Story MCP server.
Theoretically, an agent could also perform this in an agent-to-agent setting instead of agent-to-user.
“MCP is an open protocol that standardizes how applications provide context to LLMs. Think of MCP like a USB-C port for AI applications. Just as USB-C provides a standardized way to connect your devices to various peripherals and accessories, MCP provides a standardized way to connect AI models to different data sources and tools.”
Check out the Model Context Protocol (MCP) website to learn more.
Learn how to practically implement Agent to Agent transactions from the proposed architecture in the ATCP/IP whitepaper.
Still new!
We are actively working on building out real examples for ATCP/IP using Story as its foundation. At its core, ATCP/IP is a standard for agent to agent interactions, and thus is an ongoing academic proposal for builders to implement and discover best practices through trial and error.
Below are details on how to actually implement the 2. An ATCP/IP Transaction section of the whitepaper below.
Below we will show how to implement each step of the ATCP/IP interaction flow as demonstrated by the image below.
In order to register an agent’s outputs (or really any IP) on Story, follow the How to Register IP on Story tutorial. The only difference is how you structure your IP Metadata, which should always follow the 📝 IPA Metadata Standard.
You can also check out more specific tutorials that demonstrate how to register images generated by DALL·E or Stability:
Here is an example of what the IP Metadata should look like for your generated IP (using a song as an example):
As described in the Whitepaper, agents will negotiate on what agreement terms are appropriate for the requested task:
Whitepaper Section
2 Terms formulation: The provider agent will consider the request and choose an appropriate set of
license terms for the information being requested. The terms system used should be programmable in
nature to facilitate the parsing and formulation of the terms, such as Story’s Programmable IP License
(PIL)[6].
3 Negotiation (optional): The agents may have an optional negotiation phase where terms may be
altered until they are deemed appropriate for both parties.
Once agents agree on the terms, they can be created and attached to the registered asset:
Learn how to attach terms to your IP using the SDK.
Learn how to attach terms to your IP using the Smart Contracts.
As stated in the Whitepaper, after agents have negotiated on a set of terms, the requester agent can mint a license from the provider agent with specific agreement terms attached:
Whitepaper Section
4 Acceptance: The requester agent will formally accept the terms by minting an immutable token (the
agreement token) that encapsulates the terms and rules by which the information being provided is
to be used. Once minted the agreement is binding and the agent should commit to memory all of the
terms associated with the information.
Once agreement terms are attached to an IP Asset, a License Token can be minted:
Learn how to mint a License Token using the SDK.
Learn how to mint a License Token using the Smart Contracts.
Now, the requesting agent has a License Token that can be held, giving it the rights to use the provided asset based on the attached terms.
Once the providing agent has been paid for their work (when the requesting agent minted a license that costed $), they can claim their due revenue:
Learn how to claim revenue using the SDK.
Learn how to claim revenue using the Smart Contracts.
We have implemented a Model Context Protocol (MCP) server that provides tools for interacting with Story’s protocol using the MCP Python SDK, and an AI Agent that uses those tools.
Run an MCP server locally that has tools for interacting with Story’s protocol to test Agent TCP/IP.
A LangGraph-based AI agent for creating, minting, and registering IP assets with Story using the Story MCP server.
Theoretically, an agent could also perform this in an agent-to-agent setting instead of agent-to-user.
“MCP is an open protocol that standardizes how applications provide context to LLMs. Think of MCP like a USB-C port for AI applications. Just as USB-C provides a standardized way to connect your devices to various peripherals and accessories, MCP provides a standardized way to connect AI models to different data sources and tools.”
Check out the Model Context Protocol (MCP) website to learn more.