Proposal - Intear events API

[Sliman4]

Discussion of https://dev.near.org/infrastructure-committee.near/widget/app?page=proposal&id=30

[Sliman4]

Report after 3 months

• All indexers mentioned in the proposal are done, in INTEARnear organization, and can be used either as libraries or for self-hosting Intear APIs
• New HTTP / WebSocket APIs are live. WebSocket features improved server-side filtering, and HTTP APIs for historical data are now limited to a specific set of queries that are guaranteed to be fast (indexed). WebSocket has client libraries for TypeScript (browser or nodejs) and Rust (only backend for now)
• All APIs and indexers are production ready (though relying on free public ones is not recommended as rate limits can change), with 99.97% uptime of public WebSocket API in the last 30 days, 99.999% uptime of public HTTP API, and 100% uptime of indexers
• All features mentioned in the proposal, except Aurora transactions and chain signature requests (not deemed needed by our users, so didn't want to waste UI space, but available via API), are in the bot (@bettearbot > /start > Notifications)
• All APIs and libraries are fully documented on docs.intear.tech, but without videos yet, waiting for Rainy (an upcoming self-serve platform for cloud indexing that is going to launch next week) to make a huge hour-long guide, or a series of small videos about everything in the Intear stack at once

Metrics

• Known projects using inindexer: Was 1, now still 1, hard to keep track of them since most projects on near are not open source, but some people were mentioning it in t.me/neardev, so I guess more people have tried it
• Dapps using APIs: Was 1, now 3 (meme.cooking, dragontech.bot, aidols.bot) known ones, and a lot more unknown ones. Not sure if should be included since they're developed internally, but pumpit.intear.tech and oracle.intear.tech use them as well
• Historical API requests per month: Was 2,000,000, now around 700,000, probably because now there are less endpoints and no pagination in the free public API. They come mainly from aidols.bot, this website has no backend at all, it just uses Intear APIs for tokens, charts, trade history, volume, liquidity.
• Telegram bot users: Was 3,000 total, now 4,100 total. Only 70 of them have ever used the mini block explorer, mainly because of lack of awareness and lack of information in the bot. To use it, they should start typing "@bettearbot " and start typing the token ticker / token contract address / account id / transaction hash / receipt hash, but Telegram messages have a limited size and a very restricting request time limit for the data in dropdowns, which are the only usable way to represent lists with selectable items in Telegram