Accounts on other platformsCreate and connect accounts on other platforms. CRE8 fills forms, calls APIs and keeps every credential in the vault; you solve captchas, accept terms and approve access on each platform's own pages.
Sign in to start a job or continue one. The platform map below needs no sign-in.
Platform map
Account: browser. No registration API. Signup runs in the visible browser; the person solves the captcha, verifies the email and submits.
App: browser. Since November 2025 Reddit approves new API apps by hand (Responsible Builder Policy, requested through Developer Support). Once approved, a 'script' app is created at reddit.com/prefs/apps: the engine fills the form and the person clicks create, which accepts Reddit's developer and Data API terms.
Connects by: OAuth2 password grant with the script app: client_id, client_secret, username, password.
Yours to do: captcha, email_verification, review, terms
Bluesky
Account: api_when_allowed. com.atproto.server.createAccount on a PDS. describeServer says whether an invite code or phone verification is required. bsky.social gates signup behind a captcha in its web app, so that path runs in the browser and the engine watches for the account via createSession.
App: api. An app password from com.atproto.server.createAppPassword, made with a session of the new account.
Connects by: Handle plus app password against the account's PDS.
Yours to do: captcha, phone_verification, email_verification, terms
Matrix
Account: api_when_allowed. POST /_matrix/client/v3/register with user-interactive auth. m.login.dummy and m.login.registration_token complete over the API; m.login.recaptcha and m.login.terms go to the person through the homeserver's fallback page; m.login.email.identity waits on the emailed link.
App: not_needed. Registration returns an access token; no app is registered.
Connects by: Access token and homeserver URL.
Yours to do: captcha, terms, email_verification
Operator settings still missing: registration_token
Discord
Account: operator_once. A bot is an application's bot user, owned by a person's Discord account; that account's signup is captcha-gated and is the operator's.
App: browser. Applications are created in the Developer Portal after accepting the Developer Terms; there is no public API for it. The bot token is shown once, after Reset Token (which may ask for the password or a 2FA code).
Connects by: Bot token, then a bot-install link a server admin approves.
Yours to do: terms, mfa, consent
Slack
Account: not_needed. A Slack bot is an app's bot user in a workspace; no account is created.
App: api. apps.manifest.create, with an app configuration token the operator generates on api.slack.com (it lasts 12 hours). Without one, the person creates the app from the generated manifest and hands over its client id and secret.
Connects by: OAuth v2 install: a workspace member approves it and oauth.v2.access returns the xoxb bot token.
Yours to do: terms, consent
Operator settings still missing: config_token, redirect_uri
X (Twitter)
Account: browser. Signup is captcha- and phone-gated and runs on x.com.
App: browser. A developer account, project and app in the X Developer Portal; signing the Developer Agreement is the person's act.
Connects by: OAuth 2.0 authorization code with PKCE for a user-context token; offline.access adds a refresh token.
Yours to do: signup, app_registration, terms, consent
Operator settings still missing: client_id, client_secret, redirect_uri
YouTube
Account: browser. A Google account and a YouTube channel are created by a person; Google signup is phone- and captcha-gated.
App: browser. A Google Cloud OAuth client with the YouTube Data API enabled, made in the Cloud Console.
Connects by: Google OAuth consent for the youtube.force-ssl scope with offline access.
Yours to do: signup, app_registration, consent
Operator settings still missing: client_id, client_secret, redirect_uri, api_key
Account: browser. Signup runs on instagram.com or the app and is captcha- and phone-gated.
App: not_needed. Social's 'instagram' provider uses the web session, not a registered app. The official Graph API connects through Social's own instagram_graph OAuth instead.
Connects by: The sessionid, ds_user_id and csrftoken cookies of a signed-in browser, handed over by the person (the extension never reads cookies).
Yours to do: signup, supply
eBay
Account: browser. Seller accounts are opened on ebay.com by the seller, with eBay's identity and payout checks.
App: operator_once. One keyset and RuName in the eBay Developer Program, whose accept URL is this runtime's /provision/oauth/callback. Production keys need a marketplace-account-deletion endpoint (Listing owns it).
Connects by: OAuth authorization code with the RuName: a 2-hour access token and a refresh token of about 18 months, read through Provision.AccessToken.
Yours to do: consent
Operator settings still missing: client_id, client_secret, ru_name, environment
Etsy
Account: browser. Shops are opened on etsy.com by the seller.
App: operator_once. One app (keystring and shared secret) registered at etsy.com/developers, with this runtime's callback as a redirect URI. New apps work for the developer's own shop until Etsy approves commercial access.
Connects by: OAuth 2.0 authorization code with PKCE: a 1-hour access token and a 90-day refresh token that rotates on every refresh. API calls send x-api-key as keystring:shared_secret.
Yours to do: consent, review
Operator settings still missing: client_id, client_secret, redirect_uri
Amazon Seller (mapped, not automated yet)
Account: browser. Seller Central registration with identity verification.
App: operator_once. An SP-API developer profile and app registered through Seller Central.
Connects by: Seller authorization from Seller Central (an OAuth consent) returning a Login with Amazon refresh token.
Yours to do: consent, review
Operator settings still missing: client_id, client_secret, application_id
Walmart Marketplace (mapped, not automated yet)
Account: browser. Marketplace sellers apply and are approved by Walmart.
App: browser. The seller generates API keys in Seller Center.
Connects by: Client id and secret the seller hands over, exchanged for access tokens by client credentials.
Yours to do: review, supply
Mastodon (mapped, not automated yet)
Account: browser. POST /api/v1/accounts exists, but it takes agreement=true, an assertion that the person accepted the server's rules and terms. The lane would send the person to the server's own signup page instead.
App: api. POST /api/v1/apps registers an OAuth client.
Connects by: OAuth token for the account.
Yours to do: terms, email_verification