Launch ads from Cursor

You launch ads from Cursor by giving the agent a complete brief, letting it use the public Adprime Zero surface, and completing prepaid funding in the browser.

Cursor can read docs, run terminal commands, and keep going after a tool returns. That is useful for campaign setup. It is also how a model invents provider IDs if you let it. The working path is: discover the live product, create account objects through ztdsp or the API, stop at a hosted payment link when the wallet needs money, then iterate from real delivery.

Start with the public brief

The full operator prompt lives on Get started. The copy-paste $20/day version lives in the Cursor launch prompt. Use one of those, not a one-line "buy me ads" request. The brief tells the agent to:

• Run npx -y ztdsp agent-guide before it guesses routes.
• Choose dashboard, MCP, CLI, or REST for the environment.
• Collect website, offer, geography, daily budget, and a real 300x250 or source image.
• Store ADP_ZERO_API_KEY in secrets, never in the prompt transcript.
• Request a hosted prepay link instead of asking you to type a card into chat.
• Treat dashboard read time and provider sync time as different clocks.

If you already have an account, point the agent at signup only for the browser payment step. Ordinary API work uses the key, not a dashboard login cookie.

What Cursor should create

A first test needs targeting, an approved creative, a campaign, and prepaid balance. The agent can pre-check the landing page, submit the image with headline, description, click URL, expected content, and disclosure, then create the campaign and wait on review. Activation still depends on those objects being ready. The agent should not invent campaign IDs, line-item IDs, or creative IDs. Those values come back from the product after the public calls succeed.

Creative rotation after launch uses campaign associations: list, add, replace, pause, resume, remove, or copy. The API blocks pause or remove of the final active creative. Rotate creatives on a live campaign is the job page for that rule.

What you do in the browser

Payment stays on the hosted page. For agent-created funding links, the URL opens Adprime Zero login with the account email pre-filled. You verify the email, review or change the amount, then continue to Stripe Checkout. The agent polls the funding intent and continues when the wallet can support the daily cap.

You also look at the landing page the agent submitted. Destination checks are automatic and factual: a crawler, redirect policy, Safe Browsing, and restricted-category classification. A missing classifier signal parks in requires_review. It does not silently pass. Approve a landing page an agent submitted is the review guide.

After it is live

Ask Cursor for campaign performance, not for a story about CTR. If impressions or spend exist and clicks are zero, the next command is a freshness and field-name check, not a targeting rewrite. Read performance without fooling yourself lists the meters.

A sibling path if you are not in Cursor: run ads from Claude, ChatGPT, or Codex. The account is the same. The discovery and setup pillar for any agent is Run ads from an AI agent.