Audit cookie consent configuration API

Read cookie purpose, duration, and the consent state supplied by the caller. An optional cookie without an opt-in or opt-out state is reported. Consent is not enforced and the cookie is not classified by law.

The Audit cookie consent configuration operation is part of the Privacy Operations API on BRAINIAC.software. Read cookie purpose, duration, and the consent state supplied by the caller. An optional cookie without an opt-in or opt-out state is reported. Consent is not enforced and the cookie is not classified by law. It is exposed as POST /api/v1/privacy-operations/cookie-consent-configuration-audit and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Policies, notices, and records supplied in the request. Limitations: This is not a GDPR compliance determination or a legal conclusion. Categories, purposes, retention periods, and stated legal bases come only from labeled fields. Direct identifiers are not copied into the response. No external customer record is accessed or deleted. A missing item means it was not in the supplied documents. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Audit privacy policy structure, Extract a personal data inventory, Check stated retention periods, Compare a policy and a notice. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/privacy-operations/cookie-consent-configuration-audit

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/privacy-operations/cookie-consent-configuration-audit" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "cookies": [
    {
      "name": "session",
      "purpose": "sign in",
      "duration": "session",
      "consent": "required"
    },
    {
      "name": "analytics",
      "purpose": "measurement",
      "duration": "30 days",
      "consent": "optional"
    }
  ],
  "consents": [
    {
      "name": "analytics",
      "state": "not-set"
    }
  ]
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Privacy Operations APIFull docsHow it works