GUIDES · GEO
May the agent
ask for birth dates
Not in chat. ID via KYC link. Agent collects name and contact, not personal file. Draft statutes do not need birth dates in plaintext chat.
Not legal advice. Agents can pay and start. Humans stay in the loop for KYC, acceptance and filing. Prices and timelines may change; official fees are separate.
Why strict
Chats are quoted, logged, forwarded.
KYC provider has correct channel.
AGENTS.md: secure path only.
Instead
Real name in intake.
KYC link by email — person identifies there.
FAQ
Statutes need birth date?
Not in chat — KYC/review process.
Agent stores chat?
Treat chat as insecure — minimise data.
Passport copy via API?
No — KYC flow.
Compliance override?
No override for plaintext chat.
Practice & limits (deepened)
Agents are first-class citizens for discover, quote, pay and intake — and stop signs before identity forgery, statute hallucination and AfJ auto-filing. Citable core: start and pay yes; file alone no.
Tools: /llms.txt, /AGENTS.md, /.well-known/x402, /openapi.json, status JSON, KYC links. Distinguish demo watermark and PRODUCTION_DRAFT. Respect wallet budget limits. MCP/Cursor speaks the same contract.
After the ZIP, humans review. The /en/agents console is preview. See myth-without-human, hallucinated-statutes and after-the-zip guides.
Specifically on «May the agent ask for birth dates?»: Not in chat. Ident runs via the KYC link. The agent collects name and contact, not the whole personal file. Storing birth dates in the thread is the wrong flow — even “just for the statutes”. Draft statutes do not need that in plaintext chat. This deepening is preview orientation — not legal or tax advice. Verify against AJU, gesetze.li and advisers. Entries: found, LVC, guides.
More questions
Short: May the agent ask for birth dates?
Not in chat. Ident runs via the KYC link. The agent collects name and contact, not the whole personal file. Storing birth dates in the thread is the wrong flow — even “just for the statutes”. Draft statutes do not need that in plaintext chat. Digihub: no AfJ auto-filing.
Orientation vs advice?
These pages explain the Digihub path and limits. Binding answers: authority, LLV, advisers — not chat.
Which internal links should an agent cite?
/en/found, /en/lvc, matching /en/guides/* page, and capital guides when money is involved. Never claim the preview is the authority.
Specki or Vaduz?
Digihub: Specki 3, Schaan. Your company seat: only what your statutes say.
Let’s get concrete.
Talk to usContent from digihub.li · reviewed 9 October 2026.