FetchskiAI Recordings

Find out why a conversation cost what it did: while recording is on, FetchskiAI Recordings keeps a copy of each text request your site sends to the AI. Image generation isn’t recorded. Open a request to see what it cost, how many tokens it used and how much came from your Skills. Tokens are the small pieces of text the AI reads and writes, and AI is priced by them. Input tokens are what’s sent to the AI. Output tokens are what it writes back. Who can do this: Admins and Owners. They can give these permissions to other roles in People & Roles: See their own FetchskiAI recordings, See everyone’s FetchskiAI recordings and Turn FetchskiAI recordings on or off.

Open the recordings

• In the toolbar, choose FetchskiAI → FetchskiAI Recordings.
• Or open the command palette (⌘K, or Ctrl+K on Windows) and choose FetchskiAI Recordings.

What gets recorded

While recording is on, every text request FetchskiAI makes is kept. That covers the Agent, Write with AI and AI assist in rich text, SEO suggestions, blog posts, the AI Playground and the Skill Creator. How the counting works:

• A conversation is a chat from start to finish.
• A turn is one message from a person and the answer to it.
• A step is one request to the AI. Answering one message can take several steps, for example when the Agent reads a page, then changes it. Each step is its own record.

Image generation isn’t recorded. Its cost still shows in Usage and budget. Some details are masked before a request is kept. Keys and other secret codes, email addresses and phone numbers are replaced with a placeholder such as “[email removed]”, and the request notes how many were masked. Pictures are left out too. Everything else stays readable, including names, prices or other private text someone typed. Token counts and sizes stay real, so what you see is a masked copy of the request.

Recording and how long to keep it

The card at the top says Recording or Not recording. Recording is on for every new site, and recordings are kept for 7 days.

• Keep for … days: how many days to keep each recording, from 1 to 30. Type a number and choose Save. While recording is on, recordings older than that are deleted every hour.
• Stop recording / Start recording: turns recording off or back on.
  • While recording is off, nothing new is kept, and what’s already there stays. The hourly clean-up pauses.
  • When you turn it back on, the clean-up runs straight away and deletes recordings older than Keep for … days. Newer ones stay.
• Clear all: deletes every recording on the site, from every person. Confirm with Delete all. Recording stays on or off as it was.

People who can see recordings but not change them see the card without these buttons.

Whose recordings and which agent

• Everyone / Mine: switch between every person’s requests and your own. People who can see only their own don’t get this switch. Requests that no person made show only under Everyone.
• Agent: show one kind of request, such as the Agent or writing help, or All agents.

The totals and summaries

Four totals sit under the filters:

• Stored: how many steps are kept, and in how many turns.
• Input tokens: everything sent to the AI, with how much was reused from earlier steps at a lower price.
• Skills: what your Skills cost, and their share of the input.
• AI cost: the total cost of the recordings kept now, under the filters you chose, since the oldest one. It leaves out image generation, the Code Sandbox, anything made while recording was off and anything already deleted. It isn’t your site’s bill.

When the agents have run code, a Code Sandbox total appears too. That cost is billed separately from AI. See Code Sandbox. Below them, By agent splits the cost by kind of request. By Skill shows each Skill’s tokens and cost. By day charts the cost for each day over the last 30 days, with the Skills’ share drawn darker. The chart counts only the recordings still kept, so days older than Keep for … days stay empty. For the full monthly totals, use Usage and budget.

Look at one request

Recorded turns lists every conversation turn, newest first. Each turn shows who asked, when, the model and its total tokens and cost. Its steps are listed underneath. Each step has a colored bar showing how big each part of the request was:

• Instructions: the built-in guidance FetchskiAI gives the AI for this feature, plus your business details and custom instructions.
• Tools: the descriptions of the actions the AI may take, such as reading or changing a page. These aren’t buttons on your screen.
• Input: the conversation so far, the details sent along with it and the newest message.
• Skills: the Skills included in the request.
• Other: the remaining settings sent with the request.

Choose Open on a step to see it in full:

• Where the request goes: how much of the request each part took, with a token estimate for each.
• Skills, largest first: every Skill in the request, how it came in, and its estimated tokens and cost.
• Code Sandbox runs: any code this step ran, with its time and estimated cost.
• The request, as sent and The response: the whole exchange, as a masked copy. Read it right here on the screen.

Copy JSON and Download JSON at the top give a technical copy of the step. It’s meant for troubleshooting, for example to send to Fetchski Support, rather than for reading. Choose All recordings to go back to the list.

Good to know

• Use it to trim costs. A Skill that’s large and loaded on every request shows up near the top of By Skill. To lower every conversation’s cost, open it in Skills and turn off Always load in full, choose fewer Agents for it, or turn it off with Enabled.
• Costs here are for checking, not billing. For the monthly picture by feature and person, use Usage and budget.
• Recordings hold what people typed. Anyone who can see everyone’s recordings can read other people’s requests. Give that permission only to people you trust with it.

Related