Build with EIL

TypeScript SDK

Install @digitalcard/sdk from npm. DigitalCard.resolve() tries the registry first, then well-known on the target domain when configured.

npm install @digitalcard/sdk

import { DigitalCard } from '@digitalcard/sdk'

const { card, meta } = await DigitalCard.resolve({
  domain: 'example.com',
})

console.log(card.name.official)
console.log(card.verified)
console.log(meta.source)

Registry API

All registry routes are under /api/v1. Responses include a card object and optional meta (source, resolved_at). Public read endpoints require no API key.

curl "https://eilcard.com/api/v1/resolve?domain=example.com"

curl "https://eilcard.com/api/v1/cards/your-handle"

404 means no registry record — the SDK may fall back to https://{domain}/.well-known/digital-card when enabled.

Discovery chain

Hybrid discovery keeps registry fast while domain-bound well-known proves ownership at the source.

1. Registry — GET /api/v1/resolve or /api/v1/cards/{handle}
2. Well-known — GET https://{domain}/.well-known/digital-card
3. DNS TXT — _digital-card.{domain} for verification hints

curl "https://example.com/.well-known/digital-card"

_digital-card.example.com TXT

After DNS verification in the dashboard, records expose verified: true and stable canonical fields.

Response shape

Cards follow schema v1.0 — discriminated by type (organization | person). Key fields agents rely on:

• +type, card_id, handle — identity keys
• +name — official or full name
• +contact — website, email, phone
• +verified — domain-attested trust signal
• +actions — machine-readable contact intents