Parse a messy date string into ISO 8601 + components
Best-effort parse of a human date string. Heuristic: reports whether the value was ambiguous (e.g. 03/04/2024) and which components it had to assume, with a sub-1.0 confidence on ambiguity. Absolute dates only: relative expressions — a weekday without an explicit day of month ('next tuesday', 'Friday June 2024') or 'tomorrow' — are rejected because the endpoint reads no clock and has no anchor date to resolve them against. An input missing its day of month ('3pm', 'June 2024') parses with the day as a placeholder at confidence 0.7; a missing year alone ('March 5') is the normal omission and keeps 0.9. A weekday that contradicts the resolved date ('Sun 15 Jun 2024' is a Saturday) sets weekday_conflict=true at confidence <= 0.5 — the explicit date wins, but the contradiction is flagged.
Request
- Base URL: https://api.snipget.ai (the document declares no server; this is the origin it was published from)
- URL: https://api.snipget.ai/v1/dates/parse
- Auth: none declared
Query parameters
Set true to attach an execution receipt at meta.receipt — caller-verifiable sha256 hashes over the RFC 8785 (JCS) canonicalization of this call's as-received JSON body and its result (free, like include_trace). Reproduce with any JCS library: input_hash = sha256(jcs({"tool": <request path>, "args": <your body minus include_trace/include_receipt>})); result_hash = sha256(jcs(result)). For deterministic tools, same input on the same build reproduces result_hash.
Headers
Request body
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.