# Lookproof Cookie Header Parser

> Lookproof Cookie Header Parser is a paid API for AI agents from api.lookproof.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-31).

Parses a raw Set-Cookie header string according to RFC 6265bis, validating Secure, HttpOnly, SameSite, Partitioned, __Host- and __Secure- prefixes, Domain, Path, Expires, and Max-Age (with the 400-day cap), returning attribute analysis but never the cookie value itself.

## Facts

- Endpoint: POST https://api.lookproof.dev/v1/http/cookie-parse?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lookproof-cookie-header-parser-ca194266
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9sOdlkFAFN1-pc4p6YTRr

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability lookproof-cookie-header-parser-ca194266 -d '<json body>'
```

Example prompt: Can you parse this Set-Cookie header and tell me if it's correctly configured according to RFC 6265bis? The header is: __Host-sid=abc123; Path=/; Secure; HttpOnly; SameSite=Lax

## When to prefer this

Use this endpoint when an AI agent needs to audit, debug, or validate a Set-Cookie header for RFC 6265bis compliance — especially when security attributes like __Host-/__Secure- prefixes, SameSite, Partitioned (CHIPS), or Max-Age cap adherence are in question. It is privacy-safe because the cookie value is never echoed back. Prefer it over generic HTTP parsers when you need authoritative prefix-rule validation or the 400-day cap check in an offline, single-call operation.

## Known failure modes

- Empty or missing header field returns a validation error
- Header string exceeding 8192 characters is rejected
- Malformed or entirely unparseable header may return a parse error with no attribute breakdown
- Network or service availability issues return HTTP 5xx errors
- Payment failure via x402 protocol blocks the request

## How this service works

Check SPF, DMARC, DKIM, MTA-STS, DNSSEC and more, with results that explain what was found and why. Free browser checks and a pay-per-request API with x402.

## Output

A structured breakdown of every attribute found in the Set-Cookie header — including Secure, HttpOnly, SameSite value, Partitioned, Domain, Path, Expires datetime, and Max-Age (flagged if it exceeds the 400-day RFC cap). __Host- and __Secure- prefix rule compliance is reported. The cookie value itself is never returned, only its character length. Any RFC 6265bis violations or warnings are listed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "header": {
   "type": "string",
   "title": "Header",
   "maxLength": 8192,
   "minLength": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lookproof-cookie-header-parser-ca194266/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.lookproof.dev](https://www.zero.xyz/host/api.lookproof.dev/llms.txt)