Terms of Service

1. About these terms

These terms govern your use of Toolspoke, a product of Guidenco, Inc., a Delaware C corporation (Delaware file number 7214918) with its registered office at 651 N Broad St, Suite 201, Middletown, DE 19709, United States. "We", "us" and "Toolspoke" mean that company. By creating an account, connecting a tool, or calling the gateway, you agree to them. If you accept on behalf of a company, you confirm that you are authorised to bind it, and "you" means that company.

2. What the service does

Toolspoke is a gateway between AI agents and the systems a team already runs on. A workspace installs connectors, which may be MCP servers, HTTP APIs described by an OpenAPI document, or command line tools. A project decides which of an installed connector's actions it allows, and Toolspoke exposes a single MCP endpoint that agents connect to.

When an agent calls a tool, Toolspoke resolves which member the calling agent key belongs to, limits the key to what that member can reach at that moment, applies the project's policy over the connector's actions and then the key's own grant, decrypts the credential for the connector, executes the call either in process or inside a sandboxed runtime, and writes a record of what happened.

Features change. We may add, alter, or withdraw parts of the service, and we will not remove something a paid plan is built around without notice. We will give at least 90 days' notice by email to organisation owners before withdrawing a feature that a paid plan is built around.

3. Accounts and organisations

An account is created with an email address and password, or through Google or GitHub where the operator of the deployment has configured those providers. You agree to give accurate information, to keep your sign-in credentials to yourself, and to be responsible for what happens under your account.

Every account belongs to at least one organisation. An organisation is the billing unit and the security boundary. Owners and administrators of an organisation can invite and remove members, change roles, install and configure connectors, and read the organisation's audit log.

That last point matters and is easy to miss: the audit log holds the full request and response payload of every tool call made in the organisation, including calls made by other members' agents. If you administer an organisation, tell your members that this is the case before they connect anything.

An agent key acts as the member it was issued to. Treat it as you would a password. If a key is exposed, revoke it. Calls made with a key are attributed to its owner and billed to the organisation.

4. Acceptable use

You agree not to use Toolspoke to:

• break the law, or infringe anyone's intellectual property, privacy, or other rights;
• connect a system you are not authorised to connect, or use a credential you were not authorised to use;
• reach another organisation's data, circumvent an access grant, escape the execution sandbox, or probe the service for weaknesses outside a disclosure we have agreed to;
• distribute malware, mine cryptocurrency, or run workloads whose purpose is to consume sandbox capacity rather than to do work;
• resell, sublicense, or proxy the gateway to people outside your organisation without a written agreement with us;
• copy the service in order to build a competing one; or
• degrade the service for others, by denial of service, by scraping, or by working around rate limits.

We may investigate suspected breaches and take action, which can include suspending an agent key, a member, or an organisation. Section 8 covers what happens then.

Reporting a security issue is welcome and is not a breach of this section. See Security for how to disclose one.

5. Your content and your credentials

Your content. Anything you or your agents send through the gateway, and anything a connected system returns through it, stays yours. We claim no ownership. You grant us the limited licence we need to host, transmit, process, and display that content for the purpose of operating the service for you, and for no other purpose.

Credentials you connect. API keys, OAuth tokens, and other credentials you connect are encrypted at rest with AES-256-GCM and are decrypted only in memory, only for the duration of a tool call that needs them. You are responsible for having the right to connect each credential, and for scoping it as narrowly as the work allows. A call your agent makes with a credential you connected is a call you made.

The systems you connect stay under their own terms. Toolspoke does not change your relationship with GitHub, Notion, Stripe, or any other provider. Their terms and their rate limits still apply to you.

Calls are recorded. Every tool call writes an audit record containing the full request payload and the full response payload. That is the product working as designed, and it means content passing through a tool call is stored. Do not route content through Toolspoke that you are not permitted to record. The Privacy Policy describes exactly what a record contains, and the Data Processing Addendum covers the processing terms.

6. Credits

Tool calls are metered in credits, pooled across the whole organisation rather than allocated per member.

• A call that runs on the direct path costs 1 credit.
• A call that runs in the sandbox costs 5 credits, because the sandbox has to queue, boot, and hold memory for the duration.
• Building a toolkit costs 10 credits per unit built.
• A call refused by an access grant, and a call naming a tool or an action that does not exist, are both rejected before any credit is spent. They cost nothing.
• A call that reaches the provider and comes back with an error still costs, because the work was done.

Purchased credits do not expire. Plan credits are granted per billed seat when a paid invoice is paid. When the balance reaches zero, calls that would cost credits are refused until you add more.

Credits are a metering unit, not currency. They have no cash value, cannot be transferred between organisations, and are not exchangeable for money. Purchased credits are non-refundable once bought, except where a refund is required by law, and except where we terminate your account for a reason other than your breach of these terms, in which case we refund the unused balance at the price you paid for it.

7. Plans, seats and billing

The free plan gives one seat and a starting credit balance. Paid plans are billed monthly per seat through Stripe.

Seat count is derived from the number of active members in the organisation. When membership changes, the subscription quantity is updated to match, and Stripe prorates the difference over the remainder of the billing period. Adding a member costs the seat price from the day they are added.

Payment details are collected and held by Stripe. We do not receive or store card numbers. Invoices, receipts, and payment method changes are handled through Stripe's customer portal.

If a payment fails, we may retry it and then suspend paid features until it clears. Suspension for non-payment does not delete your data.

Prices are shown exclusive of sales tax, VAT and any other transaction tax. Where we are required to collect such a tax it is added at checkout and shown before you pay; where the reverse charge applies, you are responsible for accounting for it. We will give at least 30 days' notice by email to organisation owners before a price change takes effect for an existing subscription, and a change never applies to a billing period already paid for.

In a self-hosted deployment, Stripe billing is optional and may not be configured at all. Where it is not, this section does not apply.

8. Suspension and termination

You can stop using Toolspoke at any time. Cancelling a paid plan leaves it active until the end of the period already paid for, after which the organisation returns to the free plan.

We may suspend or terminate access for non-payment, for a breach of section 4, or where continuing to serve an organisation would create a clear security or legal risk. Where it is practical to warn you first, we will.

After termination we may delete the organisation's data, including its audit records, its connectors, and its stored credentials. We keep it for 30 days after termination before deleting it, so that an account closed by mistake can be recovered and so that you have time to take what you need. During that window you can ask us at [email protected] for an export of your organisation's data. After it, deletion is permanent and we cannot recover the data.

9. Self-hosted deployments

Toolspoke can be run on your own infrastructure. In that case your database, your audit records, and your connected credentials live in your infrastructure, and securing, backing up, and retaining them is your responsibility, not ours. Whether any external service is involved at all depends on what you configure.

Running Toolspoke yourself does not make it open source. The source is not public, and no rights are granted beyond those stated in these terms. Running it yourself is permitted under these terms as a non-exclusive, non-transferable, revocable licence to install and operate Toolspoke for your own organisation's internal use, for as long as these terms are in force. It does not permit redistributing it, offering it to third parties as a service, or removing its notices.

10. Disclaimers

The service is provided as it is. To the extent the law allows, we make no warranty that it will be uninterrupted, error free, or fit for a particular purpose.

Two disclaimers specific to what this product does. First, agents are not deterministic. Deciding which tools an agent may reach, and how narrowly the underlying credential is scoped, is your decision and stays your decision. Second, access grants and the audit log are controls, not guarantees. They constrain and record what an agent does; they do not make misuse impossible.

We do not warrant that a third-party system you connect will stay available, keep its interface stable, or behave the way it did yesterday.

11. Limitation of liability

To the maximum extent permitted by law, neither party is liable for indirect, incidental, special, or consequential loss, or for lost profits, lost revenue, or lost or corrupted data, arising out of these terms.

Each party's total aggregate liability arising out of or relating to these terms is capped at the fees you paid us in the twelve months before the event giving rise to the claim. That cap does not apply to your obligation to pay fees that are due, nor to either party's liability for death or personal injury caused by its negligence, for fraud or fraudulent misrepresentation, or for any other liability that cannot lawfully be limited.

12. Changes to these terms

We may update these terms. The date at the top of this page changes when we do. For a change that materially affects your rights, we will give notice by email to organisation owners, or in the product, before it takes effect. Continuing to use the service after that point means you accept the updated terms.

We will give at least 30 days' notice before a material change takes effect. Where you have signed an order form or an enterprise agreement setting a different period, that period governs instead.

13. Governing law and venue

These terms are governed by the laws of the State of Delaware, United States, without regard to its conflict of laws rules. The state and federal courts located in Delaware have exclusive jurisdiction over any dispute arising out of them, and both parties submit to that jurisdiction.

Nothing in this section removes a protection that the law where you live gives you and does not allow to be contracted out of. If you are a consumer in the European Economic Area you keep the mandatory protections of your own country's law, and may bring proceedings in its courts.

14. Contact

Questions about these terms go to [email protected]. Other routes are listed on the contact page.