{"uid":"cap_x9NTs7q7gvJhOxKmLWCMn","slug":"satledger-rfc-3161-timestamp-receipt-9b4d5105","name":"SatLedger RFC 3161 Timestamp Receipt","description":"One RFC 3161 timestamp receipt over a digest you supply. No account and no API key: the response is the whole deliverable. Your data is never sent - only its hash - and nothing about the request is retained here.","url":"https://api.satledger.org/x402/receipt","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"digest":{"type":"string","pattern":"^[0-9a-fA-F]{64}$","description":"SHA-256 of whatever you want timestamped, as 64 hex characters. Hash it yourself; the data never leaves your side."},"digests":{"type":"array","items":{"type":"string","pattern":"^[0-9a-fA-F]{64}$"},"maxItems":10,"minItems":1,"description":"Up to 10 SHA-256 hashes. Requires the batch price; the single price permits one."}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.05","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.05/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.05","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.05","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_J1SL0Z8qyNC8Co-zJBipQ","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.05","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Issues a single RFC 3161 cryptographic timestamp receipt anchored to a SHA-256 digest you provide, with no account or API key required.","exampleAgentPrompt":"I need an RFC 3161 timestamp receipt for this SHA-256 digest: a3f1e2d4b5c6789012345678abcdef01234567890abcdef1234567890abcdef12 — no account needed, just the receipt proving it existed right now.","exampleUseCases":[{"title":"Timestamping a signed contract hash","prompt":"I've hashed a signed PDF contract and got the SHA-256 digest 9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08 — can you get me an RFC 3161 timestamp receipt to prove it existed today for legal records?"},{"title":"Software build artifact integrity","prompt":"Our CI pipeline just produced a build artifact with SHA-256 hash b94d27b9934d3e08a52e52d7da7dabfac484efe04294e576b4b1d9c7d5ccd74b — timestamp that digest right now so we have verifiable proof of when this release was sealed."},{"title":"Intellectual property creation evidence","prompt":"I've written a research paper and its SHA-256 hash is e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 — please get a cryptographic timestamp receipt to prove I had this document before submitting it."}],"resultDescription":"An RFC 3161 timestamp receipt (a signed timestamp token from a Timestamp Authority) attesting that the supplied SHA-256 digest was presented at the recorded time. The receipt is self-contained and verifiable using standard PKI tooling without any further interaction with SatLedger.","failureModes":["Invalid digest format (not 64 hex characters) — returns 400 Bad Request","Payment not included or insufficient — returns 402 Payment Required","Digest field missing from request body — returns 400 with validation error","Network or TSA upstream failure — returns 503 Service Unavailable","Submitting more than 10 digests in the batch field — returns 400 with maxItems error"],"whenToPreferThis":"Choose this endpoint when you need a standards-compliant RFC 3161 timestamp receipt without creating an account or managing API keys. It is ideal for one-off or automated timestamping workflows where privacy is paramount — only the hash is transmitted, never the underlying data. Prefer it over blockchain anchoring services when compatibility with PKI tooling, legal frameworks, or digital signature standards (e.g. PDF/A, CAdES, XAdES) is required. It is also the right choice when per-call micropayment pricing ($0.05 USDC) is preferable to subscriptions.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-14T00:30:52.640Z","isFirstParty":false}