Trade a Threads sign-in code for its short-lived token
Trade the code Threads' sign-in page handed back for the connection's short-lived token, kept sealed in the vault
Trade the code Threads' sign-in page handed back for the connection's short-lived token, kept sealed in the vault
One token request to Threads (the threads descriptor's acquire.token_url, client_auth form): the code and the callback address go in a form body with the Threads login's app id and secret, placed from the vault only as the request leaves. The reply's access_token (Threads' short-lived token) is kept in the vault as the new connection's field short_lived_access_token before the reply is read; tool:trade-a-short-threads-token-for-a-long-one then trades it for the 60-day token (the descriptor's acquire.then). Run by tool:connect-an-account-by-signing-in-to-the-service at the sign-in callback.
Nothing: your AI starts it with your words.
Connect the AI you already use to Trillion once. Then ask in your own words; your AI finds this tool by what it does and runs it.
Say to your AI: “Use Trillion to trade the code Threads' sign-in page handed back for the connection's short-lived token, kept sealed in the vault”