ChatGPT, Claude, and automated access
Send the inputs. OpenBooks starts the books.
Connect an AI assistant, workflow, or internal tool to one organization. It can stage transaction inputs, receipts, and instructions in the right books. OpenBooks preserves the source and records every successful change in History. You get a review link before those inputs are approved.
1
Create or choose the organization
Sign in once. OpenBooks will ask you to create an organization only if you do not already have one, and will ask you to choose when you manage more than one. A credential can access only the organization you select.
2
Create a key for this connection
The setup path opens Settings → API & webhooksfor the selected organization. Name the key for the client that will use it, choose read-only or update access, and copy theobk_… value when it appears. New keys are read-only unless you explicitly allow updates.
3
Verify the connection, then send transaction inputs
Call whoami first. It returns the organization, role, and production or sandbox mode associated with the key.
curl https://openbooks.fyi/api/v1/whoami \
-H "Authorization: Bearer obk_your_key_here"Store the key as a secret. These two environment variables are enough for a client to find the authenticated API:
OPENBOOKS_API_KEY=obk_your_key_here
OPENBOOKS_API_URL=https://openbooks.fyi/api/v1The submit_transaction_inputs tool accepts up to 100 signed USD transactions in one retry-safe batch. Every new item lands in Needs judgment, and the response includes the exact OpenBooks review URL. It never approves, publishes, or submits a filing.
MCP availability
A public MCP installer is not live yet. The repository MCP package uses the authenticated tenant-scoped API, but its npm package is not published and OpenBooks does not currently expose a remote/api/mcp transport. Use the authenticated API today. We will put a copy-and-paste MCP installation here only after the public transport is tenant-scoped and passes a live installation test.
Never put an OpenBooks key in a prompt, repository, browser bundle, or public configuration. Store it as a secret and revoke it from the organization’s settings if it is exposed.