CHATCARD · CARDITECTURE

Your chat, on a card.

ChatCard is a portable chat card you can carry across apps and sites. It remembers how you talk, links to the AI you trust, and clicks into AI-enabled content through Carditecture.

You choose what actions the card can take, app by app.

Instead of starting over in every product, you bring one card--with your name, tone, and history--and let apps plug into it.

Get your ChatCardSee how Carditecture works

Carry your tone

Languages, tone, and reading preferences stay on the card.

Bring your provider

Link the AI you trust once and let apps plug into it.

See clear actions

Pages declare the exact actions they want your card to run.

powered by glyphd labs

Al
AlexChatCard · @alex
Not connected
AI IDENTITY CARD · VERIFIED · PORTABLE
Persona: casualReading: standardLanguages: EN · ES · FR

This AI knows:

  • • How you prefer to be spoken to (tone, language, style).
  • • Your accessibility preferences (where supported).
  • • Which actions apps are allowed to ask it to take.

Requested scopes

Read page content·Read-onlyrequiredSuggest actions·SuggestAct with confirmation·Act w/ confirm
card_01H · 2025

WHY A CHATCARD

Why a ChatCard?

People teach every new app how they talk. ChatCard gives them one portable card, while Carditecture gives builders a simple way to plug into it.

One card, many apps

Every product is shipping its own chat box. ChatCard gives you one portable identity you can carry across them all.

Remembers how you talk

Your languages, tone, accessibility settings, and reading level travel with you so new apps start on the right foot.

Your provider, your choice

Link the AI provider you trust. Carditecture routes actions to that provider without locking you into anyone's UI.

You own your card, you control consent

Your ChatCard is yours. You decide which apps can use it, what actions they can request, and what permissions you grant. Every connection requires your explicit consent, and you can revoke access anytime.

HOW CARDITECTURE WORKS

How Carditecture works

Carditecture is the system that lets cards, pages, and providers stay in sync. Three pieces, one shared contract.

The Card

You carry a ChatCard with your name, avatar, languages, tone, and permissions.

  • Link it to the AI provider you trust.
  • You choose what actions the card can take, app by app.
  • Every permission requires your explicit consent.
Pages & Apps

Web pages or native apps declare simple "do this with your card" actions.

  • Cards discover those actions automatically when you visit.
  • Pages share just enough context for the action you pick.
Providers

Providers receive a clean stream of usage events via Carditecture.

  • They see which card acted, on what surface, and why.
  • They plug into Carditecture once instead of rebuilding UI.

FOR PROVIDERS

Routes your models everywhere

Carditecture lets one integration surface your models anywhere a ChatCard appears. The card carries consent and context so you can focus on intelligence, not UI plumbing.

  • Plug into Carditecture once and appear anywhere a ChatCard does.
  • Receive structured, user-consented events that keep context clean.
  • Users own their cards and grant explicit permissions--you just receive clean, consented usage data.
Provider docs (join early list)

What you receive

Structured events describing which ChatCard acted, which surface requested the action, and what scope was granted. No scraping, no mystery sessions.

event.card

→ id, languages, tone (user-owned)

event.surface

→ action id, scopes, context summary

event.provider

→ provider id, model hint, result status

Drop-in actions for builders

Declare actions like "summarize this report" or "explain this chart." The ChatCard discovers them, fetches the right context, and talks to the user's provider.

{
  "cardActions": [
    {
      "id": "summarize",
      "label": "Summarize this page",
      "scopes": ["read_page"],
      "context": "https://yoursite.com/context"
    }
  ]
}

FOR BUILDERS

Add Carditecture in hours, not weeks

  • Add a tiny JSON snippet to declare what your surface can do with a ChatCard.
  • Optionally expose a lightweight context endpoint--no heavy SDKs required.
  • Let the user's card decide permissions, providers, and presentation.
Join early builders

NERD NOTE

If you're curious how it works

Under the hood, Carditecture leans on internal Glyphd components like GlyphdIR and Tongbuku to keep cross-language memory in sync. They stay behind the scenes so all you see is one calm card that remembers you.

Get your ChatCard

Early cards are rolling out to a small waitlist. Tell us how you plan to use your card--personal research, professional workflows, or cross-org collab--and we'll send setup details as soon as they're ready.

Email hello@chatcard.cloudSee integration paths

We reply with next steps, timelines, and how Carditecture fits your stack.