Supporting Developers with the launch of the Autonomous Economic Agent Registry
Sep 25, 2020
Today we are unveiling an outcome of our developer engagement initiative, to make it easier to build applications and services on top of the Fetch.ai network.
We have developed a new Autonomous Economic Agent (AEA) registry that will allow you to build agents and participate in this new digital economy far more easily. The aim was to develop an effective “App Store” for developers that allows you to access and build agents like never before.
What are AEAs
At Fetch.ai we build tools and infrastructure to enable a decentralized digital economy. A key component of these economies are our Autonomous Economic Agents (AEAs). AEAs act independently of constant input from their owner and autonomously execute actions to achieve economic value for you.
They have the ability to conduct decentralized searches, negotiate and trade knowledge, and share predictions and value using a digital currency called the FET token We are building a constellation of agents that can connect to transportation, financial services and mobility assets, and now you can also participate in this opportunity.
Our new AEA registry
We have developed a new AEA registry that will allow you to build agents and participate in this new digital economy far more easily. You can access the new front-end registry here: https://aea-registry.fetch.ai/. The new UI was designed to make discovering AEA projects developed by the community, the most effortless and user-friendly experience possible. It allows you to find, download and publish AEA packages including entire agents, skills, connections, protocols and contracts.
Right now we have 302 components for you to use in your projects, including
100 ready to go agents alongside the following for you to discover:
110 skills which are the core focus of the framework’s extensibility as they implement business logic to deliver economic value for the AEA. They are self-contained capabilities that AEAs can dynamically take on board, in order to expand their effectiveness in different situations/
52 connections which wrap an SDK or API and provide an interface to network, ledgers and other services.
36 protocols which define agent-to-agent as well as component-to-component interactions within agents.
4 contracts which wrap smart contracts for third-party decentralized ledgers. In particular, they provide wrappers around the API or ABI of a smart contract