Questions about the tools.
What you can read without an account, what the separate Tools sign-in is for, what the monthly price includes, and what happens at the end of a billing cycle.
- Do I need an account to see the catalogue?
- No. The whole catalogue is public and every agent has its own page, with the job, who it is for, what it reads, what it produces, the step it stops at, and what it is not. Browsing, reading a detail page and comparing them need no account and never will. An account is what you make to run one.
- Is a Tools account the same as my VoyantIQ account?
- No, and this page used to say it was. The Tools application runs on its own platform at https://tools.voyantiq.com, with its own database, its own sign-in and its own workspaces. A voyantiq.com account — the one that buys an application — is not a Tools workspace account, and a session on this site cannot reach anything there. You make the Tools account over there, when there is finally something to run.
- What can I actually subscribe to today?
- Nothing. The five jobs in the catalogue are concepts: specified, and not built. One further package, the Bill Difference Checker, is built in the Tools repository and has not been published to the live catalogue. The live catalogue itself publishes nothing today. Those are three different states and the catalogue page shows which one each thing is in.
- What will it cost?
- $29 USD a month, per agent, per workspace. $79 USD a month, per agent, per workspace. Per agent means one subscription covers one agent; per workspace means a second workspace running the same agent is a second subscription. A tier is only ever attached to an agent whose workload genuinely supports it — an empty tier on a page to fill out a table is not an offer.
- What does the monthly price include?
- An allowance, counted in a unit you can see rather than in tokens or compute: documents processed on the Standard plan, reports completed on the Advanced one, and every published agent names its own unit on its own page before you subscribe. The size of that allowance is still being set, because real model, interface, retry, infrastructure and support cost is being measured against actual runs first. No number of runs is published here, nothing is described as unlimited, and checkout stays closed until the number exists.
- What counts against the allowance, and what does not?
- A unit is counted once when the agent finishes work on it, whether the result is a clean pass or an exception held back for you. A retry the agent starts by itself is part of the same unit and is never counted twice. A run that pauses for your permission is not counted again when you answer. A run you cancel before it reads anything is not counted at all. Resubmitting an item after you change it is new work and counts again.
- What happens when the allowance runs out?
- The agent pauses and waits rather than quietly continuing and billing you for it. Nothing is charged beyond the plan price unless you buy a top-up on purpose. There is no automatic overage, and there will not be one without it being on the page before you subscribe.
- What will it do without asking me?
- Reading, checking, comparing and drafting. None of those change anything outside your own workspace, and an agent that only does those has no external change to approve — giving it an approval button on every calculation would be theatre, and theatre is how people learn to click through the prompt that actually matters. Permission is required before a consequence: sending, paying, posting, deleting, paging somebody, opening a ticket. The thing it is asking about is shown in full rather than summarised.
- What can it read, and what do I have to connect?
- Each agent's page lists the kinds of source it works from. They are categories — an invoice document, a billing export, a diff — not named integrations, because no integration has been built yet and naming one would imply it exists. When a real connection is supported it is named on the agent's own page, and it runs on an account you connect yourself inside your Tools workspace.
- What happens to my data, and can other customers see it?
- Each Tools workspace has its own isolated tenant data, and the separation is proved against a real database by a test that builds a second account realm and watches the session be refused. That is a test that runs, not a policy statement. Your connected accounts stay yours; this storefront holds no Tools session and never sees your workspace contents.
- If I cancel, when does it actually stop?
- At the end of the billing period you have already paid for, not on the day you click cancel. This page used to say it stopped the day you stopped paying, which understates what you have bought. The entitlement system this studio already runs works the other way: cancelling marks the subscription as not renewing, the access it granted stays active until the paid-through date, and only then is it revoked. Nothing is pro-rated back, and nothing stops early. Tools billing itself is not built yet, and when it is it follows that same model.
- Can I get my work out, and what is kept afterwards?
- Export is part of the product rather than a favour: what an agent produced for you is yours to take, in the format it produced it in. The retention period after an account closes will be stated on this page with a number in it before anybody can subscribe — it is not stated yet because the billing and account lifecycle it depends on is not built, and inventing a figure now would be a promise nobody has implemented.
- What happens when a run fails?
- A failure is reported rather than retried silently until it looks like a success. A retry the agent starts by itself is part of the same unit of work and is not counted against your allowance a second time. A run that cannot finish does not count. The record of what it looked at and where it stopped is yours to read.
- Is this the same thing as buying an application?
- The opposite, deliberately. An application is bought once, transferred to you, and runs on your infrastructure without us. A tool is never owned, runs on the Tools platform, and ends when you say so. Different purchase, different commitment, different kind of customer — and, as above, a different account.
- What do you publish about each tool, and what do you not?
- Published, on a page anybody can read without an account: the name, the job, who it is for, the kinds of source it reads, the run step by step, what it produces, the step it stops and asks you about, what it is not, the price once there is one, and whether it is available. Never published anywhere, including in the page's own markup and structured data: the instructions it runs on, where exactly it draws its lines, the cases it has to pass before it ships, how it is wired to the things it uses, which model it runs on, and what it does when something fails. What it does is public. How it decides is not.