Public API Terms of Use
API access, integration responsibilities, consumption, availability and data exit under the agreement.
Public API Terms
ALTA ÓRBITA TECNOLOGIA E INTELIGÊNCIA ARTIFICIAL LTDA., trading as Revvea, CNPJ 69.486.386/0001-90, Av. Francisco Campos, 849, Centro, Dores do Indaiá/MG, Brazil, ZIP 35.610-000.
These documents explain the Revvea Flow agreement and Revvea Agents when purchased. Growth Station branding and current domains remain unchanged. Legacy documentation does not expand purchased scope; earlier agreements follow their instruments. The signed agreement and Portuguese version prevail.
The Schedule and amendments prevail as provided in the agreement. Documentation cannot unilaterally change prices, scope, processing purposes, retention or safeguards; continued API use is not a substitute for commercial acceptance.
Access and integrations
Access depends on purchased features and project permissions. Protect credentials, use least privilege and revoke unauthorized access. Do not resell/share access without permission, bypass controls, access other projects or submit excessive data.
Integrators must validate inputs, handle errors, observe endpoint technical limits, implement safe retries and secure their systems. Technical rate limits are not a price or commercial allowance and do not activate unpurchased features.
Customers and their providers build, implement, adapt, operate and maintain external integrations. Revvea work requires a separate agreement. Native mechanisms remain subject to Revvea's own obligations.
Consumption and changes
Use follows the Schedule and Annex A: two wallets, contracted tariffs and continued overage. Purely technical retries must not duplicate charges, and internal processing variation alone does not create new fees. Expansion requires express authorized acceptance after items, quantities, prices, periods, activation, billing and proration are shown.
Technical changes preserve essential purchased functionality. Commercial/data changes follow contractual notices and valid agreements, rather than a generic 15-day or continued-use rule.
Availability, suspension and data
Essential covered services follow the 99% monthly target, evidence, exclusions and financial credits in the Terms. Scheduled maintenance requires 15 calendar days' notice. Own configuration, management or payment failures are not generically excluded as third-party faults.
Business-day support, 9 a.m.–6 p.m. Brasília: critical first response four business hours, high eight, medium two business days, low five; not resolution times. Contact support@revvea.ai.
Justified security/legal/prohibited-use restrictions follow the agreement. Nonpayment may lead to suspension after ten calendar days overdue by email notice, preserving data/credentials. Elapsed suspension time does not trigger irreversible cleanup.
Export does not require an active API key or extra license: assisted delivery remains available after operational blocking, without restarting Cadences or unauthorized consumption. Formats, periods and deletion follow the Privacy Notice.
Responsibility and intellectual property
Revvea remains responsible for attributable obligations/faults, with causal assessment and selection, instruction, configuration, management and mitigation duties. There is no blanket exclusion for all API interruptions. The customer is responsible for its own integrations and use.
Liability limits/exceptions, confidentiality and rights follow the signed agreement and Terms. The API does not transfer platform code, technology or base prompts; customer data remains within its rights, respecting data subjects and third parties.
DPO: João Pedro Santos da Costa — privacy@revvea.ai. Previous editions.
Your feedback matters
Did this guide answer your question?
It only takes a few seconds and helps us keep the knowledge base useful.