Trade an X sign-in code for its tokens
Trade the code X's sign-in page handed back for the connection's access and refresh tokens, kept sealed in the vault
Trade the code X's sign-in page handed back for the connection's access and refresh tokens, kept sealed in the vault
One token request to X (the x descriptor's acquire.token_url, client_auth basic, PKCE): the code, the callback address, the PKCE verifier and the sign-in app's id go in a form body, and the app's Basic credentials (the held x-sign-in-client-secret-basic) in the Authorization header, each placed from the vault only as the request leaves. The reply's access_token and refresh_token are kept in the vault as the new connection's own fields (reply_holds_values) before the reply is read. 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 X's sign-in page handed back for the connection's access and refresh tokens, kept sealed in the vault”