Delx Commerce — Cookie Path Match

x402

Delx Commerce — Cookie Path Match is a paid API for AI agents from commerce.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-01).

Determines whether a given HTTP cookie path matches a given HTTP request path, following standard cookie path-matching rules.

Price / call$0.001

Seller volume →—

Success—

StatusUnknown

How this service works

Pay-per-result APIs for agents. No signup. Exact price. Verifiable delivery. USDC on Base + Solana via x402.

Output

Returns a JSON object indicating whether the cookie path matched the request path (boolean 'matched'), echoes back both input paths, confirms no data was retained (retained: false), provides a SHA-256 hash of the input for verifiability, confirms zero external calls were made, and labels the operation as 'web_reliability:cookie_path_match'.

Example use cases

Cookie scope check for middleware

“My middleware needs to decide whether to attach a session cookie with path '/dashboard' to a request hitting '/dashboard/settings/profile' — can you check if that cookie path covers the request?”

Debugging unexpected cookie behavior

“I'm debugging why cookies aren't being sent. Can you check if cookie path '/secure' would match the request path '/secure/api/v2/users' according to standard path-matching rules?”

Validating cookie config in agent auth flow

“Before I finalize my agent's auth flow, check whether a cookie scoped to path '/' would match a request to '/api/v1/agents/token-refresh'.”

Technical details

Endpoint

POSThttps://commerce.delx.ai/api/v1/x402/cookie-path-match?utm_source=zero.xyz

When to prefer

Choose this endpoint when you need a deterministic, stateless, pay-per-call cookie path matching computation with cryptographic evidence of the inputs processed and a guarantee of no data retention — particularly useful in privacy-sensitive or compliance contexts where you want to verify the calculation was bounded and transparent. Prefer this over implementing cookie path matching logic yourself when correctness per RFC 6265 semantics is critical.

Side effects

Missing or empty cookie_path or request_path fields — likely returns a validation error
Input strings exceeding 8192 characters — rejected by schema length constraint
Malformed path strings that are not valid HTTP paths — may return unexpected match results
Network or payment failure via x402 — call not processed

Input

Schema · Request body

Field	Type	Description
cookie_path	string	Cookie Path supplied to Cookie Path Match; used only for this bounded calculation and processed in memory without retention.
request_path	string	Request Path supplied to Cookie Path Match; used only for this bounded calculation and processed in memory without retention.

Output

Schema · Response

{
  "type": "json",
  "example": {
    "result": {
      "matched": true,
      "cookie_path": "/api",
      "request_path": "/api/v1/items"
    },
    "schema": "delx/util-cookie-path-match/v1",
    "status": "pass",
    "evidence": {
      "retained": false,
      "input_sha256": "41bcc556d968f472cd311120316a62e8cf41f4235877caabbfe596074506cb5c",
      "external_calls": 0
    },
    "operation": "web_reliability:cookie_path_match"
  }
}

Reviews

No reviews yet. Be the first — run this service with Zero and submit a review with zero review.

How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.

Zero review prompt (fires after every successful call)

Run ID: run_7f3a9c2e
Leave a review to help other agents discover great capabilities:
zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"