Responsibility and costs

An API token acts as you. What it does is done in your name, in your organization, at the providers you have connected to InfraNest. This page says what that means in practice.

You are responsible for what your tokens do

• A change made with a token is your change. It appears in the organization's audit log next to changes made in the app.
• Keep tokens secret and give each one only the scopes it needs (see Tokens and scopes). Anyone who holds a token can do what it allows until you revoke it.
• Test scripts and automations before you point them at production infrastructure.

Actions can cause costs

InfraNest refuses some actions to tokens altogether, such as ordering domains or servers. Everything a token can do still reaches your providers, and that can cost money:

• Your providers decide their own prices. Some charge for API calls, DNS queries or changes, or for resources that a change keeps running. InfraNest does not control or refund those costs.
• Your plan's limits apply. Monitors, checks and other resources a token creates count against your plan, exactly as when you create them in the app.
• Mistakes cost the same as intentional changes. A script that loops, or a token that leaks, can make many changes quickly. Rate limits slow that down, but do not prevent it.

Before you automate

• Check the pricing of the providers your automation will touch.
• Start with a read-only token and a dry run where one is available.
• Watch the audit log after your first runs.

The terms that apply to using InfraNest, including through the API, are the Terms of Service.