Not sure if tangled has a sort of API documentation available, which I can use for some automation.
Use case ideas:
- Register a bot, then receive an API key I can use to authenticate that bot against tangled
- Comment on a pull request from a pipeline, for example to show that it has been deployed to a given service (Railway for instance)
- Run a search for related issues, then comment on an issue when similar issues have been found
- Link tangled with a certain project management tool (Fizzle, Trello, Jira, etc...) and when a new PR comes in/is edited, check if it references a Jira ticket, then add a label like
jira/TICKET-ID. then when that PR is merged, the jira ticket can also close automatically
Tangled aims to be a decentralized service by using atproto, and once it is fully decentralized, you won't need tangled-hosted API for most of the operations! The protocol is the api. Of course we will provide convenience APIs for things like full-text search which can be easily done after #800 gets merged.
Tangled isn't fully decentralized yet, but that is current direction to give users control over their data.
I'm closing this issue as a duplicate of #29, #47 and #56.