Add AI agents to Framer with ASDK

Framer sites are often startup landing pages and product marketing sites that change every week or two. ASDK suits that pace. You add one script to the site settings once, and from then on the agents read every page you publish, so a new landing page becomes part of the knowledge base the next time it refreshes, without anyone touching the widget.

What ASDK adds to a Framer site

ASDK builds one knowledge base from your published pages, including CMS pages such as a blog or changelog, plus documents you upload. Every agent you switch on answers from it.

• Chat (early access, from the Free plan) answers visitors from your content, links the pages each answer came from, and offers to take contact details when it cannot help.
• Sales (early access, from the Pro plan) asks the qualifying questions you write in plain language and offers a meeting to visitors who fit. For a startup site, that often means sending small teams to self-serve and booking calls with larger ones.
• Agent-Ready (early access, from the Free plan) publishes what your knowledge base knows in formats AI assistants read well, such as a hosted llms.txt file.
• Search is coming soon. It will answer in place of a search box, with sources.

The widget is a single script that adds a chat button in a corner of the page. It does not touch your Framer components, animations or breakpoints.

An example from a Framer site

Picture a young software company with a Framer site: a landing page, a pricing page, a changelog and a short FAQ. A visitor on the pricing page asks: "Does the Team plan include single sign-on, and is there a free trial?"

Chat finds the pricing table and the FAQ, answers both parts and links the pages it used. If the company has switched on Sales and the visitor mentions a team of 80, the agent asks the company's own qualifying questions and offers a demo call; a team of five gets pointed to the trial instead.

If the site does not mention single sign-on at all, the agent says so rather than guessing. That gap is useful information: it is likely a question your sales calls hear too.

How it works on Framer

Framer adds site-wide scripts from the project's custom code settings. Framer's help center places them under Project settings → Custom code and recommends the end of the body tag for scripts (checked October 2026). That is where the ASDK snippet goes.

If your site switches pages without a full reload, the widget notices those page changes by itself, so a visitor can move from your home page to pricing in the middle of a conversation and keep chatting.

Custom code depends on your Framer plan. If the custom code fields are locked, your plan does not include it; Framer's pricing page lists what each plan includes (checked October 2026). ASDK's own plans are separate, and the Free plan includes Chat and Agent-Ready.

Set up ASDK on Framer

<script async src="https://cdn.asdk.com/v1/asdk.js" data-site-id="SITE_ID"></script>

What is available and what is coming soon

ASDK as a whole is in early access: the agents work and you can use them, but they may change while we improve them.

Framer details worth knowing

• One snippet for the whole site. Page-level custom code would need the snippet on every page, and new pages would start without it. The site-wide field avoids that.
• Opening the chat from your own button. A "Talk to us" button in your design can open the widget by calling asdk("open"). The HTML guide shows the line that queues calls made before the widget has loaded.
• Options for one page. Attributes such as data-open="true" open the chat when a page loads, for example on a pricing page. The HTML guide lists every option.
• Staging domains. The install check only opens your site's own domains. Check the domain your visitors use, or add the staging address to your site's allowed domains in ASDK first.

Getting better answers from a Framer site

Framer landing pages are often light on text by design. That is fine for a hero section, but an agent needs facts it can quote:

• Spell out pricing and limits. If a plan's limits live only in a tooltip or a toggle, add them as text on the pricing page.
• Publish a changelog or "what's new" page. It answers "do you support X yet?" better than any marketing headline.
• Keep a short FAQ. Questions about trials, security, integrations and billing, with direct answers, are the passages an agent cites most.
• Retire old landing pages. Campaign pages with expired offers are still public and can still be quoted.

The free Agent Readiness Checker shows what AI assistants can read on your site today, and our agent-ready website checklist explains what to fix first.