Your workflow. Your product. AdHalo image ads.
Product-photo image ads, from your own AI agent.
Connect your own AI agent with the Model Context Protocol (MCP). Let it find a product, preview an image batch and collect finished ads—with your actual product photo passed to the model as a reference.
Included with Starter, Pro and Studio. Uses your existing image allowance, not unlimited generation. Bring a client that supports a custom Authorization header; OAuth sign-in is not available.
From product photo to a reviewed image ad
1. Choose the product
Find an existing product and its photos, or allow your agent to import a product page. Product page text is untrusted data, not instructions.
2. Preview and approve
Ask for 1–3 unique image formats. Review the options and exact image allowance debit before an agent submits the approved batch.
3. Inspect and download
The agent checks the asynchronous jobs and collects fresh download links. Review the image, product details and copy before you use it.
A prompt you can adapt
“Find my product and check my image allowance. Use its product photo to preview two image ads, square and vertical. Show me the options and exact debit before submitting. Once approved, use a stable retry key and retrieve the finished files for my review. Do not publish anything.”
This is a workflow example, not a guarantee that your agent pauses for human review. Only give generation permission to an agent you trust.
A small connection, with permissions you choose
Sign in and open Integrations → Connect your agent. Create a read-only key, optionally permit product imports or image generation, then configure your client's secret store. Keys default to seven days, can expire after 1–90 days, and can be revoked any time. Ten active keys per account.
- Streamable HTTP endpoint
- https://adhalo.app/api/mcp
- Custom header
- Authorization: Bearer ah_agent_YOUR_KEY
The full key is shown once. Keep it out of prompts, URLs, Git and shared chats. Client configuration varies; use the technical guide for approval fields, retry behavior and rate limits.
Exactly eight tools. No hidden publishing.
get_allowance
read permission
Check your plan, remaining image and video allowance, and reset dates.
list_products
read permission
Find your first 50 products and their reference photos.
get_product
read permission
Read one of your products and its photos.
list_ads
read permission
Find your image and video ads and check their job status.
get_ad
read permission
Check a job and get a fresh, expiring download link when ready.
import_product
edit permission
Import a product page and actual product photos. This does not generate ads.
preview_image_generation
generate permission
Validate the image batch and show its exact allowance debit without rendering.
generate_image_ads
generate permission
Submit the approved image batch, then check its asynchronous jobs.
Image batches only: no video generation, angle packs or grids. Existing video ads can be read and downloaded. No publishing, deletion, billing, account administration or key creation through MCP.
Allowance, approval and connection questions
Does agent access cost extra?
MCP access is included with Starter, Pro and Studio; there is no separate MCP subscription. Image generation uses the same image allowance as the web app. Each unique format costs one image from your allowance, with 1–3 formats per batch. A preview generates nothing and reserves nothing; it is not a dollar-price quote. Your agent's own service may charge separately.
Will the agent use my actual product photo?
Yes. AdHalo passes your product photo as a reference to the image-generation model, rather than relying only on a text description. Use a clear, accurate photo and inspect the finished ad: AI can still alter packaging, logos or other details. This does not guarantee exact product fidelity.
Which clients can connect?
Use your own Streamable HTTP MCP client that supports a custom Authorization header. AdHalo does not provide OAuth sign-in, and a client without custom-header support cannot use this connection. Configuration differs between clients; no specific vendor compatibility is promised.
Can an agent spend my allowance without my permission?
Keys are read-only by default. You may grant import or image-generation permission separately. Generation requires a preview hash, approved=true, a maximum image debit and a stable retry key. Approval records the agent's intent, not proof that a human reviewed it, so grant generation only to an agent you trust. Existing plan, moderation and spend gates still apply.
What happens if my agent retries?
Keep the same idempotency key and identical inputs for the same submission. Completed submissions replay the original response and job ids rather than generating another batch. Pending or uncertain submissions are not rerun: inspect list_ads instead of using a new key. A new batch needs a fresh preview when the product or subscription cycle changes.
Can I generate videos or publish ads through MCP?
No. MCP generates normal image batches only, not video, angle packs or grids. It can read your existing image and video ads and retrieve ready downloads. It cannot publish, delete content, manage billing, administer accounts or create keys. The standard image-only trial rules still apply; paid plans do not make unsupported tools available.