# Yieldmo

> Yieldmo is a programmatic native advertising marketplace and smart exchange, founded 2012 and headquartered in New York, operating as a supply-side platform (SSP) connecting premium publishers with advertisers across Display, Native, High-Impact, Video and CTV formats. Its YMax platform applies machine learning and attention analytics to inventory curation, contextual targeting and creative optimization.

Generated by API Evangelist from the artifacts in this repository. Yieldmo publishes no llms.txt of its own (https://yieldmo.com/llms.txt returns a robot-challenge shell; https://api.yieldmo.com/llms.txt and https://ads.yieldmo.com/llms.txt both return 404), so this file is generated, not harvested.

## APIs

- [Yieldmo DCS reporting API (MCP)](https://api.yieldmo.com/dcs/mcp): OAuth-protected campaign reporting and analytics over YMax exchange data. 19 read-only operations covering campaign performance, daily spend, creative performance, URL quality, audience segments, browser topics and advertiser attribution. Served as both an MCP server and a REST API by one FastAPI application.
- [Yieldmo JavaScript SDK](https://github.com/yieldmo/yieldmo-js-sdk/wiki): Publisher-side ad placement SDK. `window._ym.requestPageView([placementId])` requests new ads for placements already on the page, for single-page apps and infinite scroll.
- [Yieldmo Prebid.js Bid Adapter](https://docs.prebid.org/dev-docs/bidders/yieldmo.html): Header bidding adapter, biddercode `yieldmo`, banner and video, IAB GVL ID 173. Both Prebid.js and Prebid Server.
- [Yieldmo Synthetic Inventory Module](https://docs.prebid.org/dev-docs/modules/yieldmoSyntheticInventoryModule.html): Prebid.js module that creates a placement and injects the Yieldmo SDK for Synthetic Outstream ads via Google Ad Manager.

## Specs

- [OpenAPI 3.1.0 — DCS reporting API](openapi/yieldmo-dcs-mcp-openapi.json): 27 paths, 19 business operations. Captured verbatim from https://api.yieldmo.com/dcs/mcp/openapi.json.
- [MCP server manifest](mcp/yieldmo-mcp.yml): endpoint, OAuth model, and the 19-tool surface derived from the co-served OpenAPI.
- [Tool crosswalk](mcp/yieldmo-tool-crosswalk.yml): each MCP tool bound to its backing REST operationId.
- [Authentication profile](authentication/yieldmo-authentication.yml): OAuth 2.0 authorization code against Amazon Cognito (`yieldmo-cuba`).
- [OAuth scopes](scopes/yieldmo-scopes.yml): `openid`, `profile`, `email` — no provider-defined resource scopes.
- [Well-known index](well-known/yieldmo-well-known.yml): RFC 8414, RFC 9728 and OIDC discovery documents on api.yieldmo.com.
- [Conventions](conventions/yieldmo-conventions.yml): pagination, date-key encoding, KPI vocabulary, versioning, error envelopes.
- [Error catalog](errors/yieldmo-problem-types.yml): the three error envelopes served from one host.
- [Data model](data-model/yieldmo-data-model.yml): 12 entities, 12 relationships derived from identifier parameters.
- [Conformance](conformance/yieldmo-conformance.yml): OpenAPI 3.1, MCP, OAuth 2.0, RFC 8414/9728/7591, OpenRTB 2.5, IAB TCF/GPP/USP/schain, MRAID 2.0.
- [Lifecycle](lifecycle/yieldmo-lifecycle.yml): no versioning, no deprecation policy, no status page, no changelog.
- [Packages](packages/yieldmo-packages.yml): Prebid adapter, Android `ym:ymsdk` 4.1.3 (2017), iOS `YieldmoSDK` 4.2.5 (2017), CDN JS SDK.
- [Agent skills](skills/_index.yml): packaged operating instructions grounded in real operationIds.
- [Domain security](security/yieldmo-domain-security.yml): TLS, HSTS, DNSSEC, CAA, SPF, DMARC probes.

## Auth

- Authorize: https://yieldmo-cuba.auth.us-east-1.amazoncognito.com/oauth2/authorize
- Token: https://yieldmo-cuba.auth.us-east-1.amazoncognito.com/oauth2/token
- Protected resource metadata: https://api.yieldmo.com/.well-known/oauth-protected-resource
- Authorization server metadata: https://api.yieldmo.com/.well-known/oauth-authorization-server
- Scopes: `openid`, `profile`, `email`. No read/write or per-advertiser scopes exist.

## Docs

- Website: https://yieldmo.com
- YMax platform: https://yieldmo.com/solutions/
- Technology: https://yieldmo.com/technology/
- Console / login: https://apps.yieldmo.com/auth
- Creative format gallery (AdBuilder): https://formats.yieldmo.com/
- Blog: https://yieldmo.com/category/blog/
- GitHub: https://github.com/yieldmo
- Privacy policy: https://yieldmo.com/privacy-policy/
- Ad policy: https://yieldmo.com/adpolicy/
- Processor list: https://yieldmo.com/processor-list/
- Opt out: https://yieldmo.com/opt-out/
- Support: support@yieldmo.com — Sales: info@yieldmo.com

## Known gaps

- The DCS reporting API and its MCP server are live but undocumented: no reference page, no announcement, no llms.txt, and the host (api.yieldmo.com) is not linked from anywhere public.
- The OpenAPI declares no securitySchemes, no tags, no response schemas and no examples, so an agent cannot know a report's shape before calling it.
- The `WWW-Authenticate` challenge advertises a `resource_metadata` URL (`/.well-known/oauth-protected-resource/dcs/mcp`) that returns 404.
- yieldmo.com and www.yieldmo.com return HTTP 202 robot-challenge shells to every non-browser client, so the marketing and policy surface is not machine-readable.
- No status page, no changelog, no versioning scheme, no security.txt, no A2A agent card.