OpenTools procurement policy evidence
Only topics backed by verified findings appear below. Each row preserves the platform's exact policy words and capture provenance.
| Topic | Plan or tier | Risk | Their words | Source |
|---|---|---|---|---|
| Subprocessors & data sharing | All applicable tiers | unknown | “ OpenTools is an external service aggregator for AI models, providing an API and a user interface at opentools.com (“Services”). The API can be used by developers to interact with a variety of large language models, generative image models, and generative 3D object models. OpenTools uses OpenRouter to route user API requests to the AI model of their choosing, among other vendors and services. Applications that developers build can be shown publicly on OpenTools. OpenTools also offers a registry site for showcasing capabilities of Model Context Protocol (MCP) servers. This registry is provided as a public good on a best-effort basis and is not a paid service. The information in the registry may occasionally be outdated or inaccurate. While we strive to maintain the registry's accuracy, we make no guarantees regarding the completeness, reliability, or timeliness of the information provided. OpenTools is in beta; we may change or discontinue any part of the Services at any time, including the availability of certain models or integrations. Some services are marked as (“experimental”) on their service pages - these services are being evaluated to see if they receive enough usage to be economical for us to maintain. They may be removed at any time. If a non-experimental service needs to be removed, you can expect the following: We will provide a notification in the OpenTools community Discord server. For a certain period of time, we will re-route requests for that service to another service of similar price and capability when possible. After a grace period of at least 2 weeks, we will stop re-routing requests for that service and will return a 404 error instead.” | Captured 2026-09-25Open source →Finding permalink → |
| Tier differences | All applicable tiers | medium | “ Developers can pay for services themselves, or they can have Users pay by using the OAuth flow to let Users sign in with their OpenTools settings and billing. Pricing for services is available on our pricing page, and varies by service and whether a discount is applied. Users can pay for services by purchasing credits using a payment card. Credits are non-refundable. Credits can be used to pay for services, and can be topped up at any time. While OpenTools is in beta, credits may expire 12 months after purchase. OpenTools uses Stripe to securely process payments. See their terms of service. Credits purchased via credit card incur a total fee of 5% + $0.35. In the event that we receive a fraud dispute on one of your payments, or any chargeback related to fraud, you will lose credits equal to the amount of the chargeback plus the fee levied by Stripe for handling the dispute (currently $15). If you are a business and would like invoices for each payment, Stripe charges an additional fee of 0.4% per invoice, capped at $2 per transaction. When using your own provider API keys (via integrations), we will deduct credits from your account equal to 5% of the cost of the request, calculated using the pricing listed on OpenTools at the time of the request. We may change our pricing at any time. If we do, we will provide notice of the change on the OpenTools website or Services.” | Captured 2026-09-25Open source →Finding permalink → |
Informational only, not legal advice. Terms can change; verify every cited source and capture date during procurement review.
📢 POLICY UPDATES ALERT
AIRIN Brief
Built for compliance officers, legal counsel, and SaaS founders. Subscribe to the email digest — one short brief when a tracked vendor materially changes its terms, training policy, or risk rating. Prefer in-app? Watch platforms in your alerts inbox instead.