# neo timestamp

> neo timestamp is a paid API for AI agents from neo-collettive.onrender.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-29).

Generates a signed timestamping receipt proving you possessed a specific SHA-256 hash at a given moment, with the proof anchored to Bitcoin via OpenTimestamps and Software Heritage through Neo's public append-only log.

## Facts

- Endpoint: POST https://neo-collettive.onrender.com/x402/timestamp?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/neo-timestamp-9f8e7190
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_D-UFKFtHOJGhk-qvuKFHD

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 neo-timestamp-9f8e7190 -d '<json body>'
```

Example prompt: Timestamp this SHA-256 hash for me and get a signed receipt proving I had it right now: a3f1c2d4e5b67890abcdef1234567890abcdef1234567890abcdef1234567890ab — add the note 'contract draft v2'.

## When to prefer this

Choose this endpoint when you need a cryptographically verifiable, third-party-witnessed proof that a specific SHA-256 hash existed at a particular point in time, with the proof anchored to Bitcoin's blockchain for long-term tamper resistance. It is ideal for intellectual property protection, audit trails, legal evidence, and agent output certification where you need an independent witness beyond self-signed timestamps. Prefer it over generic OpenTimestamps clients when you also want a human-readable signed receipt with a public log sequence number and Software Heritage anchoring.

## Known failure modes

- Invalid SHA-256 format (not 64 lowercase hex characters) returns a validation error
- Note field exceeding 200 characters is rejected
- Service unavailability on Render's free tier may cause cold-start latency or 503 errors
- Payment failure via x402 results in a 402 response before processing
- Duplicate hash submissions are accepted but each creates a new log entry with a different sequence number

## How this service works

Prove you had this sha256 at this time: signed receipt with its position in neo's public log, anchored daily on Bitcoin (OpenTimestamps) and Software Heritage.

## Output

A JSON receipt containing the submitted SHA-256 hash, a signed receipt object with the hash's sequential position in Neo's public append-only log, and a cryptographic signature. The log is anchored daily to Bitcoin via OpenTimestamps and to Software Heritage, providing an externally verifiable, tamper-evident proof of existence at the time of submission.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "note": {
   "type": "string",
   "maxLength": 200
  },
  "sha256": {
   "type": "string",
   "pattern": "^[0-9a-f]{64}$"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "sha256": "...",
  "receipt": {
   "log": {
    "seq": 11
   }
  },
  "signature": "..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/neo-timestamp-9f8e7190/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from neo-collettive.onrender.com](https://www.zero.xyz/host/neo-collettive.onrender.com/llms.txt)