How does the Fetch.ai Mobility Framework help you develop on Fetch.ai

The Mobility Framework consists of a set of protocols describing how agents must look, and what language they must talk in order to take part. Once compliant agents are able to form part of the Mobility Framework: they are able to deliver, or be delivered.

In addition to forming the key components for actual delivery, agents are also able to provide information and services, such as identity support, credential verification or insurance and dispute resolution. Some of these services consist of agents and smart contracts to support them.

The initial release of the Mobility Framework describes the initial set of protocols, in particular, the way in which agents negotiate for a delivery to take place.

These protocols determine the actions of a number of agent types that exist within the Fetch.ai network. The Mobility Framework presents a schema and protocol for the actions of:

• “Drivers” — mobile agents that move to deliver items
• “Depots” — sources of items that need to be moved
• “Passengers” — agents representing humans that wish to move
• “Parcels” — agents representing the items in the network
• “Locations” — physical locations in the real world

By creating a first principles markup language and communication and value transfer protocol for the logistics network, we see a huge opportunity for emergent properties of the network to develop as more users are onboarded.

In addition to code samples, there is documentation which describes what takes place during these negotiations. It is worth noting that:

1. As a public permissionless system, anyone can build compliant agents providing mobility solutions or provide information that aids other activities (route optimisation, hyper-local intelligence, other support).
2. As 2020 moves into Q1, 2021, full working agents will be released for packages, food and ride hailing. These can be used as a base for other agents.
3. Negotiation between agents uses a FIPA style mechanism that’s well described in the existing agent framework documentation at https://docs.fetch.ai/aea.

To also check out the documentation we have released so far concerning the Autonomous Economic Agents (AEA), you may head over to our repository on docs.fetch.ai.

Because we want to underline the transparency in our approach towards and hence we are open to continued collaboration between us and the community, if you’re interested in helping us create agents yourself and deploy them to the OEF (Open Economy Framework), you can shoot us an email to developer@fetch.ai or join us on Discord.

The anticipated benefits for you are::

• You can use the developer tools, public interfaces and /API schema to be a part of the project that will deliver decentralized mobility solutions.
• You do not need any prior knowledge in Fetch.ai in order to create data and features.
• You can join our Incentivized Testnet Phase and construct an agent yourself and deploy it on the OEF (Open Economy Framework). The OEF acts as a decentralized search and discovery mechanism where upon the agents will communicate using the agents P2P network.

The role of the FET token in the Mobility Framework

Within the context of the Fetch.ai Mobility Framework, here is how the FET token will be utilized:

1. Constructing and deploying agents on the Open Economic Framework: Once a developer has built an agent and it complies with the Mobility Framework, it can be deployed on the network. FET tokens would be the fuel driving the interaction between different agents.
2. Exchange of information and services between agents: When two agents on the mobility framework have successfully connected, communicated and negotiated a service or requested information, one needs to pay the other for the data or service on offer. The FET token, in this case, acts as the medium of exchange in all network transactions.
3. Smart contract execution and maintaining framework integrity: Within the Mobility Framework, FET token also dynamically exchanged to pay network operation, smart contract execution, and maintenance fees.

The FET token enables the activities listed above on the Mobility Framework and is the currency agents use to pay for the benefits they derive from the wider network, whilst also providing a frictionless means of paying each other.