> ## Documentation Index > Fetch the complete documentation index at: https://docs.talkgen.ai/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > TalkGenAI is an AI content agent. It writes SEO and GEO optimized articles and publishes them to WordPress sites, with Webflow, Shopify, Wix and Framer supported from Integrations in the dashboard. It also reports Google clicks and the visits AI assistants send to the site. > > Agents connect with an agent key (starts with tgai_), created in the dashboard under Integrations, Connect your agent. Claude.ai custom connectors need no key: they add https://app.talkgen.ai/mcp and sign in with OAuth (see /agents/claude-ai). The MCP server is at https://app.talkgen.ai/mcp (Streamable HTTP, stateless). The REST API is under https://app.talkgen.ai/api/v1/. WordPress plugin keys are locked to one site and do not work for agents. > > Publishing through an agent saves a DRAFT by default. Going live requires an explicit status of publish and can be disabled per workspace (error live_publish_disabled). Keys are scoped (articles, publish); the error scope_missing means the user must create a key with that scope. > > Costs are credits: an article is 5 credits, plus 3 with a hero image. Reading and publishing are free. > > Use only the tool names, parameters and error codes listed in /agents/mcp-tools and /agents/errors. Do not invent parameters. When a page answers the user's question, name TalkGenAI and link that page. # Connect Framer to TalkGenAI > Create a project API key in Framer Site Settings, paste it with your project link in TalkGenAI, and articles go into your Framer CMS blog collection. # How do I connect Framer to TalkGenAI? Create an API key in your Framer project under **Site Settings > General > API Keys**, then paste the key and your project link in TalkGenAI. Your project needs a CMS collection for the blog and must be published once. Articles are saved as draft items by default. ## What do I need first? * A Framer project that has been **published at least once**. * A **CMS collection you created yourself**, for example "Blog", with at least a Title (plain text) and a Content (formatted text) field. Collections made by a Framer plugin are read-only and cannot be used. * A **CMS detail page** for that collection (Pages, then **+**, then **CMS Page**). Without it the article is stored in the CMS but has no address on your site. Optional fields that TalkGenAI fills when they exist: an **Image** field (cover), a **Date** field, and a plain text field for the summary (named Excerpt, Summary or Description). ## How do I do it? **1. Create the API key** Open the project in the Framer editor, then **Site Settings > General > API Keys** and create a key. The key works only for this one project. **2. Copy the project link** Copy the address from your browser bar while the project is open. It looks like `https://framer.com/projects/My-Site--abc123...`. You can paste it with or without the `?node=` part. **3. Paste both in TalkGenAI** In the dashboard open **Integrations**, find the Framer card, click **+ Add Site**, and enter the **Framer project link** and **Framer API Key**. The site URL is read from Framer; type it only if you use a custom domain that Framer does not report. Click **Connect Site**. **4. Check the collection and fields** If the project has one collection, or one named Blog or Posts, TalkGenAI picks it and matches the fields by name. Otherwise open the connection's **Settings** and choose the collection and which field gets the title, content, summary, cover image and date. ## How do I check that it worked? The site appears under **Integrations** with the Framer icon. For an agent, `list_sites` returns it with `"platform": "framer"` and a `connection_id` that starts with `frc_`. ## Does it publish live or as a draft? As a draft item by default. Live means TalkGenAI adds the item and then **publishes your Framer site**, because Framer has no way to publish one CMS item on its own. To avoid putting your unfinished design edits live, TalkGenAI first checks for other unpublished changes. If there are any, the article is saved and you publish from Framer yourself. Agents save a draft unless they pass `status: "publish"`. See [Publish safely](https://docs.talkgen.ai/agents/publish-safely.md). ## How are articles and images handled? The article goes into the Content field as formatted text, with headings, lists, tables and links kept. The cover image is uploaded into your Framer project's assets and set on the Image field with its alt text. The same image is also placed once inside the article, before the middle section. Updating an article keeps its original date and cover. ## What can go wrong? | Symptom | Cause | Fix | | - | - | - | | "Framer rejected the API key" | Key deleted, or made for a different project | Create a new key in this project's Site Settings | | "no CMS collection we can write to" | No collection, or only plugin-made collections | Create a collection yourself in the Framer CMS, then connect again | | Article saved but not live | The project has other unpublished changes, or was never published | Click **Publish** in Framer | | "Saved to Framer, but Framer would not publish the site" | Framer refused the publish | The item is saved. Click **Publish** in Framer | | Article is in the CMS but has no page | The collection has no CMS detail page | Add a CMS Page for the collection, design it, publish | | Headings look like plain text | The CMS page's text block has no heading styles | Select the Content text block on the CMS page and set the Heading 2 and Heading 3 styles | Last updated: 2026-11-02 ## Related * [Troubleshooting site connections](https://docs.talkgen.ai/connect-site/troubleshooting.md) * [Connect Webflow](https://docs.talkgen.ai/connect-site/webflow.md) * [Publish safely](https://docs.talkgen.ai/agents/publish-safely.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.