generated: '2026-08-12'
method: generated
source: openapi/ (7 harvested Sourcepoint OpenAPI documents) + conventions/, errors/, authentication/
skills:
- name: sourcepoint-dsar-consent-erasure
  file: sourcepoint-dsar-consent-erasure.md
  description: Erase one end-user's consent and preference records across every Sourcepoint regulatory
    surface for a property, as part of a data subject erasure request.
  operations:
  - deleteGdprTcfConsent
  - deleteGdprStandardConsent
  - deleteUsnatConsent
  - deleteGlobalEnterpriseConsent
  - deletePreferencesHistory
- name: sourcepoint-consent-status-lookup
  file: sourcepoint-consent-status-lookup.md
  description: Read one end-user's current or historical consent state for a property on whichever regulatory
    surface applies.
  operations:
  - getGdprTcfConsentHistory
  - getGdprStandardConsentHistory
  - getUsnatConsentHistory
  - getGlobalEnterpriseConsentHistory
  - getPreferencesHistory
- name: sourcepoint-tcf-vendor-list-audit
  file: sourcepoint-tcf-vendor-list-audit.md
  description: 'Audit a property''s vendor list: vendors, vendor-to-purpose legal-basis mapping, and content
    URL to vendor resolution.'
  operations:
  - getGdprTcfVendors
  - getGdprTcfVendorPurposeMapping
  - postGdprTcfVendorUrlMapping
  - getGdprStandardVendorPurposeMapping
  - postGdprStandardVendorUrlMapping
- name: sourcepoint-usnat-opt-out
  file: sourcepoint-usnat-opt-out.md
  description: Server-side opt an end-user out of every U.S. Multi-State Privacy choice and vendor, and
    know when that does not reach the browser.
  operations:
  - postUsnatRejectAll
  - getUsnatConsentHistory
- name: sourcepoint-consent-dashboard-reporting
  file: sourcepoint-consent-dashboard-reporting.md
  description: Pull dashboard pageview/user and consent-message metrics for a property and period using
    the X-API-KEY reporting API.
  operations:
  - postGdprPageviewReport
  - postGdprMessageReport
  - postUsnatPageviewReport
  - postUsnatMessageReport
notes:
- Sourcepoint publishes no AGENTS.md or provider-authored skills; these are generated by API Evangelist
  from the harvested specs.
- Every operationId referenced is assigned by overlays/sourcepoint-*-overlay.yaml because the published
  specs carry no operationIds. The HTTP method and path in each skill are quoted verbatim from the spec.