veil

Integrate Veil

Find the right key through an account your users already know. Let them check who signed a message, even if that account is stolen.

A card, read live#

GEThttps://veil.rip/u/1.json

This request runs as the page opens. Its answer fills the values below.

FieldIn this answerMeaning
nintegerPermanent card number.
namestringCurrent display name; a hidden name becomes Card followed by its number.
urlstringPermanent URL using the card number.
keysarray<CardKey>All device and recovery keys, including revoked keys.
fingerprintFingerprintTwelve words in each language and twelve five-digit groups.
witnessesobject | nullsigned, of and needed counts for the current version. These are server checks.
The whole answer

Public lookups, cards and message verification need no API key. You can call them from a browser, a bot or a server.

cURL
curl -fsS 'https://veil.rip/u/1.json'

Common tasks#

  • GET
    Look up a cardFind the card that holds one exact account, key or fingerprint.
    /v1/lookup
  • GET
    Read a person’s cardRead the full public card, signed record, proof and recent history.
    /u/{card}.json
  • GET
    Find the owner of a keyLook up a public key, the card holding it and its validity period.
    /v1/keys/{key}
  • POST
    Verify a messageCheck a signature block or an explicit key, message and signature. This POST only reads.
    /v1/verify
  • POST
    Verify a file or a releaseCheck the signature of a file from its hash, or of a signed checksum list, against a card’s keys. This POST only reads.
    /v1/verify
  • GET
    Check when a key could signAsk whether a key was active at a particular time.
    /v1/keys/{key}/active-at
  • GET
    Read card historyRead older version events and the account transfers around them.
    /v1/identities/{n}/history
  • GET
    Embed a verifying widgetShow a read-only card that verifies itself in the visitor’s browser.
    /{kind}/{card}/embed

Use the result#

Browse the reference#