1. Acceptance and Operator
These terms govern your use of RequestBeam accounts, the console, APIs, and related services. By registering for or using these services, you agree to these terms, subject to any express consent required by law. Do not register or use them if you do not agree. Merely browsing the public website does not purchase services or authorize charges.
RequestBeam is operated by JenThoughful. In these terms, "we" means that service operator.
If you use the services on behalf of an organization, you represent that you have authority to accept these terms for that organization.
Personal data processing is described separately in the Privacy Policy. Section 11 explains the order of precedence for separate agreements, orders, and these terms.
2. Description of Service
RequestBeam provides unified account access, authentication, balance management, and usage records for AI models and selected data APIs. Different APIs may use different endpoints, request formats, protocols, and upstream providers.
The applicable service pages, documentation, and orders describe specific models, endpoints, data fields, billing units, limits, and regional availability. Input, output, and usage restrictions may differ between services.
You may integrate the APIs into your own applications, websites, workflows, or commercial products for end users, subject to these terms and the relevant service restrictions. Normal application integration is not the sale of an account or API key and does not automatically grant rights to standalone API resale, white-label API proxying, or redistribution of third-party data.
3. Accounts and API Keys
- You must provide accurate account information and are responsible for securing your account, password, OAuth login, and API keys.
- API keys are for you and your authorized systems only. Do not sell accounts or API keys, expose keys publicly, or place them in webpages, client code, or public repositories where end users can extract them. When serving end users, manage keys and access through a backend you control.
- You are responsible for managing authorized users and their requests through your account or API keys. If you discover a leaked key or unusual activity, promptly revoke affected keys and contact support to prevent further charges.
- You may dispute unauthorized calls or charges by providing relevant request and billing details for review. We will investigate using account, request, and billing records. This clause does not excuse responsibility for our billing errors, security negligence, or other causes for which we are responsible.
4. Data Sources, Acceptable Use, and AIGC Content Policy
This section applies to all users, developers, and their end users accessing services through the website, console, or APIs. It covers submitted prompts, reference materials, input files, and text, image, audio, video, or other outputs generated, stored, or distributed through the services. Do not use the services to submit, generate, or distribute the prohibited content below. Developers must communicate and enforce these restrictions for their end users.
- Pornography / NSFW: pornography, sexually explicit material, and other NSFW content are prohibited.
- Violence / gore: violent, gory, or violence-promoting content is prohibited.
- Hate speech: content inciting discrimination, hatred, or violence based on protected characteristics such as race, ethnicity, religion, gender, sexual orientation, or disability is prohibited.
- Child sexual abuse material (CSAM): any sexual content or exploitation material involving minors is prohibited, including AI-synthesized, generated, or modified content.
- Deepfakes / impersonation of real people: deepfakes, impersonation of real people, and content violating likeness, privacy, or personality rights are prohibited, including non-consensual synthetic sexual content.
- Copyright / trademark infringement: content infringing copyright or trademarks is prohibited.
- Zero-tolerance violations also include promoting or facilitating terrorism, extremism, or mass violence; inciting genocide or ethnic hatred; and providing technical instructions for weapons of mass destruction. Do not use jailbreak prompts or other methods to bypass content safety measures.
- You must comply with applicable law and the usage policies and license restrictions relevant to the models or data services you use. Consult the relevant service pages and documentation; contact support before use if upstream policies or the scope of authorization are unclear.
- Do not use the service for unauthorized scraping, access-control bypass, privacy violations, unauthorized access, or other unlawful activity.
- Do not submit, query, generate, or distribute data or content that you are not authorized to process or use, or that infringes third-party rights.
- Do not bypass rate limits, quotas, billing, provider restrictions, or other technical protections.
- Standalone API resale, white-label API proxying, and caching, display, or redistribution of third-party data must fall within the relevant service authorization. Paying for calls does not imply rights that have not been expressly granted. Confirm the applicable authorization or obtain a separate agreement before such use.
- If your application serves end users, manage their access and take reasonable measures to prevent unlawful use, key exposure, and circumvention of restrictions. We remain responsible for our own service provision, upstream selection, and obligations under applicable agreements; this clause does not transfer those obligations to you.
- Reporting: report suspected prohibited content or conduct by emailing [email protected] with the subject "Content report". Include available request IDs, content links, timestamps, reasons for the report, and any necessary evidence of your rights. Do not provide API keys, passwords, or other credentials. Do not download, attach, or forward suspected CSAM; provide only location information and a non-graphic description.
- Intake and review: after receiving a report, we assess its risk and urgency and review the submitted information and available account, request, and service records. Reports involving child safety, terrorism, or other serious risks receive priority. We may ask for additional non-sensitive information where needed. Related data is handled under the Privacy Policy.
- Enforcement: based on our findings, severity, and repeated violations, we may issue a warning, require the prohibited use to stop, or restrict, suspend, or terminate account and API access. Serious or urgent risks may warrant suspension before review without successive warnings. We cooperate with authorities where legally required. Access restrictions do not mean we can recall delivered outputs or delete copies held by users or third parties. Charges and balances remain subject to Sections 6 and 9.
- Notice and appeals: where legally permitted and without compromising security, privacy, or investigations, we inform reporters of the outcome and affected users of the action and its reason. To appeal a suspected mistake, use the same support email with the subject "Content appeal" and include the relevant request ID or enforcement notice, your reasons, and necessary supporting information. Do not send credentials or suspected CSAM. We review the additional information, communicate the outcome, and correct the relevant action when a mistake is confirmed.
5. AI Outputs, Data Results, and Validation
You retain rights to your inputs and are responsible for ensuring that inputs, queries, and intended uses are lawful and properly authorized. We may process inputs as necessary to provide the service and send necessary data to relevant providers as described in the Privacy Policy.
We do not claim ownership of your inputs or generated outputs because you use the service. Intellectual property protection and permission for a particular commercial use depend on applicable law, third-party rights, and the relevant model or service license. This clause does not guarantee copyright protection, exclusivity, or non-infringement for every output.
Data API results may be subject to source licenses and third-party rights. Paying for a call does not purchase ownership of the data or automatically grant permission to cache, publicly display, or redistribute it.
AI outputs and Data API results may be inaccurate, incomplete, delayed, or unsuitable for a particular purpose. Review them in proportion to the intended use and risk, especially before publication, commercial use, or important decisions affecting individuals. These results do not replace necessary professional judgment.
6. Billing, Balance, and Refunds
RequestBeam charges using the units and prices stated on the relevant service page, console, or order, such as tokens, requests, images, or seconds. Monitor usage, balances, and API key activity; rate limits, concurrency limits, and minimum balance requirements are not hard spending caps.
Some requests require a minimum available balance and reserve estimated charges from that balance before execution. A reservation is not the final charge. Settlement uses the applicable price recorded when the request was accepted and the actual billable units, returning excess reserved credits or deducting additional charges if actual costs exceed the reservation. The minimum balance requirement is not an extra fee, and later price changes do not retroactively change the price for that request.
For confirmed failed or cancelled requests that are not billable, reserved credits are returned to the available account balance. Releasing credits is not a cash refund of a top-up. A client timeout, disconnect, or decision to stop waiting does not automatically mean an upstream task was cancelled or incurred no charges. Uncertain outcomes or usage require review of task and upstream records before settlement or release of the reservation.
Usage that actually occurred and was correctly billed is not refundable solely because the output did not meet subjective expectations, unless an order, separate agreement, or applicable law provides otherwise. This restriction does not apply to duplicate charges, billing errors, or other billing disputes. Contact support with request identifiers and relevant records to request review and correction; do not send API keys or other credentials.
Refund eligibility for unused paid top-up balances, including the method, fees, and conditions, follows the refund rules expressly provided at purchase, the order or separate agreement, and applicable law. Contact support to confirm the applicable rules and submit a request. The restriction on refunds for consumed usage does not mean all top-ups are non-refundable and does not exclude statutory refund rights.
After a top-up refund or payment chargeback is confirmed, the corresponding credited balance is removed, which may leave insufficient available funds. We may reject new requests with insufficient balance and take necessary risk measures where there are reasonable grounds for fraud, unauthorized payment, or abusive chargebacks. A normal refund request is not itself a reason to suspend an account.
7. Availability and Changes
We work to keep the service stable, but we do not guarantee that any API, model, data field, upstream provider, price, limit, protocol, latency, or feature will remain available permanently.
We may modify, suspend, or discontinue parts of the service for maintenance, security, abuse prevention, provider changes, legal requirements, or product updates.
Where reasonably practicable, we will notify you of material pricing, functionality, or availability changes through service pages, the console, your account email, or other service notice channels. Urgent security, legal, or upstream interruptions may require immediate action. Charges for already accepted requests remain subject to Section 6; settlement and balances after discontinuation are addressed in Section 9.
8. Intellectual Property
RequestBeam's website, console, API documentation, trademarks, interfaces, software, and platform elements are owned by JenThoughful or its licensors.
You may use the APIs as documented to develop your own applications and use SDKs, documentation code examples, and other expressly available materials under their applicable licenses. Unless authorized or permitted by applicable law, do not copy, distribute, or reverse engineer the platform itself, misuse our trademarks, or claim an official partnership or endorsement that does not exist.
These platform intellectual property restrictions do not cover your own applications, inputs, or generated outputs and do not prevent the normal API integration allowed in Section 2. Section 5 addresses rights in inputs, outputs, and third-party data.
9. Suspension, Termination, and Outstanding Charges
Where we have reasonable grounds to believe that you materially breach these terms, fail to pay due charges, abuse the service, threaten platform security, or that continued service would violate law or applicable provider requirements, we may impose restrictions, suspension, or termination proportionate to the risk.
Where legally permitted and without compromising security or abuse investigations, we will provide the reason and feasible steps to address the issue. You may request review through support; urgent risks may require suspension before investigation.
You may stop using the service and revoke API keys; contact support to close an account. Revoking a key or closing an account does not automatically cancel tasks already executing upstream. Related usage and reservations remain subject to review under Section 6.
After termination, both parties must still reconcile valid charges incurred beforehand, in-progress requests, and unreleased reservations. Suspension or termination does not itself forfeit unused paid balances. Remaining paid balances, including when we discontinue the service, are handled under the applicable refund rules in Section 6, the order, any separate agreement, and legal requirements.
10. Limitation of Liability
RequestBeam is provided with the functionality and availability actually offered. Unless expressly agreed separately, we do not guarantee that AI outputs or third-party data will always be accurate, uninterrupted, suitable for all purposes, or achieve a particular business result.
To the extent permitted by applicable law, we are not liable for indirect or consequential losses arising from use of the service, including indirect lost profits or business interruption losses. This clause does not exclude responsibility for billing errors, failure to perform expressly agreed service obligations, or other matters for which we are legally responsible.
These terms do not limit liability for fraud, intentional misconduct, gross negligence, personal injury, or other liability and statutory rights that applicable law does not allow to be excluded or limited. Upstream provider involvement does not excuse our own obligations.
11. Updates and Order of Precedence
We may update these terms as services or legal requirements change and will identify the version and effective date on this page. Where reasonably practicable, we will notify you of material changes to fees, usage rights, or other important rights and obligations through account email, the console, or other service notice channels. We will obtain separate consent where required by law.
New terms apply to service arrangements formed after their effective date in accordance with applicable law, not retroactively to the billing conditions of already accepted requests or rights and obligations already incurred. If you do not accept a change, stop submitting new requests and contact support about account closure and balance handling.
A service agreement separately entered into with you takes precedence over these general terms. Prices, refund rules, or usage conditions expressly stated in an order or service page for the relevant service take precedence over general descriptions here, but cannot exclude mandatory rights under applicable law. Contact the operator through the support channel below about questions or disputes; these terms do not restrict your right to seek remedies under applicable law.
Terms Questions, Content Reports, and Appeals
Send questions about these terms, content reports, or appeals to JenThoughful at [email protected].