Native Ads Publisher API

{
  "service_type": "platform",
  "base_url": "https://nativeads.com",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "notes": "Native Ads operates a self-serve DSP for native and display advertising. Pricing is likely based on ad spend / auction-based buying, but exact terms are not exposed on the public homepage."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Native advertising campaigns",
    "Display advertising campaigns",
    "Self-serve DSP (demand-side platform)",
    "Native and display ad exchange access",
    "Audience targeting / performance marketing",
    "Campaign creation and management via GUI",
    "Publisher API (per description) mirroring Publisher Account GUI functionality",
    "Analytics / reporting (via AAS tag and platform dashboards)",
    "Brand and performance marketing campaign support",
    "Mobile ad and video ad formats referenced"
  ],
  "raw_analysis": "Native Ads Inc. (nativeads.com) operates an ad tech platform, specifically a self-serve DSP for buying native, display, and related advertising inventory. The homepage positions the product for advertisers, brand marketers, and performance marketers, with language covering native ad exchange, mobile ads, video advertising, and conversions/lead generation. The described 'Native Ads Publisher API' is stated to expose the same functionality as the Native Ads Publisher Account GUI, which implies the platform supports two sides: advertisers (DSP) and publishers (supply side). The public HTML provided is purely marketing/landing page markup, not API documentation. It includes extensive third-party tracking scripts (Google Analytics, Google AdServices remarketing, Bing UET, Facebook Pixel, LinkedIn Insight, Yahoo DOT, and a custom 'aka' analytics pixel at static-analytics.nativeads.com). No API endpoints, authentication scheme, request/response schema, rate limits, or SDK references are present in the provided content. The platform appears mature in the ad tech space (operating since at least 2014 based on Google Analytics UA-53861296-1 timeline signals). Integration maturity on the public web surface is limited to marketing tags; developer-facing API documentation would need to be obtained from an authenticated dashboard, developer portal, or support contacts. Pricing is not publicly specified; as a DSP it is likely spend-based or auction-based rather than subscription-tiered, though this is unconfirmed. Overall, this should be treated as a mature ad-tech platform (not a generic SaaS tool) whose API surface is private/account-gated rather than publicly documented."
}

3/3 tests passed

{
  "overall": 48,
  "dimensions": {
    "token_efficiency": 6.0,
    "first_try_success": 5.0,
    "response_parseability": 3.0,
    "error_clarity": 4.0,
    "doc_quality": 4.5,
    "auth_simplicity": 5.0,
    "latency": 9.0,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "model": "auction_based_ad_spend",
    "public_price": "unknown",
    "note": "Self-serve DSP — likely auction-based ad spend with no public rate card."
  },
  "issues": [
    "robots.txt and llms.txt endpoints return the HTML homepage instead of respective files — no machine-readable directives.",
    "No security headers (HSTS, CSP, X-Content-Type-Options) detected on responses.",
    "Pricing model not exposed publicly; agents cannot advise users on cost.",
    "No API documentation or structured developer resources surfaced in checks.",
    "Marketing-heavy homepage; parsing yieled only high-level capability keywords, not concrete endpoints or schemas."
  ],
  "recommendations": [
    "Publish a real robots.txt and llms.txt so agents and crawlers can index structure properly.",
    "Expose public API docs / OpenAPI spec for the DSP to enable agent-driven campaign operations.",
    "Add a public pricing or spend-range page (even ranges or min budgets) so agents can qualify users.",
    "Add security headers (HSTS, CSP) for trust signals used by automated audits.",
    "Provide structured JSON for pricing, capabilities, and onboarding to improve parseability."
  ]
}