<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Rindler</title>
    <link>https://rindler.ai/</link>
    <description>Docs and essays on giving AI agents deterministic access to real websites.</description>
    <language>en-us</language>
    <lastBuildDate>Sat, 15 Aug 2026 06:14:41 GMT</lastBuildDate>
    <atom:link href="https://rindler.ai/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>When portal work outgrows the team doing it | Rindler</title>
      <link>https://rindler.ai/blog/portal-work-at-back-office-volume</link>
      <guid isPermaLink="true">https://rindler.ai/blog/portal-work-at-back-office-volume</guid>
      <description>Portal queues grow faster than the team working them. What changes when software can operate the site, and what to require before it carries the queue.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Sat, 15 Aug 2026 06:14:41 GMT</pubDate>
    </item>
    <item>
      <title>Portal automation that compliance can sign off | Rindler</title>
      <link>https://rindler.ai/blog/portal-automation-compliance-signoff</link>
      <guid isPermaLink="true">https://rindler.ai/blog/portal-automation-compliance-signoff</guid>
      <description>Operations, IT and compliance each need one question settled before portal work is automated. What each requires, and the order that keeps a pilot moving.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Sat, 15 Aug 2026 06:14:41 GMT</pubDate>
    </item>
    <item>
      <title>Why scripts and RPA stall on portal work | Rindler</title>
      <link>https://rindler.ai/blog/why-scripts-and-rpa-stall</link>
      <guid isPermaLink="true">https://rindler.ai/blog/why-scripts-and-rpa-stall</guid>
      <description>Most teams have already tried twice. Why portal work defeats both scripts and RPA, what changed, and the three questions to ask of the next attempt.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Sat, 15 Aug 2026 06:14:41 GMT</pubDate>
    </item>
    <item>
      <title>What to ask for instead of uptime | Rindler</title>
      <link>https://rindler.ai/blog/what-to-ask-for-instead-of-uptime</link>
      <guid isPermaLink="true">https://rindler.ai/blog/what-to-ask-for-instead-of-uptime</guid>
      <description>Availability answers a question your queue did not ask. Six things to require from an automation agreement so the work gets done and you can prove it.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Sat, 15 Aug 2026 05:05:33 GMT</pubDate>
    </item>
    <item>
      <title>What portal automation means for survey quality | Rindler</title>
      <link>https://rindler.ai/blog/portal-automation-and-survey-quality</link>
      <guid isPermaLink="true">https://rindler.ai/blog/portal-automation-and-survey-quality</guid>
      <description>For survey research, automating portal work touches paradata, fraud detection and disclosure. A governance read, not a productivity one.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Thu, 13 Aug 2026 03:43:20 GMT</pubDate>
    </item>
    <item>
      <title>Portal data for research and survey firms | Rindler</title>
      <link>https://rindler.ai/blog/portal-data-for-research-firms</link>
      <guid isPermaLink="true">https://rindler.ai/blog/portal-data-for-research-firms</guid>
      <description>Sample frames, statements and panel counts arrive through a login. What the work looks like, and the four questions to settle first.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Thu, 13 Aug 2026 03:41:48 GMT</pubDate>
    </item>
    <item>
      <title>How to choose automation for portal queues | Rindler</title>
      <link>https://rindler.ai/blog/choosing-automation-for-portal-queues</link>
      <guid isPermaLink="true">https://rindler.ai/blog/choosing-automation-for-portal-queues</guid>
      <description>Inventory the work, classify the task shapes, score what an error costs, then evaluate tools against your own map instead of a demo.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Thu, 13 Aug 2026 03:39:43 GMT</pubDate>
    </item>
    <item>
      <title>Privacy-first automation for portal work | Rindler</title>
      <link>https://rindler.ai/blog/privacy-first-automation-for-portal-work</link>
      <guid isPermaLink="true">https://rindler.ai/blog/privacy-first-automation-for-portal-work</guid>
      <description>Three decisions to write down once: what access the automation gets, what data may leave the portal, and what ends up in the logs.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Thu, 13 Aug 2026 03:37:55 GMT</pubDate>
    </item>
    <item>
      <title>Turning portal work into a repeatable playbook | Rindler</title>
      <link>https://rindler.ai/blog/repeatable-portal-playbook</link>
      <guid isPermaLink="true">https://rindler.ai/blog/repeatable-portal-playbook</guid>
      <description>Write down the steps, define what done means, plan the branches, and require proof. A playbook that survives the portal changing.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Thu, 13 Aug 2026 03:34:20 GMT</pubDate>
    </item>
    <item>
      <title>When the portal changes, what should happen | Rindler</title>
      <link>https://rindler.ai/blog/when-the-portal-changes</link>
      <guid isPermaLink="true">https://rindler.ai/blog/when-the-portal-changes</guid>
      <description>Portals change without warning. What your automation should do when it happens, how to catch drift early, and who owns the escalation.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Thu, 13 Aug 2026 03:32:36 GMT</pubDate>
    </item>
    <item>
      <title>Onboarding automation to your portals safely | Rindler</title>
      <link>https://rindler.ai/blog/onboarding-automation-to-your-portals</link>
      <guid isPermaLink="true">https://rindler.ai/blog/onboarding-automation-to-your-portals</guid>
      <description>A staged rollout for portal automation: scope one workflow, name owners, set credential and logging standards, pilot, then go or no-go.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Thu, 13 Aug 2026 03:30:51 GMT</pubDate>
    </item>
    <item>
      <title>How to run a portal automation trial | Rindler</title>
      <link>https://rindler.ai/blog/how-to-run-a-portal-automation-trial</link>
      <guid isPermaLink="true">https://rindler.ai/blog/how-to-run-a-portal-automation-trial</guid>
      <description>A hands-on checklist for trialling portal automation: pick real tasks, define completion, count hidden rework, and decide on four criteria.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Thu, 13 Aug 2026 03:29:07 GMT</pubDate>
    </item>
    <item>
      <title>Portal work as a managed service offering | Rindler</title>
      <link>https://rindler.ai/blog/portal-work-as-a-managed-service</link>
      <guid isPermaLink="true">https://rindler.ai/blog/portal-work-as-a-managed-service</guid>
      <description>How MSPs turn client portal work into a defined offering: runbooks, credential hygiene, exception monitoring, and how to package it.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Thu, 13 Aug 2026 03:28:29 GMT</pubDate>
    </item>
    <item>
      <title>Your first automation on a site with a login | Rindler</title>
      <link>https://rindler.ai/blog/first-automation-on-a-login-site</link>
      <guid isPermaLink="true">https://rindler.ai/blog/first-automation-on-a-login-site</guid>
      <description>How to pick, capture, test and monitor your first portal automation, and the proof to require before you trust a run.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Wed, 12 Aug 2026 19:55:05 GMT</pubDate>
    </item>
    <item>
      <title>Error Codes: Causes and Fixes | Rindler Docs</title>
      <link>https://rindler.ai/docs/errors</link>
      <guid isPermaLink="true">https://rindler.ai/docs/errors</guid>
      <description>Every error code Rindler can return when a run does not go through, what each one means, the most common cause, and what to do next.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Tue, 11 Aug 2026 23:36:03 GMT</pubDate>
    </item>
    <item>
      <title>How Signing In Works | Rindler Docs</title>
      <link>https://rindler.ai/docs/auth</link>
      <guid isPermaLink="true">https://rindler.ai/docs/auth</guid>
      <description>How Rindler signs in: a one-time handoff where you log in yourself in a live browser, with the session stored encrypted and reused on later runs.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Tue, 11 Aug 2026 04:09:48 GMT</pubDate>
    </item>
    <item>
      <title>Tool Reference | Rindler Docs</title>
      <link>https://rindler.ai/docs/tools</link>
      <guid isPermaLink="true">https://rindler.ai/docs/tools</guid>
      <description>Reference for every public Rindler tool: parameters, side-effect annotations, and usage notes, taken directly from the registered tool schemas.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Tue, 11 Aug 2026 04:09:48 GMT</pubDate>
    </item>
    <item>
      <title>How Dashboard Numbers Are Measured | Rindler Docs</title>
      <link>https://rindler.ai/docs/metrics</link>
      <guid isPermaLink="true">https://rindler.ai/docs/metrics</guid>
      <description>What each figure on the Rindler dashboard counts, what it excludes, the window it covers, and why some figures are taken over a smaller denominator.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Mon, 10 Aug 2026 05:55:06 GMT</pubDate>
    </item>
    <item>
      <title>How Rindler Works: You Describe the Task | Rindler</title>
      <link>https://rindler.ai/how-it-works</link>
      <guid isPermaLink="true">https://rindler.ai/how-it-works</guid>
      <description>The first run on a new site works out how to do it. Later runs repeat it. Describe the task in plain language, and hear about it when a run does not go through.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Sun, 09 Aug 2026 06:27:10 GMT</pubDate>
    </item>
    <item>
      <title>Automatically Download Bank Statements | Rindler</title>
      <link>https://rindler.ai/answers/download-bank-statements-automatically</link>
      <guid isPermaLink="true">https://rindler.ai/answers/download-bank-statements-automatically</guid>
      <description>Pull statements and transaction CSVs from your bank portal on a schedule. Rindler signs in the way you do, with no API and no aggregator in the middle.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Sat, 08 Aug 2026 08:18:23 GMT</pubDate>
    </item>
    <item>
      <title>How to automate reconciliation for service reps | Rindler</title>
      <link>https://rindler.ai/blog/automated-reconciliation-for-service-reps</link>
      <guid isPermaLink="true">https://rindler.ai/blog/automated-reconciliation-for-service-reps</guid>
      <description>Pull the statement, compare it to your own list, and get the mismatches back marked, on a schedule you set. What to decide before you hand the job over.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Fri, 07 Aug 2026 21:36:53 GMT</pubDate>
    </item>
    <item>
      <title>Connect Rindler | Rindler Docs</title>
      <link>https://rindler.ai/docs/mcp-setup</link>
      <guid isPermaLink="true">https://rindler.ai/docs/mcp-setup</guid>
      <description>Connect Claude Code, Cursor, Windsurf or Codex to Rindler&apos;s hosted service, or call it directly with curl. Setup steps, file locations, and keys.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Fri, 07 Aug 2026 06:19:36 GMT</pubDate>
    </item>
    <item>
      <title>Pull Applicants Without the ATS API | Rindler</title>
      <link>https://rindler.ai/answers/ats-data-without-the-api</link>
      <guid isPermaLink="true">https://rindler.ai/answers/ats-data-without-the-api</guid>
      <description>Get candidate records out of an applicant tracking system when there is no API, no admin access, and no engineer to ask, without rekeying them by hand.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Thu, 06 Aug 2026 06:25:27 GMT</pubDate>
    </item>
    <item>
      <title>When the Site Has No API | Rindler</title>
      <link>https://rindler.ai/blog/browser-vs-api-ai-web-agents</link>
      <guid isPermaLink="true">https://rindler.ai/blog/browser-vs-api-ai-web-agents</guid>
      <description>Integrations only reach sites that publish an API, and most portals never will. The rest of the work happens in the browser your team already signs into.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Thu, 06 Aug 2026 06:25:27 GMT</pubDate>
    </item>
    <item>
      <title>Rindler vs RPA and In-House Scripts | Rindler</title>
      <link>https://rindler.ai/compare</link>
      <guid isPermaLink="true">https://rindler.ai/compare</guid>
      <description>How portal work gets done today: RPA, in-house scripts, per-site integrations, or people rekeying by hand. What each one costs you when the page changes.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Thu, 06 Aug 2026 06:25:27 GMT</pubDate>
    </item>
    <item>
      <title>What It Takes to Automate a Site With No API | Rindler</title>
      <link>https://rindler.ai/docs/what-is-mcp-web-automation</link>
      <guid isPermaLink="true">https://rindler.ai/docs/what-is-mcp-web-automation</guid>
      <description>What automating a login-walled portal involves: structured records instead of raw pages, a session that survives, and knowing when a run did not finish.</description>
      <dc:creator>Rindler</dc:creator>
      <pubDate>Sat, 18 Jul 2026 00:12:32 GMT</pubDate>
    </item>
  </channel>
</rss>
