# AdReady (CPXi) / Digital Remedy

> Digital Remedy operates an omnichannel advertising management platform — marketed as the Digital
> Remedy Platform and historically as AdReady+ — for independent agencies, brands and media companies.
> It covers media planning, RFPs, insertion-order and line-item management, programmatic / CTV / DOOH /
> social execution, pixel-based attribution (Flip), incrementality and brand-lift measurement, and
> white-label reporting. AdReady began as a Seattle self-serve ad-building tool, was acquired by CPXi
> in 2013, and is today part of Digital Remedy, which has since combined with Compulse.

This file is generated by API Evangelist. Digital Remedy publishes no llms.txt of its own
(https://www.digitalremedy.com/llms.txt returns 404) and no developer portal.

## What an agent should know first

- **There is a real, current OpenAPI 3.1 description and it is public.** It is served anonymously at
  https://platform.digitalremedy.com/v3/api-docs with a Swagger UI at
  https://platform.digitalremedy.com/swagger-ui.html — 285 paths, 355 operations, 285 schemas.
- **The API itself is not open.** It is the first-party backend of Digital Remedy's own web
  application. There is no developer program, no public sign-up, no pricing, and no documentation
  beyond the generated Swagger UI. Every business operation returns HTTP 401 without a session.
- **Credentials are provisioned by Digital Remedy**, obtained through
  https://www.digitalremedy.com/contact-us/ — not by self-service registration.
- **Do not treat this API as automatable without a contract with the vendor.** It has no idempotency
  keys, no rate-limit signalling, no problem-details errors and no deprecation policy.

## APIs

- [Digital Remedy Platform (Kickstart) API](https://platform.digitalremedy.com/swagger-ui.html):
  base https://platform.digitalremedy.com — accounts, organizations, agencies and advertisers; users
  and permissions; media plans, insertion orders, line items and budget groups; rate cards, media
  publishers, publisher deals and segments; Flip attribution pixels; incrementality and performance
  reporting; App Console solution/brand/search/social/Converged TV management; white-label domains;
  and embedded Tableau / ThoughtSpot analytics tokens.

## Specs

- [OpenAPI 3.1 (refined)](openapi/adready-cpxi-kickstart-openapi.yml)
- [OpenAPI 3.1 (verbatim as harvested)](openapi/_original/adready-cpxi-kickstart-openapi.json)
- [OpenAPI Overlay — API Evangelist annotations](overlays/adready-cpxi-kickstart-overlay.yaml)

## Runtime semantics

- [Authentication](authentication/adready-cpxi-authentication.yml) — session JWT from
  `POST /api/auth/login`; the spec declares no securitySchemes at all.
- [Conventions](conventions/adready-cpxi-conventions.yml) — `ApiResponse {status, message, result}`
  envelope; offset pagination via `pageNumber` / `perPage` / `sortKey` / `sortOrder`; **no
  idempotency**; no request-id header.
- [Error catalog](errors/adready-cpxi-problem-types.yml) — not RFC 9457; the 401 returns an empty body
  with no `WWW-Authenticate` challenge.
- [Rate limits](rate-limits/adready-cpxi-rate-limits.yml) — none published, none signalled.
- [Data model](data-model/adready-cpxi-data-model.yml) — 86 id-bearing entities, 222 derived
  relationships; Account, Advertiser, Plan, LineItem and User are the hubs.
- [Lifecycle](lifecycle/adready-cpxi-lifecycle.yml) — unversioned paths; running build 3.5.6
  (2026-08-04); no deprecation policy, no SLA, no status page.
- [Agentic access recommendations](agentic-access/adready-cpxi-agentic-access.yml)

## Agent surfaces

- **MCP**: none published. A [candidate tool list](mcp/adready-cpxi-mcp.yml) is derived from the spec.
- **A2A agent card**: none. `/.well-known/agent-card.json` and `/.well-known/agent.json` were probed on
  all three hosts and none served a card.
- **Well-known**: [nothing served](well-known/adready-cpxi-well-known.yml) — 24 paths probed, 0 documents.
- [Agent skills](skills/_index.yml) — generated operating instructions grounded in real operationIds.

## Security and compliance

- [Trust center](security/adready-cpxi-trust-center.yml) — https://trust.digitalremedy.com/, SOC 2.
- [Domain security](security/adready-cpxi-domain-security.yml) — TLS 1.3 on both hosts; HSTS on the
  platform host only; no DNSSEC, no CAA; SPF and DMARC published (policy `quarantine`).
- [Conformance](conformance/adready-cpxi-conformance.yml)
- No security.txt, no published vulnerability disclosure policy, no bug bounty.

## Company

- [Platform](https://www.digitalremedy.com/platform/)
- [About](https://www.digitalremedy.com/about/)
- [Blog](https://www.digitalremedy.com/blog/)
- [Contact](https://www.digitalremedy.com/contact-us/)
- [Terms and conditions](https://www.digitalremedy.com/terms-and-conditions/)
- [Privacy policy](https://www.digitalremedy.com/privacy-policy/)
- [Login](https://platform.digitalremedy.com/)