# APISphere Timestamp API

> APISphere Timestamp API is a paid API for AI agents from apisphere.us.ci, paid per call via x402, $0.0005/call, status unknown (last checked 2026-10-13).

Returns the current timestamp in multiple formats (ISO 8601, Unix, RFC 2822, human-readable) for a specified IANA timezone, paid per-call in USDC via x402.

## Facts

- Endpoint: POST https://apisphere.us.ci/api/v1/timestamp?utm_source=zero.xyz
- Price: $0.0005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apisphere-timestamp-api-d06b6c53
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_V6jwmMoogfx1As3hASrpZ

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 apisphere-timestamp-api-d06b6c53 -d '<json body>'
```

Example prompt: What's the current time in America/Los_Angeles right now? Give me the ISO 8601 and Unix formats.

## When to prefer this

Choose this endpoint when an agent needs the current time in a specific IANA timezone and wants multiple output formats (ISO, Unix, RFC 2822, human) in a single pay-per-call request without API key setup. Prefer it over system clock reads when the agent runtime's local time is unreliable or when an authoritative, formatted multi-timezone response is needed on demand.

## Known failure modes

- Invalid IANA timezone string returns an error (e.g. 'America/Fakecity')
- Unrecognized format names in the formats array may be silently omitted or cause an error
- Payment failure or insufficient USDC balance results in HTTP 402 and no data returned
- Network timeout may occur under high load, reflected in elevated latency_ms

## How this service works

Pay-per-call APIs for AI agents. No signup, no API keys — agents pay in USDC on Base via x402. Live endpoints for crypto prices and geocoding.

## Output

Returns a JSON object containing a timestamp object with only the requested format fields (iso, unix, unix_ms, human, rfc2822), the resolved timezone string, and optional metadata including latency in milliseconds and a request ID.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "formats": {
   "type": "array",
   "description": "Time formats to include in response."
  },
  "timezone": {
   "type": "string",
   "description": "IANA timezone name (e.g., UTC, America/New_York)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "timestamp",
  "timezone"
 ],
 "properties": {
  "meta": {
   "type": "object",
   "properties": {
    "latency_ms": {
     "type": "integer"
    },
    "request_id": {
     "type": "string"
    }
   }
  },
  "timezone": {
   "type": "string"
  },
  "timestamp": {
   "type": "object",
   "properties": {
    "iso": {
     "type": "string",
     "format": "date-time"
    },
    "unix": {
     "type": "integer"
    },
    "human": {
     "type": "string"
    },
    "rfc2822": {
     "type": "string"
    },
    "unix_ms": {
     "type": "integer"
    }
   },
   "description": "Only the requested formats are present."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/apisphere-timestamp-api-d06b6c53/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from apisphere.us.ci](https://www.zero.xyz/host/apisphere.us.ci/llms.txt)