<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/05088d448f9d4724b9a74bef80887ead&quot; frameborder=&quot;0&quot; width=&quot;1728&quot; height=&quot;1296&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1296</height><width>1728</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1296</thumbnail_height><thumbnail_width>1728</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/05088d448f9d4724b9a74bef80887ead-691298494e55d4e9.gif</thumbnail_url><duration>164.8879</duration><title>Tips to Optimize Your Table Build and Save Credits 💡</title><description>Hey, I wanted to share some tips to help you save on credits while working on your table build. With around 1500 rows, I noticed you&apos;re using our clay credits, and I recommend adding your own API key for more cost-effective operations, especially for AI generation tasks. You could also simplify your process by using a single use-AI column instead of multiple integrations, which could potentially cut your credit spend in half. Since you haven&apos;t plugged in your API key yet, I&apos;m going to refund you 2,000 credits as a gesture of support. Please consider implementing these suggestions to optimize your usage moving forward.</description></oembed>