Availability and capabilities
SDK source exists for all nine runtimes below. Experimental is the audit classification until installation, device rendering and production eligibility are verified. A published package alone does not establish general availability.
Evidence reviewed on . Release classifications reflect this audit. Account eligibility, support commitments and device-specific production validation remain subject to review.
SDK runtime matrix
| Runtime | Status | Public distribution | Rendering and limits |
|---|---|---|---|
Web / JavaScript@theaimart/adx-web · 1.0.0 | Experimental | Not verified | Image banners and sandboxed HTML; separate VAST helper in source. Browser requests require an approved origin. The checked contract records a first-party CORS limitation; confirm your domain before live requests. |
Node.js@theaimart/adx · 1.0.0 | Experimental | Verified · Registry | Server-side request and HTML helper; host application controls display and viewability. Forward the end user’s real User-Agent and IP, with a separate identity cookie per user. Do not report viewability on receipt of a server response. |
Pythontheaimart-adx · 1.0.0 | Experimental | Verified · Registry | Server-side request and HTML helper; optional Flet, Kivy and Streamlit adapters. GUI adapters depend on host framework setup. Forward each end user’s identity and measure actual visibility. |
Rusttheaimart-adx · 1.0.0 | Experimental | Verified · Registry | Server-side request and HTML helper. Host application owns the renderer and visibility measurement. Forward per-user identity when proxying requests. |
React Native@theaimart/adx-react-native · 1.0.0 | Experimental | Not verified | Banner component; HTML depends on a configured WebView. Native device rendering and public installation have not been verified. Runtime dependencies must be tested on each target device. |
Android / Kotlinco.theaimart:adx-android · 1.0.0 | Experimental | Not verified | BannerAdView source for images and WebView creatives. Android build, device behavior and production eligibility remain unverified. |
iOS / SwiftTheaimartAdx · 1.0.0 | Experimental | Not verified | UIKit BannerAdView source and WKWebView creatives. Requires an Apple build environment. Public package access, device rendering and production eligibility remain unverified. |
Flutter / Darttheaimart_adx · 1.0.0 | Experimental | Verified · Registry | BannerAd images; HTML requires an application-provided htmlBuilder. Test click navigation and HTML rendering for each target platform. Publication does not verify every desktop or mobile runtime. |
Unity / C#co.theaimart.adx · 1.0.0 | Experimental | Not verified | AdxBanner image path; HTML needs an application-provided renderer. Unity editor build, renderer integration and production eligibility remain unverified. |
Browser tags
The backend repository includes adx.js and adx-lite.js. Their availability is Experimental in this audit. Confirm the deployed script and approved publisher origin before use. Initialize only after the script load event, and measure rendering and viewability in the host page.
Ad formats by runtime
Banner and image creative paths exist in the SDK source. Native and interstitial presentation need runtime-specific integration. Video uses a separate VAST path with a Web playback helper; rewarded delivery and reward verification are not established for all SDKs.
- Web source: image banners and sandboxed HTML; separate VAST playback helper. Browser origin approval is required.
- Node, Python and Rust: requests and HTML helpers. The host application must render and measure visibility; a server request cannot prove a viewable impression.
- React Native, Android and iOS: banner renderer source. Device builds and HTML/WebView configuration require target-runtime testing.
- Flutter and Unity: image banner source. HTML requires a host-provided renderer; test each platform before release.
- Rewarded: do not promise rewards or paid delivery until demand, reward validation and policy controls are verified.
Product capability evidence
Partially verified means implementation source was inspected, with live configuration, coverage or operational behavior still unverified. Unsupported means evidence for the stated public promise was not supplied.
| Capability | Evidence status | Interpretation |
|---|---|---|
| 180+ country demand | UNSUPPORTED | Inventory and market availability are determined during onboarding; geographic demand is not guaranteed. |
| Higher eCPMs | UNSUPPORTED | Revenue depends on valid demand, traffic quality, placements and applicable fees. An ad request or house ad is not proof of a paid impression. There is no verified evidence that ADX earns more than another network. |
| Higher fill rates | UNSUPPORTED | Fill depends on demand, eligibility and request context; no-fill is a normal outcome. |
| Real-time bidding | PARTIALLY VERIFIED | The backend includes real-time auction logic; available demand must be confirmed. |
| OpenRTB interoperability | PARTIALLY VERIFIED | OpenRTB routes exist in source. Partner compatibility and buying access require integration review. |
| Header bidding | PARTIALLY VERIFIED | The publisher interface includes an OpenRTB connection workflow. Do not assume a certified Prebid adapter or active demand connection. |
| Private marketplace deals | PARTIALLY VERIFIED | Private-deal controls exist in source; buyer participation and operational availability need confirmation. |
| ML fraud filtering | PARTIALLY VERIFIED | Invalid-traffic filtering exists in backend source. Its live efficacy and model configuration are not independently measured. |
| Fraud refunds | PARTIALLY VERIFIED | Refund handling exists in source; amounts, eligibility and timing depend on validated traffic and policy. |
| Public Merkle logs | PARTIALLY VERIFIED | Merkle log implementation exists. Live completeness and independent inclusion verification remain unverified. |
| Ed25519 auction receipts | PARTIALLY VERIFIED | Signed-receipt implementation exists; availability depends on backend configuration and the event path. |
| Yield optimization | PARTIALLY VERIFIED | Yield controls exist; no increase in revenue is promised. |
| Dynamic floors | PARTIALLY VERIFIED | Floor controls exist in source. Live optimizer cadence and effectiveness need verification. |
| Audience revenue sharing | PARTIALLY VERIFIED | A reader-share implementation exists. Do not enable or promote rewards without eligibility, anti-incentive and policy review. |
| Smart bidding / tCPA / tROAS | PARTIALLY VERIFIED | Bidding strategies exist in code; delivery performance and access require validation. |
| Brand safety | PARTIALLY VERIFIED | Brand-safety controls exist; they are not a guarantee that every placement is suitable. |
| Behavioral targeting | PARTIALLY VERIFIED | Audience and retargeting code exists; consent, eligibility and account access constrain use. |
| Contextual targeting | PARTIALLY VERIFIED | Contextual matching exists in source; actual inventory and campaign access require review. |
| Frequency caps and pacing | PARTIALLY VERIFIED | Frequency-cap and pacing controls exist. Identity persistence and live enforcement need integration testing. |
| Real-time reporting | PARTIALLY VERIFIED | Reporting screens and endpoints exist. Data freshness and financial settlement are separate. |
| Conversion attribution | PARTIALLY VERIFIED | Conversion endpoints exist. Observed conversions are not evidence of campaign profitability. |
| Publisher payout schedule | OWNER CONFIRMATION REQUIRED | Payout eligibility depends on verified earnings, account review, supported payment methods and current terms. Check the transparency feed and your dashboard for the applicable threshold. No payment timing or earnings level is guaranteed. |
| Minimum payout | PARTIALLY VERIFIED | The public feed reports a configured minimum when available. Actual payout eligibility is subject to current terms and account review. |
| Instant payouts | OWNER CONFIRMATION REQUIRED | Payment processing times depend on review and the payout provider; instant payment is not guaranteed. |
| Supported inventory countries | OWNER CONFIRMATION REQUIRED | Confirm eligible markets and inventory during onboarding. |
| Actual advertiser demand sources | OWNER CONFIRMATION REQUIRED | Responses distinguish internal, OpenRTB and house paths. No partner or delivery volume is promised. |
Safe testing and eligibility
Start with local mocks or a confirmed sandbox workflow. A normal production serve request can create billing and identity side effects. Registration and package installation do not authorize paid traffic. Read the terms, privacy policy and SDK safety requirements.
Machine-readable reference: capability manifest. For requests and errors, see the wire contract and troubleshooting guide.