Token Terminal API Listing Portal

❗️Please note that due to resource constraints, we’re likely to prioritize submissions with complete data sets.
General information

Please provide general information about the project.
1. Project name
2. General information
Please provide links to the protocol's official Twitter, website, and Github accounts.
3. Contact and role information
Please provide your email, Twitter, and Telegram handles and role.
4. Operating model information
Please provide a short description of how the project works.
Business model information

At Token Terminal, we see most of the protocols/blockchains as two-sided market places. E.g. on Polygon validators process transactions sent by users. The users pay a fee for this service and that fee is divided between the validators and burn.
5. Fee model
Please provide an explanation of your fee model. This should include who pays for the service and who receives the fees (validators, users, burn, protocol, etc.). Include a link to your documentation explaining this subject. For more information, please see our documentation: https://docs.tokenterminal.com/
6. Incentive model
Please provide an explanation of your incentive / block reward model. This should include where do the incentives come from and how are they split between different stakeholders (validators, users, protocol, etc.). Include a link to your documentation explaining this subject. For more information, please see our documentation: https://docs.tokenterminal.com/
7. Stakeholders
Please provide an explanation of your different stakeholders and what their roles are. For more information, please see our documentation: https://docs.tokenterminal.com/
API specification and format
For most projects we are looking to add the following historical metrics:
- fees (e.g. transaction fees, burn),
- incentives (e.g. block rewards, token rewards),
- daily active users (unique tx senders, unique users),
- volume (trading volume, outstanding borrows, etc. N/A for blockchains),
- treasury (USD value of the protocol’s funds held on-chain including unallocated governance tokens),
and how these are split between different stakeholders (validators, users, protocol, etc.).

Below we have listed some requirements and preferences for the format in which we prefer to fetch the data.

Requirements:
- Web API (REST, GraphQL, etc.)
- Ability to query it historically
- Timestamp, date, or startDate/endDate for each row
- Value for each row (if applicable)
Preferences:
- Denominated in underlying token denomination specified for each row. We need to be able to derive the USD prices for fee, incentive values and volume values
- startDate and endDate parameters where the range for e.g. startDate: 2020-11-01 and endDate: 2020-11-02 is exclusive to 2020-11-01 -> 2020-11-02 and fully covers data from 2020-11-01
- Full historical dataset
- Daily granularity or all relevant transactions
- Unique id for each row
- Component level information included (this can be asset in which the fee is paid, type of token incentive, etc.)
API endpoint information

Please provide the relevant API endpoints, queries and parameters needed to track the following key metrics. Link to corresponding section of API documentation is sufficient if it contains all relevant information.
8. Fee endpoints + example queries
Please provide API endpoint + example queries needed to calculate fees and the split between different stakeholders. Add a short explanation what the fetched metrics correspond to. Feel free to add multiple endpoints for different fee types (transaction fees, burn, protocol fees etc.). Include an API key and link to your API documentation.
9. Incentive endpoints + example queries
Please provide API endpoint + example queries needed to calculate token incentives. Add a short explanation what the fetched metrics correspond to. Feel free to add multiple endpoints for different incentive types (validator rewards, governance rewards, protocol rewards etc.). Include an API key and link to your API documentation.
10. Active users endpoints + example queries
Please provide API endpoint + example queries needed to calculate active users. Add a short explanation what the fetched metrics correspond to. Include an API key and link to your API documentation.
11. Volume endpoints + example queries (optional)
Please provide API endpoint + example queries needed to calculate volumes. Add a short explanation what the fetched metrics correspond to. Include an API key and link to your API documentation.
12. Treasury endpoints + example queries (optional)
Please provide API endpoint + example queries needed to calculate treasury values. Add a short explanation what the fetched metrics correspond to. Include an API key and link to your API documentation.
13. Other relevant endpoints + example queries (optional)
Please provide API endpoint + example queries needed to calculate the values. Add a short explanation what the fetched metrics correspond to. Include an API key and link to your API documentation.
Additional information

Please provide the following additional information about the project, if applicable.
14. Benchmark analytics information and link to block explorer (if applicable)
Please provide a link to a benchmark protocol analytics page and block explorer, if available.
15. Token unlock information
If applicable, please provide information regarding your token unlock schedule.
16. Fundraising information
Please provide information about prior funding rounds.
17. Please verify that you are human*
Should be Empty:

General information

Business model information

API specification and format

Requirements:

Preferences:

API endpoint information

Additional information