APIS integrations are built from the ground up: we support each blockchain native interface and extend those interfaces into cross-chain interoperable interfaces. There are three types of interfaces in the APIS protocol: Native, Extended, and Unified.
Native: Blockchain-specific interfaces of the individual chain, typically JSON-RPC 2.0.
Ex: Get block information for one blockchain, with a specific request payload
Extended: HTTP and Websocket extensions of native interfaces, often REST-based, which extend the native functionality or reduce its complexity for end-users.
Ex: Get token transfers for any address, on any chain, with a generic payload
Unified: HTTP and Websocket agnostic interfaces of multiple chains, often REST-based, which greatly extend the native functionality, reduce complexity for end-users, and allows cross-chain interoperability.
Ex: Send a transaction on any blockchain, with a generic payload, and few required arguments
The primary consumers of APIS endpoints are DApps and DApp developers. APIS endpoints are built from each individual blockchain interface, so DApps may incrementally adopt the APIS endpoints. If you want to swap out your current web3 solution for the APIS now, check out our Getting Started page.
API Token Utility
The API community token is used for a myriad of functions.
Payment for Services Rendered: Consumers may provide and/or stake API tokens in exchange for services rendered by network providers.
Staking by APIS Nodes and APIS Gateways:Nodes and gateway operators are required to stake a number of API tokens in order to establish their network presence. This will be subject to slashing, should the actor be proven to act maliciously.
Dispute resolution: This mechanism allows API holders to determine whether Nodes or Gateways acted maliciously (similar to Augur’s dispute resolution mechanism).
Staking by Optimistic or Zk-Rollup validators: We anticipate this feature will be in place within a year.
Governance: Numerous ways to decide on new APIS contracts and upgrades through a voting system.
API Token Allocation
API Token Release Schedule
The initial two-years token allocation is as follows:
43% to The APIS community members 43,000,000 API
21% to team members and future employees with 2 - year vesting 21,000,000 API
19% to Community Treasury with 1- year vesting 19,000,000 API
17% to DApp Partners with 2 - year vesting 17,000,000 API