WritersLogic Verifiable AI Agent Hub Naive Timestamp Hazard API
The Naive Timestamp Hazard API from WritersLogic Verifiable AI Agent Hub — 1 operation(s) for naive timestamp hazard.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/writerslogic-com:writerslogic-com-naive-timestamp-hazard-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: WritersLogic Verifiable AI Agent Hub Naive Timestamp Hazard…
version: 2.0.0
description: Pay-per-call agents settled in USDC on Base via x402. Every response carries a signed provenance envelope.
contact:
name: WritersLogic
url: https://writerslogic.com/agents
email: agents@writerslogic.com
servers:
- url: https://agents.writerslogic.com
tags:
- name: Naive Timestamp Hazard
paths:
/api/v1/naive-timestamp-hazard:
post:
operationId: naive_timestamp_hazard
summary: Which timestamps are anchored?
description: 'Classifies up to 200 timestamp strings as anchored (RFC 3339 with Z or offset), naive local (no offset), date-only, epoch seconds or milliseconds, zone abbreviation, ambiguous numeric date, or unparseable, and lists the hazard of each; with assumedTimeZone it also reports whether a naive time falls in a DST gap or overlap there, every instant it could mean, and offsets that contradict the zone. Built for an agent about to store, compare or schedule timestamps it was handed. It reports hazards and candidates; it never picks a zone for you and never reads the clock.
Price: 0.005 USDC on Base (x402).'
x-x402-price-usdc: '0.005'
x-x402-amount: '5000'
x-payment-info:
protocols:
- x402
price:
mode: fixed
currency: USD
amount: '0.005'
x-audience: business
x-sample-url: https://agents.writerslogic.com/api/v1/samples/naive-timestamp-hazard
security:
- x402: []
- apiKey: []
requestBody:
required: true
content:
application/json:
schema:
type: object
additionalProperties: false
required:
- timestamps
properties:
timestamps:
type: array
minItems: 1
maxItems: 200
items:
type: string
maxLength: 64
assumedTimeZone:
type: string
pattern: ^[A-Za-z][A-Za-z0-9_+-]*(/[A-Za-z0-9_+-]+){0,2}$
maxLength: 64
description: IANA zone the producer is believed to use; used for gap/overlap and offset-consistency checks.
example:
timestamps:
- '2026-03-08T02:30:00'
- '2026-07-01T12:00:00+01:00'
- 03/04/2026
- '1793836800'
assumedTimeZone: America/New_York
responses:
'200':
description: Paid result with provenance
content:
application/json:
schema:
type: object
properties:
data:
type: object
properties:
status:
type: string
enum:
- pass
- fail
- unknown
- unsupported
description: 'pass: every rule held. fail: a rule was violated (see witnesses). unknown: the input lacks the evidence to decide. unsupported: outside what this engine covers. Missing evidence is never a pass.'
items:
type: array
items:
type: object
properties:
index:
type: integer
input:
type: string
kind:
type: string
enum:
- anchored
- naive-local
- date-only
- epoch-seconds
- epoch-millis
- ambiguous-numeric-date
- zone-abbreviation
- unparseable
hazards:
type: array
items:
type: string
instantUtc:
type: string
candidatesUtc:
type: array
items:
type: string
offsets:
type: array
items:
type: string
anchoredCount:
type: integer
witnesses:
type: array
items:
type: object
properties:
ruleId:
type: string
detail:
type: string
path:
type: string
description: JSON pointer or dotted path into the input.
offset:
type: integer
index:
type: integer
expected:
description: What the rule required.
actual:
description: What the input had.
versions:
type: object
description: Every semantic dependency of this answer (engine, tables and their as-of dates, tokenizer, calendar, rounding profile).
limits:
type: array
items:
type: string
deterministic:
type: boolean
description: 'Always true: pure code, no model.'
_provenance:
type: object
description: C2PA-aligned manifest and W3C VC 2.0 (eddsa-jcs-2022) issued by the hub DID; verify at POST /api/v1/verify-provenance
required:
- data
- _provenance
'400':
description: Invalid request (no payment consumed)
content:
application/json:
schema:
type: object
properties:
error:
type: string
code:
type: string
'401':
description: Invalid X-API-KEY
content:
application/json:
schema:
type: object
properties:
error:
type: string
code:
type: string
'402':
description: Payment required or invalid
content:
application/json:
schema:
type: object
description: x402 v2 PaymentRequired (also base64 in the PAYMENT-REQUIRED header)
properties:
x402Version:
type: integer
error:
type: string
code:
type: string
resource:
type: object
accepts:
type: array
items:
type: object
extensions:
type: object
'502':
description: Upstream failure; the payment is released or not settled
content:
application/json:
schema:
type: object
properties:
error:
type: string
code:
type: string
tags:
- Naive Timestamp Hazard
components:
securitySchemes:
x402:
type: apiKey
in: header
name: PAYMENT-SIGNATURE
description: x402 v2 payment payload (base64) sent after a 402 challenge
apiKey:
type: apiKey
in: header
name: X-API-KEY