This page answers the most common questions developers and integrators ask about using the ad generation SDKs and API.
Our platform generates intelligent, context-aware ads for chat applications and websites. You send us the chat history or web page content, and we return the most relevant ad — in JSON, HTML, or JavaScript format.
Any registered developer or partner who has an `apiId` and `apiKey`. These credentials are required for all API calls and SDK functions.
Please contact support for pricing and usage limits. A free tier may be available for small or personal projects.
We currently provide SDKs for:
No. Just send messages using your existing format. Our backend uses AI to extract structure and understand meaning.
In React, you can wrap your own chat component in our `<SendChatHistory>` tag — we handle the rest.
→ See Ad Formats for examples.
Yes. For HTML formats, ads use CSS classes like `.ad-box`, `.ad-text`, `.ad-label`, etc. You can override these with your own styles.
Only when you explicitly call `renderAdIntoElement(…)`. Otherwise, it returns content and lets you insert it manually.
No. Never. Chat history and page content are used once to generate the ad and then discarded immediately. → See Security Considerations for full policy.
Yes. Use the Go SDK or a server-side proxy. Never expose your `apiKey` in public JavaScript unless you're in a controlled environment.
All SDKs return standard errors:
You can handle fallbacks or show no ads as appropriate.
At the moment, the API is cloud-based only. If you have specific hosting or compliance requirements, contact support.
Yes, most HTML/JS formats already include click tracking. For custom formats, you're responsible for invoking the click URL.
If you're unsure about anything or need help integrating:
→ Getting Started → API Reference → SDKs