What do I download to connect my AI agent to FlipperForce?

Disclaimer: FlipperForce does not provide tax, legal, or accounting advice. This report and FAQ are for informational purposes only and should not be soley relied upon for tax compliance. Because IRS rules are complex and subject to change, we strongly recommend consulting with a qualified tax professional or accountant before making business decisions or filing returns.
Download our setup kit, or grab the files individually. It contains the Public API Agent Guide your assistant reads, templates for your business context, and a Project instructions block.

There is no FlipperForce app to install inside Claude or ChatGPT. Your assistant talks to us the same way any other program does: authenticated requests to our Public API, using a key that belongs to you.

That means three things have to be true before it can do anything useful. It needs permission to reach us over the network. It needs your API key. And it needs to know what our API actually offers, because otherwise it guesses at endpoints and burns your session finding out what does not exist.

The files below handle the third one and give you templates for the rest. Current version: 2026-08-31. Every file carries its version at the top, so you can tell whether the copy in your Project is current.

Everything at once

Download the FlipperForce + Claude Setup Kit — every file below, organised into folders by where it goes. Start here if you are setting up for the first time.

Files that go in your Project's knowledge

  • Public API Agent Guide — the capability reference our engineering team maintains. Every endpoint, the authentication format, how pagination and totals work, the three-stage flow for uploading receipts and photos, and the rules an assistant should follow before changing your data. This is the file doing the heavy lifting, and it is written for your assistant to read rather than for you.
  • Company profile template — who you are, how you run your flips, what you want help with. This is the file most people skip and the one that makes the biggest difference to what you get back.
  • Chart of accounts template — your expense categories and how you actually use them. Two investors with identical category lists often code the same receipt differently, so the edge cases matter more than the obvious ones. This is what makes automated categorization accurate instead of plausible.
  • Workspace reference template — a lookup sheet of your workspace UUID, project UUIDs, expense accounts and stage labels. Fill this in after your first session so your assistant stops re-deriving the same values every time.

Your API key belongs in this group too. Read Is it safe to give an AI agent access to my FlipperForce data? first, because where you keep the key is a real decision rather than a formality.

The file that goes somewhere else

Project instructions — paste this into your Claude Project's custom instructions field, not into knowledge. It keeps your assistant read-only by default and makes it show you every change before saving.

This is the distinction worth getting right. Putting the instructions into knowledge instead of the instructions field is the usual reason a setup half-works: the assistant can reach your data but nothing is stopping it from writing to it unasked.

For you, not for your assistant

Setup checklist — work top to bottom the first time. Do not upload this one. Keeping your Project's knowledge tight gives you better answers than loading it with everything you have.

Then what

Follow How do I connect Claude to FlipperForce? for the network settings and the verification steps. If something fails along the way, My AI agent cannot connect to FlipperForce covers the usual causes.

Related Video

Avatar photoAvatar photoAvatar photo

Still Have Questions?

Can’t find the answer you’re looking for? Please chat to our friendly team.