YOUR PUBLISHING CONNECTION

Copy a prompt.
Your agent does the setup.

Use Codex, Claude, or Grok Bot to put approved sponsor banners on your X profile. Give your agent the prompt below—or just this site—and ask it to connect.

Paste it into my current agent. Your agent handles the setup and tells you what is ready.

View the prompt

Set up Sold My Soul Auto-sponsor for me at https://soldmysoul.ai, using my current agent and my existing agent account. Read https://soldmysoul.ai/agent-setup.txt and follow its current setup guide. Handle the installation, pairing, connection checks, and supported scheduling yourself. Keep the companion in a dedicated folder and preserve my existing agent settings.
If you need a setup code, open Auto-sponsor on the site in my signed-in browser and create one for this agent after installation.
Use my normal browser and permissions. Let me handle sign-in, account consent, or any step that requires me; do not ask me for model API keys. Check that you can use the correct X account and upload a local file. Do not change my X banner during setup.
Prefer a native scheduled task or routine when this agent supports it. Otherwise use the documented local adapter. Set up hourly checks for eligible, approved, paid sponsor banners; show the schedule and its next run. Retain the site's approval rules. Never enable blanket permissions, alter payouts, or forward passwords or browser cookies.
Finish with a short readiness report: paired account, connection check, browser/file-upload access, schedule, and any remaining blocker. Do not call setup complete merely because instructions or files were created.

Or just give your agent the site

“Set up Auto-sponsor for me on https://soldmysoul.ai.”

Agent instructions

Connections are in preview. Setup checks do not upload a banner. Live uploads still need validation with your agent and X account.

Already connected to X?

Choose your agent in Auto-sponsor to get a prompt with a one-time setup code. It lets your agent pair itself. The code expires after 10 minutes; your agent can get a fresh one from your signed-in marketplace session if installation takes longer.

Use the agent you already work with

When supported, your agent can check for banners through its own scheduled task or routine. The prompt asks for hourly checks and a readiness report. Codex desktop tasks need the app, computer, and companion folder available. Grok Bot uses its own persistent computer and routines; its browser and files live on that shared account computer. Claude Code can use the included local channel.

A text-only chat cannot install software or upload a file to X. Your agent must have browser control, local file access, and the necessary account permissions. If something is missing, it should tell you exactly what needs connecting.

Setup is separate from your first upload

The agent checks its connection without taking a banner job. Once you approve a paid campaign’s finished artwork, Auto-sponsor can pass that exact image to your agent during the booked period. Safety screening, account checks, and your approval rules still apply.

After the agent reports an upload, check your X profile and confirm it in the marketplace. Interrupted or uncertain uploads wait for your review and are never silently retried.

If you give the agent only the site

The agent can follow the setup links here to discover the current instructions and companion download. It should complete the setup, verify the connection, and show its real schedule and next run. Creating files alone is not a completed connection.

Read the instructions for agents

Manual setup and connection details

Install and pair

Download companion

Use Node.js 22.22.2 or newer. Extract the download, open its folder, and follow the included README. Replace YOUR_SITE_ORIGIN with the address of the marketplace you are using.

npm ci --ignore-scripts
node companion.mjs pair --origin YOUR_SITE_ORIGIN
node task.mjs status

Codex CLI fallback

Start the local listener with your normal browser tools configured, then run the companion. It creates a separate publishing thread rather than attaching to a desktop conversation.

codex app-server --listen ws://127.0.0.1:4500
node companion.mjs doctor --check-codex
node companion.mjs start

The upstream WebSocket connection is experimental. A native scheduled task can avoid that adapter when available.

Claude Code channel

The README explains how to register the included local channel. Custom channels require Claude’s development-channel opt-in. Normal browser permissions and organization rules apply.

Private preview access

A private site’s sign-in gateway can prevent the standalone companion from reaching the publishing queue. Your agent must report that blocker. Public API access, a linked X account, and image moderation are required before live publishing can be validated.

Connection references

Codex scheduled tasks Codex App Server Claude Code channels Grok Bot routines