Everything your engineering team needs to integrate BlockContentSeal — and everything about how we keep certificates tamper-proof, independently verifiable, and permanent.
BlockContentSeal is available via a clean REST API. If your platform can make an HTTP request at publish time, it can have content provenance in production today.
# POST /v1/seal curl https://api.blockcontentseal.com/v1/seal \ -H "Authorization: Bearer $BCS_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "url": "https://yourpublication.com/article/slug", "author": "author-id-or-byline", "content": "full article text or canonical HTML", "published": "2025-06-16T09:31:00Z" }' # Response { "certificate_id": "BCS-2025-0047291", "content_hash": "sha256:a7f3c91e4b2d8f…", "tx_hash": "0x4a3f…c91b", "block": 19847203, "sealed_at": "2025-06-16T09:31:02Z", "verify_url": "https://blockcontentseal.com/verify/BCS-2025-0047291" }
Paste any URL from a BlockContentSeal-protected publisher. We'll return its authenticity status, original certificate, and full chain of proof in under a second.
Certificates are anchored on public blockchains. Anyone can verify them without involving BlockContentSeal — including after we're gone. Not even we can alter a sealed record.
Read the architecture →SHA-256 content hashing means any alteration — even a single character — invalidates the certificate and flags the content immediately. Mathematical certainty, not policy.
View technical details →BlockContentSeal is built on and compatible with C2PA — the non-profit Coalition for Content Provenance and Authenticity. No proprietary lock-in. The emerging industry standard.
C2PA compatibility →Breaking news is when content gets copied, misquoted, and replicated fastest. BlockContentSeal creates an unimpeachable timestamp at publish — giving you a permanent record of exactly what you reported, and when, before anyone else could have altered the narrative.
When a story goes viral and variants start circulating, your original is provably yours.
Protect your newsroom →Wire content is republished dozens of times before end-of-day. BlockContentSeal gives the originating outlet a permanent proof-of-origin that travels with the content — making it unambiguous which publication created the story and when.
See integration →AI can generate articles that look like yours. It cannot generate a certificate that was anchored on-chain before the AI existed. BlockContentSeal's provenance timestamp is the one signal AI-generated impersonators can never fake.
Start protecting content →BlockContentSeal creates a legally-relevant chain of evidence for every published document. Timestamps are verified to the second. Content integrity is cryptographically guaranteed. Certificates are independently auditable without involving BlockContentSeal.
Book enterprise demo →The embeddable BCS verified badge gives readers immediate confidence — without requiring any technical knowledge. One click shows the full provenance record: who wrote it, when, and that it hasn't changed.
Add the verified badge →Average integration time under two hours. No blockchain knowledge required.