Cursor prompt: launch a $20/day test
Copy a Cursor prompt that creates targeting, submits creative, and requests a funding link for a twenty-dollar daily test. The agent must read ztdsp docs and must not invent Beeswax IDs.
Published 2026-09-09 · Search job: Cursor ads prompt
Paste this into Cursor when you want a first paid display test, not a research memo.
The job is a twenty-dollar daily campaign on Adprime Zero. The agent should use the public product path: ztdsp, the docs, the API, or MCP. It should create targeting, submit a creative, and stop at a hosted funding link when the wallet needs money. It should not invent Beeswax campaign IDs, line-item IDs, or creative IDs. Those objects are created by the product after the public calls succeed.
What this prompt is for
A Cursor session can read the repo, run terminal commands, and keep going after a tool returns. That is useful for launch work and dangerous if the model improvises provider IDs. The June 2026 learning flight and later reporting gaps both got worse when people treated guessed fields as truth. This prompt tells the agent to discover the live surface first, then act.
Use a real landing page that matches the ad. Do not send the click to a generic homepage if you are testing one promise. See the isolated funnel checklist before you paste.
Rules the agent must keep
- Read
https://adprimezero.com/docs,/docs/get-started, and/docs/quickstartbefore creating objects. - Run
npx -y ztdsp agent-guideornpx -y ztdsp agent-guide --jsonso the command list comes from the CLI, not from memory. - Create targeting through
ztdsp targeting createor the matching API. If you want segments, discover real catalog IDs first. Do not type a segment name and hope. - Submit creative through the public creative path. Include headline, description, click URL, expected content, and disclosure.
- Request a hosted prepay link with
ztdsp fundorPOST /account/prepay-link. Do not collect card numbers, bank details, or CVCs in chat. - Do not invent Beeswax numeric IDs. Use Adprime Zero IDs the API returns (
camp_,cr_, targeting IDs). If a call fails, stop and show the error. - Daily budget is $20. Do not raise it to make delivery look healthier.
- After launch, read performance with freshness fields. If spend exists and clicks are zero, inspect
freshness_statusand Beeswax reporting status before concluding there were no clicks. The reporting field isclicksplural.
Copy-paste prompt
Launch a $20/day Adprime Zero display test from this Cursor session.
Product:
- Signup: https://adprimezero.com/signup
- Docs: https://adprimezero.com/docs
- Get started: https://adprimezero.com/docs/get-started
- Agent quickstart: https://adprimezero.com/docs/quickstart
- API: https://adp-zero-api.adam-25a.workers.dev
Discover first:
- npx -y ztdsp agent-guide
- npx -y ztdsp agent-guide --json
- npx -y ztdsp --help
Do this work, in order:
1. Create or connect the account. Store ADP_ZERO_API_URL and ADP_ZERO_API_KEY only in the user's secret storage. Never print the key.
2. Collect launch inputs from me: landing URL, who should see the ad, geography, headline, description, image or source image, and the one promise the page must keep.
3. Create targeting with ztdsp targeting create or POST /targeting. If I ask for audiences, run ztdsp targeting discover-segments and use returned ids, not names. Show estimated data CPM before you attach a segment.
4. Pre-check the landing page, then submit creative with headline, description, click URL, expected content, and disclosure.
5. Create the campaign at $20/day. Name it so a stranger can read the stack (angle__targeting__inventory__pageTemplate__wave).
6. If the wallet cannot fund activation, request a hosted prepay link (ztdsp fund 50 --dollars --open or POST /account/prepay-link). Do not collect card data. Poll the funding intent after I finish the hosted page.
7. Review readiness. Activate only through the public campaign path when creative review, destination checks, and prepaid balance are ready.
Hard stops:
- Do not invent Beeswax campaign, line-item, or creative IDs.
- Do not write to Beeswax or the database directly.
- Do not embed API keys in landing-page tags.
- Do not raise the daily budget above $20 unless I say so.
- If impressions or spend exist and clicks are zero, run reporting status before you change targeting. Use the clicks plural field.
Report back with the Adprime Zero IDs you created, the funding-link status, and the next command I should run.