agent-launch.ai

Tony's AI agent deployment platform with blockchain tokenisation (Fetch.ai / FET).

Recommendation: WAIT (vertical risk + LP gap + audience mismatch)

Niche

B2B developer infrastructure + blockchain/crypto

Site

agent-launch.ai (currently a docs page, not marketing)

Stack

MCP Server, TypeScript SDK, CLI, REST API; deploys to BSC blockchain

Pricing model

120 FET deploy fee + 30,000 FET liquidity target

1. Vertical eligibility

RISK FLAG. The blockchain/crypto angle is in the gray zone of OpenAI's ad policy. The published exclusions cover "regulated financial services" plus "gambling" but don't explicitly list "crypto / blockchain / token sales" - this is exactly the kind of category that gets ad-platform policies tightened mid-test-phase.

Specific risk vectors:

FET token mention + "auto DEX listing" + "30,000 FET liquidity" reads as financial services / token sale promotion to a policy reviewer
"120 FET deploy fee" implies a paid-token product, which most ad platforms (Google, Meta) treat with elevated scrutiny
OpenAI's mover into ChatGPT ads is consumer-trust-conscious; crypto ad risk-weighting is likely higher than typical

Recommended: do NOT submit ads with crypto / token language. If agent-launch.ai keeps the developer-tooling positioning visible AND keeps the FET / blockchain angle out of the LP and ad creative, vertical risk drops materially. But that's a product positioning question, not just an ad question.

2. ICP fit scorecard

1/4

Total

PARTIAL

Vertical

FAIL

ChatGPT-tier overlap

FAIL

LP marketing readiness

1/4 ICP fit. The audience is the bigger problem than the vertical:

Developer + crypto ICP overlap with ChatGPT free-tier is very thin. Both populations skew heavily Plus/Pro (who do not see ads). Crypto power users in particular are technically sophisticated and pay for AI tools.
The site is documentation, not marketing. Even if traffic arrived, there is no conversion path. No hero CTA, no value-prop hierarchy, no trust signals.
The conversion event is unclear. Is it "deploy your first agent"? "Buy FET tokens"? "Sign up for the SDK"? Without a defined event, ad math doesn't compute.

3. Landing page scorecard

Check	Result	Note
OAIQ SDK installed	FAIL	Not installed.
Page LCP	VERIFY	Likely fine - documentation pages are typically lightweight.
Form / CTA above the fold	FAIL	Documentation page. Primary CTAs are technical install commands, not conversion CTAs.
Trust signals	FAIL	No marketing trust signals. Platform constants only.

0-1/4 landing page score. Worst LP score in the entire OO audit set. The site is technical reference material; it would need to become a marketing page before any ads run.

4. Budget simulator

Not computable without: defined conversion event, defined LTV, defined audience segment, marketing page existing. Returning to this calculation requires answers from Tony first.

5. The fundamental problem

OpenAI Ads is a research-stage consumer/SMB channel. agent-launch.ai is a technical infrastructure product targeting power users in two of the most paid-AI-tool-saturated audiences (developers + crypto). Even if vertical clears and LP gets built, the ICP overlap with ChatGPT free-tier users is structurally thin. This is not a budget problem or a creative problem - it is a channel-fit problem.

Better channel for agent-launch.ai is likely:

Developer-focused content marketing (X, Hacker News, dev newsletters)
Crypto-Twitter (X) where the FET / blockchain angle plays cleanly
Direct integration / partnership with existing Fetch.ai community channels

6. Recommendation

WAIT. agent-launch.ai is structurally a poor fit for OpenAI Ads as currently positioned.

Reasoning: 1/4 ICP fit. Vertical risk on crypto/blockchain language. LP is documentation, not marketing. Audience (developers + crypto power users) skews paid-AI-tier where ads don't show. Even if all three problems are solved, the channel-fit problem remains.

What changes the recommendation to GO: agent-launch.ai pivots to a non-crypto positioning targeting non-technical audience-builders OR crypto-curious newcomers (free-tier audience exists there); a real marketing page exists with defined conversion event and LTV; OpenAI policy clarifies that crypto-adjacent dev tools without token sale language are eligible.

7. Tony's better paid options to explore instead

X / Twitter ads - native crypto + dev audience, lower CPC, can lead with FET / blockchain angle.
YouTube preroll on AI / crypto channels - converts technical audience.
Sponsorships on dev newsletters (Bytes, JavaScript Weekly, AI Tidbits) and crypto Substacks.
Fetch.ai community channels directly - existing audience, native fit.

Recommendation: Tony focuses on X/dev-newsletter/crypto-Twitter channels. Revisit OpenAI Ads in 6 months if positioning + LP + policy all evolve