API & MCP Terms of Use
These Terms govern programmatic access to Valkiria through the public API v1, the MCP server and OAuth apps. Keep your keys secret, stay within the rate limits and scopes, and remember that write operations follow the same approval rules as the app.
1. Scope
1.1 These API & MCP Terms supplement the /terms and apply to the Valkiria public API v1, the Model Context Protocol (MCP) server, the OAuth 2.1 authorisation server for third-party apps, and any API keys, tokens and documentation we provide (together, the ‘API’).
1.2 Use of the API also remains subject to the /legal/acceptable-use, the /legal/ai-terms and, for personal data, the /legal/dpa.
2. Availability
2.1 API keys for the public API v1 are included in the Pro plan, and in agency arrangements where per-client keys are enabled for the account. Other plans do not include API keys.
2.2 We may change, version or deprecate endpoints and MCP tools. We aim to announce breaking changes to generally available endpoints in advance, except where an immediate change is needed for security or legal reasons.
3. API keys
3.1 API keys (prefix vk_live_) are sent as Bearer tokens. We store only a hash of each key, so a lost key cannot be shown again; create a new one and revoke the old one.
3.2 Each key carries scopes, for example reports:read, campaigns:read, campaigns:write, analytics:read, leads:read, rules:read, rules:write, content:read, content:write, smm:read, seo:read, aso:read, ai:generate and portal_users:manage. Use the narrowest scopes you need.
3.3 Keys may be limited to a single client workspace. A client-limited key cannot be used to access other clients or partner functions.
3.4 You are responsible for all activity carried out with your keys until you revoke them.
4. OAuth apps and MCP clients
4.1 Third-party apps and AI assistants connect through OAuth 2.1 with dynamic client registration. Only the authorisation code flow with PKCE (S256) is supported. Refresh tokens rotate on use and can be revoked.
4.2 Two scopes are available: ‘read’, which allows reading data, and ‘propose’, which allows creating paused drafts and proposals only. The ‘propose’ scope never activates campaigns or increases spend.
4.3 The person who authorises an app is responsible for choosing apps they trust. You can revoke an app's access at any time in your account settings.
4.4 If you build an app for others, you must give your users an accurate description of what your app does with their data and must not request access you do not need.
5. Write operations and approval rules
5.1 Changes made through the API or MCP are subject to the same write policy as changes made in the app, including your autonomy level, limits, emergency stop and the requirement of human approval for deletions, new spend and irreversible changes. These rules are described in /legal/ai-terms.
5.2 You are responsible for the consequences of changes you make or approve through the API, including ad spend on the connected platforms.
6. Rate limits and fair use
6.1 The public API, the MCP server and the OAuth endpoints share a rate limit of 100 requests per minute. We may adjust limits to protect the Service and will reflect current limits in the documentation.
6.2 Requests above the limit are rejected. Do not try to circumvent limits, for example by using multiple accounts or keys for one workload.
7. Prohibited uses
- Scraping or bulk extraction of the Service, other customers' data or our knowledge content, beyond your own account data.
- Reselling, sublicensing or offering raw API access to third parties as a standalone service, except under the /legal/partner-terms or a written agreement.
- Building a competing product by copying our outputs, prompts or interfaces.
- Probing, load-testing or attacking the API, except as allowed by the /legal/security-policy.
- Using the API to bypass advertising platform policies, approvals or limits.
8. Key security
8.1 Keep keys and tokens out of public code repositories, client-side code and shared documents. Rotate them regularly and immediately if you suspect exposure.
8.2 Tell us without delay at support@valkiria.pro with subject ‘Security’ if a key or token is compromised.
9. Suspension and revocation
9.1 We may suspend or revoke keys, tokens or app registrations where we reasonably believe they are compromised, are used in breach of these Terms, endanger the Service or other customers, or where required by law. Where possible we will tell you the reason.
9.2 Keys stop working when your plan no longer includes API access or your account ends.
10. No warranty
10.1 The API is provided under the service and liability terms of the /terms. We do not guarantee uninterrupted availability; see /legal/support-policy.