EIL — Entity Identity Layer
Verified identity for the agent era
EIL (Entity Identity Layer) standardizes who an organization or person is — domain-bound, machine-readable, and authoritative. Agents call resolve() to read canonical JSON in milliseconds, without scraping HTML or guessing from search snippets. Not a payment card. Not user login. Infrastructure for the agent web.
Infrastructure, not another card product
Domain-attested
DNS and email verification tie identity to the domain you already own.
Agent-native
Registry API and /.well-known/digital-card — built for resolve(), not browsers alone.
Canonical by design
One verified record replaces conflicting HTML, snippets, and hallucinated answers.
SSL secures the pipe. EIL certifies the meaning.
| Layer | Question | Role |
|---|---|---|
| SSL / TLS | Is the connection authentic? Does this server own the domain? | Transport security |
| EIL | Who is this entity? Are phone, address, and official name correct? | resolve(domain) |
Agents do not choose between SSL and EIL — they choose between crawling the web or reading a verified registry record.
Scope
Not this
- —Payment or banking card
- —User login / SSO platform
- —Replacement for SSL/TLS
- —Business-card networking app
This is
- +Verified organization & person identity
- +Single source of truth for agents
- +Registry + well-known discovery
- +Trust signal via verified: true
Discovery stack
- 1
Registry (primary)
GET /v1/resolve?domain= — indexed, fast, verification metadata
- 2
Well-known (fallback)
GET /.well-known/digital-card — RFC 8615, domain-bound
- 3
DNS TXT (hint)
_digital-card.{domain} — ownership proof and registry pointer
SDK
resolve in one call
import { DigitalCard } from '@digitalcard/sdk'
const { card } = await DigitalCard.resolve({
domain: 'example.com'
})
console.log(card.name.official)
console.log(card.verified) // true