{"uid":"cap_ugDjzUNPcPbbj82l4QcsS","slug":"json-timestamp-fields-check-b64ccc1c","name":"JSON Timestamp Fields Check","description":"JSON Timestamp Fields Check: JSON Timestamp Fields Check checks selected fields as integer epoch seconds within bounds from bounded caller-supplied values without an external provider. Call JSON Timestamp Fields Check before an agent hands structured data or a batch plan to a downstream tool with a stricter contract. Returns the bounded transformation or validation finding with counts, normalized values, and a versioned result contract for JSON Timestamp Fields Check as versioned deterministic…","url":"https://api.delx.ai/api/v1/x402/json-timestamp-fields-check","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"fields":{"type":"array","items":{"type":"string","maxLength":8192},"maxItems":256,"description":"Fields supplied to JSON Timestamp Fields Check; used only for this bounded calculation and processed in memory without retention."},"object":{"type":"object","description":"Object supplied to JSON Timestamp Fields Check; used only for this bounded calculation and processed in memory without retention.","maxProperties":128,"additionalProperties":true},"maximum_epoch":{"type":"integer","description":"Maximum Epoch supplied to JSON Timestamp Fields Check; used only for this bounded calculation and processed in memory without retention."},"minimum_epoch":{"type":"integer","description":"Minimum Epoch supplied to JSON Timestamp Fields Check; used only for this bounded calculation and processed in memory without retention."}}},"responseSchema":{"type":"json","example":{"result":{"passed":true,"invalid_fields":[]},"schema":"delx/util-json-timestamp-fields-check/v1","status":"pass","evidence":{"retained":false,"input_sha256":"c12d2ec16714eac59b617fadcb92ec5fbee3fc2095362925f77691ae25cca0ee","external_calls":0},"operation":"data_batch:json_timestamp_fields_check"}},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.001","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.001/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.001","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.001","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_kOiNcaaYPVgvOC57PLklv","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.001","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Validates selected fields in a JSON object as integer epoch seconds, checking they fall within caller-supplied minimum and maximum bounds, and returns counts, normalized values, and a versioned result contract.","exampleAgentPrompt":"Before passing this order payload to the fulfillment API, check that the fields 'created_at' and 'expires_at' are valid integer epoch seconds between 1700000000 and 1800000000 — here's the object: {\"order_id\": \"abc\", \"created_at\": 1712345678, \"expires_at\": 1812345678}.","exampleUseCases":[{"title":"Pre-flight timestamp check for downstream API","prompt":"Before I send this event payload to the analytics pipeline, can you verify that the 'event_time' and 'received_at' fields are valid epoch seconds between 1600000000 and 1800000000? Here's the object: {\"event_id\": \"evt_001\", \"event_time\": 1712300000, \"received_at\": 1712300500}."},{"title":"Batch plan timestamp bounds validation","prompt":"I'm about to hand this batch job plan to the scheduler — can you check that 'start_epoch' and 'end_epoch' are both valid integer epoch seconds and fall between 1700000000 and 1750000000? Here's the plan object: {\"job_id\": \"job_42\", \"start_epoch\": 1710000000, \"end_epoch\": 1745000000}."},{"title":"Detecting out-of-range timestamps in user data","prompt":"Can you check whether the 'registered_at' and 'last_login' fields in this user record are reasonable unix epoch seconds — they should be between 1000000000 and 1800000000? Object is: {\"user_id\": \"u_99\", \"registered_at\": 1650000000, \"last_login\": 9999999999}."}],"resultDescription":"Returns a versioned deterministic result containing: validation finding (pass/fail per field), counts of valid and invalid fields, normalized epoch values for each checked field, and a versioned result contract describing the schema of the response.","failureModes":["Field names in 'fields' array do not exist in the provided object — fields will be counted as invalid or missing","Non-integer values in timestamp fields cause validation failures","minimum_epoch greater than maximum_epoch causes undefined or error response","Object exceeds maxProperties limit of 128 — request rejected","Fields array exceeds maxItems limit of 256 — request rejected","Network or payment failure returns HTTP 402 or connection error"],"whenToPreferThis":"Use this endpoint when you need a deterministic, bounded, in-memory check of integer epoch second timestamps across multiple fields of a JSON object before passing structured data to a downstream system with a strict contract. It is especially useful in agentic pipelines where you want a versioned, auditable validation result without retaining or externalizing the data. Prefer it over generic JSON schema validators when epoch-second bounds checking per named field is the specific requirement.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-15T01:07:57.894Z","isFirstParty":false}