1min.

1MIN · AI & AGENTS

Chat SDK turns one component catalog into native chat cards

Chat SDK’s json-render integration lets an agent describe a card using a typed JSON component catalog. Adapters translate it into formats such as Slack Block Kit or Teams Adaptive Cards, while streamed elements update the message as they arrive. Component properties are validated, but platform limits still differ: Slack may turn a second table into a code block unless explicit limits reject it.

Vercel · Nov 6, 2026

Why it matters

A shared message schema can reduce platform-specific presentation work without pretending every chat platform supports the same layout.

More context

Try a small catalog with @json-render/core and @json-render/chat. streamCard updates at most every 500 milliseconds by default, and toCard reports invalid specifications with CardSpecError. Test both valid output and platform-limit failures in each adapter. Model calls and platform access have separate costs and requirements.

Keep in mind

This is a released integration, not proof that generated content is correct or actions are authorized; schema validation checks the card structure.

Original read

More engineering ideas, one minute at a time.

Explore more stories