Yes - a lot of possibilities. Path.Tax is just an example of apps that can be built on the platform. API docs coming very soon. If you join the waitlist, I'll notify users once it is ready.

"aggregation of all historical trades, transfers and assets" - yep, you got it. It will include manual input too - as you mentioned. The goal is actually to automate as much as possible.

Trading - no. But it shouldn't be hard to add - but it is a policy issue vs tech. And it'll never be as fast as trading on the exchange itself due to the extra layer. Think of the current Path. API as a 'ledger of ledgers'. A view of trades/assets across all exchanges and wallets. There are many possible use cases - like the tax manager or a more advanced 'coin tracker' type app. There are no user identifiable info at the API level - just a hash that ties things together in the path system. There is no way (at the user level) I'll know who that data belongs to. The app (like path.tax) that sits on top of the platform, handles any user identifiable info (if they choose to do so).

Thanks for the detailed feedback. The tax manager currently only supports US. Not a technology issue but because tax laws vary a lot between countries, so it is just bandwidth to cover different cases. As for the APIs, the big advantage is that I don't store any user identifiable info. 100% agree about the visibility of information stored. Trading is an interesting case - but it does open up different challenges. Latency as you mentioned. Additionally, trust and various policy also. Thanks again.