Your AI agent signs in to LotsBlog with OAuth, so no key or password goes into the chat, and it can do only what your role and the permissions you tick allow. A new post can't go live without Send and publish, an agent can't delete a post for good or your blog, and you can disconnect any app at any time.
LotsBlog is the blog your AI agent runs: ChatGPT, Claude or another agent saves drafts, schedules and publishes on your own domain, and the dashboard does all of it by hand too. Handing a live blog to an agent is a fair thing to be careful about, so this page sets out how the agent signs in, what each permission covers, what it can't do at all, where your content is stored, and how to give an agent less access than you have. It comes from LotsBlog's skill file, tool list, REST documentation, the security page, the privacy policy, the terms, the changelog and the product code, all read on 29 October 2026.
How you and your agent sign in
- You: Google or a one-time code. You sign in to your LotsTech account with Google or a code sent to your email, so there is no account password for us to lose. The session lives in a secure cookie that scripts on a web page can't read.
- Your agent, over MCP: OAuth in your browser. You add
https://api.lots.blog/mcpto ChatGPT, Claude, Claude Code, Codex, Cursor or another MCP client and sign in. You never paste a key or password into the chat. Setup steps for each agent are on lots.blog/mcp. - You approve every app. A page asks "Allow [app]?", shows the account you're signed in with and the address you'll return to, and lists what the app may do. An app that registered itself and returns to an address LotsTech doesn't run gets an "Unverified app" warning, with that address shown; apps on your own computer and the official Claude, ChatGPT and Cursor connections don't get it. You press Allow or Deny.
- PKCE, short-lived tokens. The sign-in uses the authorization code flow with PKCE (S256 only; see the public server metadata). The access token lasts one hour. It renews with a refresh token that lasts 30 days and is replaced each time it's used, and tokens are stored as hashes.
- REST and a few agents: an API key. Scripts and agents that can't do OAuth use a key you create at lotstech.com/api. It's shown once, LotsBlog keeps only a hash of it, it's limited to 100 requests a minute, and you can limit it to the same permissions as an app connection or revoke it. Some agents, such as Hermes Agent, DeepSeek, nanoclaw and Paperclip, connect this way; their setup guides say so.
An agent acts as you, with your role on each blog. It can never do more than you can.
What each team role can do
A blog has one owner. You can invite people as admin, editor or author, and you can only invite, re-role or remove people below your own role. Ownership is never granted by an invite or a role change.
| Role | What it can do |
|---|---|
| Owner | Everything: team, settings, custom domain, publishing, and deleting posts for good from the dashboard Trash |
| Admin | Manages the team, manages and publishes any post, and can delete posts for good from the dashboard Trash |
| Editor | Writes, edits and publishes any post. Can move only their own posts to Trash |
| Author | Writes and edits their own drafts. Can't publish |
Changing blog settings, connecting a custom domain and removing a path setup through your agent need the owner's account.
Permissions: what you let an app do
When you approve an app, the screen asks what it may do in LotsBlog. Each tool in the tool list carries one of these permissions, and a tool whose permission depends on how it's used is listed with both.
| Permission | What it covers in LotsBlog | Starts |
|---|---|---|
| Read | Lists your blogs, posts, topics, media, team and funding status, reads analytics, and reads a saved post back | Always on |
| Create and edit | Saves drafts, edits posts, topics and images, updates blog settings, connects a domain, creates a blog, submits your sitemap to Google, moves a draft to Trash and restores a draft from Trash | On |
| Send and publish | Publishes or schedules a post, restores a post from Trash to live or scheduled, and invites people to the team | Off |
| Delete | Takes a published post off the blog, moves a published post to Trash, deletes a topic or an unused image, removes a teammate or changes their role, removes a path setup, gives the blog to another account (owner only, and the new owner must accept) | Off |
If an app asks for more than the defaults, those rows are ticked and highlighted for you to review before you approve. Your role still applies on top: a permission your role doesn't have in any of your blogs isn't offered. You can change an app's permissions later in Connected apps, and the change applies to its live sign-in at once.
A request to our support team from your agent is the one tool that works on every connection, even a read-only one: it only writes to our support inbox, never to your blog.
Two things in Create and edit are worth knowing:
- Edits to a post that's already live go live. Publishing is Send and publish, but changing the text of a published post is an edit. An app that should only draft needs a role that can't publish, as described below.
- Settings and credits. Blog settings such as privacy, the description and reader sign-in are updated with Create and edit, owner account only. Creating a blog is too, and a blog beyond your plan is paid from your credits at your plan's rate.
What your agent can't do at all
- Delete your blog. There is no tool for it. Neither is there one for removing a custom domain; both happen in the dashboard.
- Delete a post for good. A deleted post goes to Trash, leaves the site, sitemap, RSS and search at once, and can be restored. Only the owner or an admin can delete it for good, from the dashboard Trash.
- Buy credits or change your plan. It can check funding and give you a link, and you open it.
- Make anyone the owner on its own. Invites and role changes never grant it, and the owner can't be removed or leave. Ownership moves only when the owner starts a transfer, which needs Delete, and the new owner accepts it.
- Read your readers. There is no tool for reader accounts or comments.
- Change your DNS or your website. For a custom domain it returns the records and you add them. For a blog at
example.com/blogit returns one rewrite rule and a private secret that you store as theLOTSBLOG_PROXY_SECRETsecret or environment variable, never in code. - Act beyond your role. An author's agent can't publish, and
list_blogsreturns only blogs where you're an owner or active member.
What it does only when you ask
The tool descriptions and the skill file tell your agent to publish, schedule, unpublish, trash and delete only on your instruction, and to read a saved post back before retrying an uncertain write. The permissions above are the hard stop behind that:
| Action | What has to be true first |
|---|---|
| Publish or schedule | Send and publish is on, your role can publish, and the blog is funded. A scheduled post is checked every 15 minutes |
| Unpublish a live post | Delete is on. A live post leaves the blog only this way: other status changes are refused, and it becomes a private draft |
| Move a published post to Trash | Delete is on. Drafts, scheduled and archived posts need only Create and edit |
| Invite a teammate | Send and publish is on, and you're an owner or admin. The invitation lasts 7 days and the invitee signs in with the address it was sent to |
| Delete an image | Delete is on, and the image isn't used by a post, cover or the blog's appearance |
What stays private
- Drafts and previews. A new post defaults to a private draft. Its preview link needs you to be signed in as an active member of the blog, is kept out of search engines, and an author can preview only their own posts. Drafts stay out of the sitemap, RSS,
llms.txtand the Markdown copies. - Private blogs. A private blog is invite only: nobody else can sign up to read it. Private blogs stay out of those discovery files too.
- Images are public. Every uploaded image has a public CDN address, even on a private blog. Don't upload an image you wouldn't show anyone.
- The blog guide. The private Markdown guide holds your audience, voice and facts for your agent. It's never part of public article content. Keep passwords and API keys out of it.
Your readers
Readers sign in to like, save and comment. Each blog has three switches: a 6-digit email code, Continue with Google, and passwords, with at least one on. A new blog starts with passwords off. A code expires in 10 minutes, works once and is retired after 5 wrong guesses. Someone who already has an account can always get a code for their address, so turning a method off never locks anyone out. Your agent can set these switches with update_blog.
Google Search Console
Connecting Search Console is done in the dashboard by an owner or admin, and there's no Google login for you to give LotsBlog. You either add LotsBlog's service account to your own property, or choose "Set it up for me", which verifies the blog and makes that account an owner of a new property. Owners, admins and editors can see the numbers, and your agent reads them through get_blog_analytics and get_post_analytics. Disconnecting stops LotsBlog reading Google and deletes the numbers it stored. On a property you own, remove our account under Users and permissions in Search Console to finish the job.
How your content is stored
You keep ownership of what you create. The terms give LotsTech a limited licence to store and display it to provide and improve the service, and the privacy policy says "Our products do not send the content you create or store to AI providers". When you use an AI agent, it is the agent you connect and control, and its provider processes what it reads under its own terms.
- Where. Your data is stored primarily in the United States, in Supabase databases and on Cloudflare, including your images. Page-view analytics for hosted blogs run on Umami that we operate on a server in Nuremberg, Germany.
- Encryption. Every connection to our sites uses HTTPS, and your data is encrypted at rest by our providers.
- Backups. Every database is backed up nightly, encrypted, with a second locked copy at a separate provider that nobody can change or delete for 30 days. Uploaded files are copied nightly and an earlier copy of an overwritten or deleted file is kept for 30 days.
- Third-party tags. Google Analytics and other trackers load on your blog only if you add their ID. Visitors on a European time zone see a consent bar first, and sign-in and dashboard pages never load these tags.
- Taking it with you. Every public article also exists as Markdown at
/your-slug.md. For anything else, email legal@lotstech.com. - Deleting your account. Your account and data are deleted or anonymized within 30 days. Copies in encrypted backups expire within about 13 months and are never used to bring a deleted account back.
LotsTech doesn't sell personal information, and the security page lists how to report a vulnerability: security@lotstech.com.
If you stop paying
Cancel any time and nothing is deleted. Public pages stay readable, and new publishing and other paid operations need funding again. Nothing in Trash is purged automatically: it stays until the owner or an admin deletes it.
How to give an agent less access than you have
Because the agent acts as whoever signed in, you narrow it by signing it in as someone with a narrower role:
- Invite an address you control to the blog as Author (drafts only, can't publish) or Editor (can publish). You can do it on the Team tab or ask your agent to call
invite_blog_member. - Sign in to your agent with that account instead of yours.
- On the approval screen, leave Send and publish and Delete off.
An author's agent can't publish, can't change blog settings, domains or privacy, and sees only the blogs it was invited to.
If you run client blogs
Every blog has its own team, roles and private guide, and an agent sees only the blogs its account belongs to. Invite a client's staff as authors or editors, keep the owner seat on your account, and connect each agent with the narrowest account that does the job. Ownership and the custom domain stay with the owner until you hand the blog over: when it's finished, you can transfer it to the client's own LotsBlog account, stay on the team as admin, editor or author if you choose, and the posts keep the same addresses. Invitations work on private blogs too, and a removed teammate keeps a reader account while their posts stay.
If the blog lives on your own site
A blog served at example.com/blog needs one rewrite rule on your site. LotsBlog never edits your site or your DNS: it returns copy-ready rules for Cloudflare Workers, Vercel, Next.js, Netlify and Nginx, you add one, and check_domain confirms it. The steps are in host your blog at yourdomain.com/blog.
How to cut off access
- An AI app: open Connected apps, which lists every AI app that can act on your account, and disconnect it. It has to ask for your approval again.
- An API key: revoke it at lotstech.com/api.
- A teammate: remove them on the Team tab or ask your agent. They keep a reader account and their posts stay.
Connect LotsBlog to your agent
Give your agent this and let it set itself up:
Read https://lots.blog/skill.md and help me connect LotsBlog for you. Then list my blogs and tell me my role in each.
LotsBlog plans start at $24 a month for 3 blogs, or you pay $9 per blog a month from credits (checked on 29 October 2026 at lots.blog/pricing). New accounts get free credits when they sign up, no card, enough to run one blog for about a month. For the full walk-through in one agent, read How to Publish Blog Posts From Claude Code, and for every REST call see the LotsBlog REST API guide.
Common questions
Is LotsBlog safe to connect to ChatGPT or Claude?
LotsBlog signs your agent in with OAuth, so you don't paste a key or password into the chat, and the agent has only your role on each blog. You choose what it may do on the approval screen, and a new post can't go live without the Send and publish permission. You can disconnect it at any time from Connected apps.
Can my AI agent publish without asking me?
Not without the Send and publish permission, which starts off. Drafts stay private, and publishing, scheduling and unpublishing need that permission or Delete. The agent is also told to act only on your instruction.
Can my agent delete my blog posts?
It can move a draft to Trash, and a published post only if you've allowed Delete. Nothing is deleted for good: you or your agent can restore a post from Trash, and only the owner or an admin can delete it for good from the dashboard Trash.
Where does LotsBlog store my content?
Primarily in the United States, in Supabase databases and on Cloudflare, with HTTPS connections, encryption at rest and nightly encrypted backups. Page-view analytics for hosted blogs run on a server in Germany.
Does LotsBlog send my posts to an AI provider?
No. The privacy policy says LotsTech products don't send the content you create or store to AI providers. Your own agent reads what you ask it to, and its provider processes that under its own terms.
How do I disconnect an AI agent from LotsBlog?
Open Connected apps at lotstech.com, which lists every AI app that can act on your account, and disconnect it. Revoke an API key at lotstech.com/api. A disconnected app has to ask for your approval again.
Details from LotsBlog's skill file, tool list, REST documentation, pricing, the security page, the privacy policy (last updated 27 October 2026), the terms and the product code, read on 29 October 2026.
