Terms of Service

Draft — last updated 7 October 2026

What this service does

Inline sits between your AI agents and the services they call. You connect sources (MCP servers and REST APIs), decide which operations an agent may use, and set rules, such as holding a call until a person approves it. When an agent makes a call, Inline checks it against those choices, makes the call to the service using your credentials, hands the result back, and records that the call happened.

The service is operated by Agentic Users, a business of 1001538151 Ontario Inc. (Ontario, Canada). What we do with data is described in the privacy policy, which is part of these terms.

We hold credentials for services you connect

This is the unusual thing about Inline, so it gets its own section.

• What we hold. To act for you, Inline stores the credentials for the services you connect: OAuth tokens, client secrets and API keys. An agent is given a tool it may call, not the credential underneath it.
• We can read them. Our servers open those credentials at the moment of each call in order to use them. Most are sealed with a key held in Google Cloud KMS, which protects them from a copied database. It does not stop the service, or a person who administers it, from obtaining them. REST API keys, whether you register one for the API or each person adds their own, are sealed the same way, with your workspace’s key, and stored in your workspace. The exact split is in the privacy policy.
• A call is made as you. When Inline uses a credential, the service on the other end sees you (or the account that credential belongs to) making the call. What it does, it does on your account, under that service’s terms.
• You must have the right to hand them over. By connecting a service you tell us you are allowed to give Inline that access, and that doing so does not break your agreement with that service. Inline does not remove any limit that service places on you.
• Our controls are not a guarantee. Scopes, rules, approvals, limits and loop brakes are there to stop an agent doing what you did not intend. They are software, and software has bugs. A call you meant to be refused might go through. Do not rely on Inline as the only thing standing between an agent and something you cannot afford to have done.
• Undoing. Disconnecting a source deletes our copy of the credential and we then try to revoke it at the provider. Many providers offer no revocation, and a call already made cannot be recalled. Where revoking did not work we tell you, and you must revoke access in that service yourself. Closing a workspace does not revoke anything at the services you connected.

Your account

You are responsible for who you invite into your workspace and what you allow them to connect. An administrator can see the workspace’s activity log, which records who called what and, by default, the arguments they sent (with credential-looking values removed).

• Keep your agent keys secret. A key acts as the person it was issued to, within its scope, until it is revoked.
• You are responsible for what your agents do through Inline, including calls made by scripts an agent wrote and by apps you install.
• Every person in your workspace signs in as themselves. Do not share a sign-in.
• Do not use Inline to break the law, to break a service’s terms, to attack or overload a service, or to get around a limit or a control we or anyone else has set.
• Tell us if you think a credential, key or workspace has been exposed: contact@agentic-users.com.

Plans, limits and paying

There is a free plan and paid plans. Each has limits on calls per day, people, sources and installed apps; the current ones are on the pricing page. Calls over a limit are refused and you are told which limit you hit. Payment is taken by Stripe, and a paid plan is charged to the card you give at checkout.

We will tell workspace owners by email at least 30 days before a price change takes effect on their plan. Refunds, taxes, and when a cancellation takes effect are not settled to confirm. Nothing on this page promises a refund.

Availability

This is an early product. It is offered as it is, without a service level commitment. Do not place it in the path of anything you cannot afford to have fail.

We keep backups of the databases for our own recovery. We do not promise that any data can be recovered for you, and we have not yet shown that a restore works end to end. Keep your own copy of anything you cannot lose, such as the source of tools you have saved.

We do not have a SOC 2 report, an ISO 27001 certificate or any other audit or certification. Nothing on this page or on our website says we do.

Apps and the marketplace

You can publish an app for other workspaces to install, and you can install apps others published. An installed app runs in your workspace, against the sources your workspace has connected. Before it runs, you are shown which of your systems it would touch. What you publish is your responsibility. Paid listings are not available: you can publish, you cannot charge.

Ending it

You can stop using Inline at any time. Revoking an installed app or a key stops further calls immediately; it cannot undo calls already made, and the product says so where it matters rather than implying otherwise.

• Cancelling a paid plan. Your workspace falls back to the free plan’s limits. Nothing is deleted because a subscription lapsed. You keep your sources, tools and records. The one thing that is destroyed is a key of your own, if your plan included one: your credentials are first returned to the shared key, after at least 7 days’ notice to the owners, and the key is destroyed after that.
• Closing a workspace. An owner can close it. It stops serving at once, and the owner can still read it and reopen it for the grace period (30 days, never fewer than 7). Closing does not cancel a subscription; cancel it separately or it will keep being charged. A closed workspace keeps its own key, if it has one, until it is erased.
• What happens after. When the grace period ends, we erase the workspace. A person at Inline does this by hand, within 30 days after the grace period ends. Erasure removes most of what is in the workspace. It keeps billing records, the administrative record and marketplace publisher records; it cannot reach Google Cloud log entries, or copies held by services you connected; and backups keep copies for up to 14 weeks. The full list, of what is deleted, what is kept and why, is in the privacy policy.
• We can stop it too. We can suspend a workspace, which stops it serving in the same way as closing. We would do this for security, abuse or non-payment. Where we can, we tell the owners first and say why; where there is a security risk or abuse in progress we may act first and tell you straight after.

Liability and the rest

The service is provided as it is, without warranty. What we owe you if something goes wrong, the limits on it, how disputes are decided and under what law, indemnities, and how these terms change are left for a lawyer to settle to confirm. Until they are, do not read the absence of a clause here as a promise in either direction.

Still open

• Governing law and where disputes are decided.
• Refunds, taxes, and when a cancellation takes effect.
• The limits on our liability, and any indemnities.