Legal
Terms of Service
Monthly tier and Free Model allowance update effective 31 October 2026. Read the updated limits.
1. Agreement and Interpretation
These Terms of Service ("Terms") govern access to and use of asAi, operated by Fibonacci Ventures ("we", "us", or "our"). By creating an account or using the Service, you agree to these Terms. If you do not agree, do not create an account, purchase credits, or use the Service.
In these Terms:
- Service means the asAi API gateway and its related website, account dashboard, and service-administration features.
- You means the person using the Service or, where properly authorised, the organisation on whose behalf that person acts.
- Account means the registered account through which access and credits are administered.
- API key means a credential issued for authenticating requests to the Service.
- Credits means prepaid service units recorded in an account and applied toward eligible usage at the applicable rates.
- Input means prompts, conversation context, attachments, parameters, or other content submitted for processing.
- Output means content returned in response to an Input by the AI infrastructure accessed through the Service.
- Upstream providers means third-party infrastructure providers involved in processing requests and generating Outputs.
References to applicable law include mandatory requirements that cannot lawfully be excluded by contract. Section headings are for navigation and do not narrow the meaning of a provision.
2. Nature of the Service
asAi provides gateway access to third-party AI language models and related supported capabilities under branded model aliases. We route eligible requests to underlying infrastructure and return the resulting responses. We do not represent that we develop, own, or independently operate every underlying model.
A model alias is an asAi-facing identifier, not a guarantee of a particular upstream organisation, immutable model version, or permanent set of capabilities. Routing, availability, and supported parameters may vary. Descriptions and status information are informative but do not constitute a service-level agreement or guarantee that every request will succeed.
Specific upstream relationships and routing arrangements are treated as confidential commercial information. We do not ordinarily disclose which provider serves a particular alias. This position remains subject to disclosure obligations under applicable law and does not authorise misleading statements about the Service.
Unless expressly agreed in writing, the Service does not include dedicated capacity, guaranteed uptime, guaranteed response times, a particular processing location, or a customised data-processing agreement. Confirm suitability before using it for a workload that depends on such commitments.
3. Eligibility and Authority
You must have the legal capacity and authority required to enter into these Terms in your jurisdiction. Where applicable law requires authorisation from a parent or legal guardian, that authorisation must be obtained before use and the responsible adult must supervise the use as required by law.
If you use the Service on behalf of an organisation, you represent that you are authorised to bind it to these Terms. You must not create an account using another person's identity without authority or provide materially false account information.
You are responsible for ensuring that your use is lawful where you access the Service and where you deploy any application that uses it. Availability of the website or API in a location is not a representation that every proposed use is lawful there.
4. Registration, Verification, and Account Responsibilities
New customer registration is available through Google OAuth. Existing email and password accounts may continue to sign in. Keep your account email and relevant information accurate and accessible so that you can receive payment and security communications.
Unverified accounts cannot generate API keys, run inference, or redeem credits until verification is completed. Creating an account does not guarantee approval of a payment, access to every feature, or uninterrupted access to every model.
You are responsible for protecting your password, signed-in sessions, devices, and integrations. You are also responsible for use by people you authorise to access your account. Contact us promptly if you suspect compromise or an unauthorised change. Do not attempt to recover an account by submitting another person's confidential information.
We may request information reasonably necessary to investigate an ownership, payment, fraud, or security issue. Failure to provide information necessary to resolve such an issue may limit our ability to restore access or complete a transaction.
5. API Keys and Credential Security
API keys issued by the Service use the prefix asai_sk_. A valid key permits requests to be attributed to its associated account and may allow chargeable usage against that account's balance.
Stored API key material is encrypted at rest. Eligible keys may be retrieved through authenticated account functions, and restricted administrative retrieval is supported. Administrative key-reveal actions are audit-logged. Encryption should not be interpreted as a promise that keys are irretrievable or visible only at initial issuance.
Do not publish keys in source repositories, screenshots, public messages, client-side code accessible to untrusted users, or shared configuration files. Apply appropriate controls in any application that holds a key. Account access and key-management access should be treated as sensitive.
If a key may have been exposed, revoke or rotate it through available controls and notify us promptly. If you cannot do so, contact support for assistance. Revocation prevents subsequent authorised use of that key but does not automatically reverse usage already incurred. We will assess disputed usage according to the available records and applicable law; key attribution alone does not remove any mandatory rights you may have concerning unauthorised activity.
Support should not require you to send a complete API key or password through ordinary correspondence. Provide non-secret account or request references instead.
6. Prepaid Credits and Top-Ups
The Service operates on a prepaid credit basis. Sufficient available credits are required for eligible chargeable requests, subject to the Service's balance checks and metering arrangements.
Top-ups are purchased through the supported QR-transfer process. The purchase quantity, applicable coupon, and total shown at confirmation should be reviewed before you initiate payment through your banking application. Verify the payment details and transfer the correct amount using the required reference, if provided.
Credits are applied after payment has been confirmed. Sending a transfer or submitting a receipt does not itself establish that a payment has been received and reconciled. If a payment is delayed, incomplete, duplicated, or cannot be matched, contact us with the relevant transaction reference and appropriately redacted evidence. Do not make repeated payments merely because the first is still being reviewed.
The confirmed purchase total governs that purchase, subject to correction of genuine errors and mandatory legal requirements. Future prices or offers may differ. A purchased credit balance does not guarantee that a particular model or consumption rate will remain available indefinitely.
Unused credits do not expire unless we notify you otherwise in advance. Any proposed change to expiry arrangements remains subject to applicable law and the treatment of existing purchases. Credits are for use within the Service; they are not a bank deposit or a promise of investment return. Resale or transfer to third parties requires our written permission.
Referral rewards
When the program is active, an ordinary customer may share their personal referral link. A new account must confirm a valid referral code during Google signup; attribution is fixed at account creation. Existing accounts, self-referrals and recreated deleted identities do not qualify as referred buyers. A shared IP alone is not grounds for rejection.
The referrer earns 10% of the referred customer's first server-verified and legitimately fulfilled paid purchase's base credits, including the full checkout quantity. There is no referral cap. Existing buyer bonuses, including the DuitNow QR promotion, are excluded from the reward calculation. FPX and owner-verified QR payments qualify; test-provider payments, receipt uploads alone, coupons and manual adjustments do not.
When the separate repeat program is active, a previously attributed buyer's second and later server-verified, legitimately fulfilled paid purchases may earn the direct referrer 2% (0–20 qualifying buyers), 3.5% (21–49), or 5% (50 or more). Qualifying buyers are distinct referred buyers whose first 10% reward has ever been issued. The first purchase receives only 10%; rates never stack, and earlier repeat purchases are not paid retroactively. The repeat rate is determined when the reward is actually issued, not at checkout or verification; pending or held rewards have no guaranteed amount or rate. Pausing new repeat acceptance does not cancel accepted obligations; an issuance hold may temporarily defer payment.
Rewards are asAi service credits, not cash or transferable value, and expire 720 hours after actual issuance in a separate credit lot. Pending verification, restricted accounts or existing gateway safety controls may hold issuance for review without reversing a legitimate paid top-up.
Pausing the program stops new rewarded enrollments but preserves accepted obligations. Verified refunds or disputes may result in an audited reversal of only unspent, unreserved credits from the related reward lot. Spent, held, expired or ambiguous amounts require review; paid credit lots are not debited and first-purchase eligibility is not reset. Mandatory consumer rights remain unaffected.
7. Metering, Rates, and Billing Discrepancies
Usage is metered according to the applicable model and service pricing. Relevant factors may include Input tokens, Output tokens, and other chargeable units identified for the feature. Usage records and credit adjustments are used to calculate and reconcile the account balance.
Review the available pricing information before running a workload. Tokenisation, conversation context, Output length, and model behaviour can affect final consumption. A local estimate or request count alone may not equal the amount billed. Automated retries and repeated requests may create additional usage, so implement retry and spending controls appropriate to your application.
A timeout, interrupted stream, or unsuccessful client-side experience does not by itself establish whether an upstream request was processed or whether a debit should stand. Report disputed charges so that we can investigate the request state and billing records rather than assuming either that every failed request is chargeable or that every failure is free.
If you believe a balance, debit, or top-up is incorrect, contact us promptly with your account email, approximate time, and any non-secret request or transaction references. We will investigate and make appropriate corrections where an error is established. These Terms do not introduce a fixed dispute deadline that overrides statutory rights.
Coupons and promotional credits are subject to the conditions communicated with the offer, including any eligibility, redemption, or validity restrictions. Do not manipulate accounts or transactions to obtain benefits contrary to those conditions. We may correct benefits obtained through an established error or misuse, subject to applicable law.
8. Refunds and Payment Errors
Except where required by applicable law or expressly agreed by us, purchases are non-refundable once credits have been applied to the account or consumed. A change of mind or voluntary account closure does not, by itself, create an entitlement to a cash refund of an applied balance.
This policy does not remove remedies that cannot lawfully be excluded. Duplicate payments, payments received without corresponding credits, incorrect allocations, and other payment errors will be investigated and corrected as appropriate to the circumstances. Contact us before assuming that a missing balance requires a second purchase.
A correction may involve applying missing credits, reversing an incorrect debit, or another appropriate remedy. These Terms do not guarantee a particular remedy before the facts have been reviewed. Where a refund is due, reasonable payment verification may be required to prevent payment to an unauthorised recipient.
Nothing in this section prevents you from exercising a lawful right through your bank or a competent authority. Please provide accurate information in any payment dispute and retain the relevant payment records.
9. Acceptable Use
You must use the Service lawfully and in a manner that does not compromise its security, integrity, or availability. You must not:
- Resell access, API keys, or credits to third parties without our written permission.
- Circumvent rate limits, concurrency controls, verification requirements, balance checks, or access restrictions, including by creating accounts to evade an enforcement measure.
- Interfere with or overload the gateway or upstream infrastructure, exploit vulnerabilities, or attempt unauthorised access to systems, accounts, or data.
- Use stolen credentials, fraudulent payment evidence, or deceptive transaction practices.
- Submit content or use Outputs in a way that violates applicable law or another person's privacy, intellectual-property, or other legal rights.
- Reverse-engineer non-public components or attempt to extract confidential routing information, expose upstream relationships through unauthorised technical means, or bypass the branding and aliasing layer, except to the extent a restriction is prohibited by law.
- Impersonate the operator or misrepresent an independent application as officially endorsed by us.
These restrictions do not prohibit a good-faith complaint, a truthful review, lawful reporting to a regulator, or an activity that applicable law does not permit us to restrict. Ordinary use of documented interfaces is not permission to probe or extract non-public infrastructure details.
If you discover a suspected vulnerability, report it privately with enough non-secret detail to investigate. Do not access other users' information or continue exploiting an issue to demonstrate its impact.
10. Your Inputs and Use of Outputs
As between you and Fibonacci Ventures, you retain any rights you already hold in your Inputs. You authorise us to transmit and process those Inputs through the infrastructure reasonably necessary to fulfil your requests. This authorisation is for service delivery and is not a transfer of ownership of your content to us.
You are responsible for having the rights, permissions, and lawful basis necessary to submit an Input, including information concerning another person or organisation. Do not assume that a general-purpose API is suitable for every category of confidential or regulated information.
Subject to applicable law and third-party rights, we do not claim ownership of an Output merely because it passes through the gateway. We do not guarantee that an Output is eligible for intellectual-property protection, exclusively yours, unique, or free of another person's rights. Similar or identical content may be generated for other users.
Review the intended use before publishing, distributing, or commercialising an Output. These Terms do not grant rights owned by an upstream provider or another third party that we are not authorised to grant.
11. AI Limitations and Human Review
AI Outputs may be inaccurate, incomplete, outdated, biased, fabricated, or unsuitable for a particular purpose. An Output may contain incorrect citations, unsafe code, or confident statements that are not supported by evidence. Apparent fluency does not establish reliability.
You are responsible for reviewing and independently verifying Outputs before relying on them, making them available to others, or allowing them to trigger an external action. Apply appropriate testing and human oversight when integrating the Service into an automated workflow.
The Service is not a substitute for qualified medical, legal, financial, or other professional judgement. We do not guarantee fitness for safety-critical decisions or systems in which an incorrect or delayed response could cause serious harm. Assess your own use case and obtain appropriate professional advice where necessary.
To the extent permitted by law, we make no warranty regarding an Output's accuracy, legality, completeness, non-infringement, or suitability. Responsibility and remedies remain subject to the mandatory-rights provisions in Section 16.
12. Privacy and Request Content
Studio chat history and generated images are part of the persisted Studio workspace. Deleting a Studio conversation removes its stored messages and linked retained images through the conversation deletion control, subject to temporary technical copies and lawful retention requirements. Retained generated images are normally available for up to 15 days and are subject to a 100 MB per-account retained-image quota. Inline source images uploaded for editing are processed for the request and are not retained as separate source artifacts after processing.
Our Privacy Policy explains how Studio content, retained images, and deletion requests are handled.
Our gateway's request-processing policy is not to persist prompt or Output content beyond the processing needed to fulfil and return a request. We retain usage and billing metadata for account administration, reconciliation, support, and abuse prevention. Content you separately submit in a support message is handled as correspondence rather than an automatically expiring API payload.
Studio document uploads are accepted only for the document-processing feature. Uploaded bytes and extracted text remain in private temporary storage, are sent as bounded excerpts to the selected third-party AI provider when you press Send, and are deleted after 24 hours or earlier on document, thread, or account deletion, subject to technical copies and lawful retention requirements. Do not upload information you are not authorised to process.
Document scanning and parser controls are designed to reject unsupported, oversized, malformed, or detected-malware files, but they are not guaranteed against malware or prompt injection. Treat document content and model output as untrusted and apply human review. The Privacy Policy explains the processing, provider, and deletion limits.
These Terms do not create a customised confidentiality agreement, data-processing agreement, or geographic-processing commitment. Any such requirement must be separately confirmed in writing before use.
13. Rate Limits, Availability, and Service Changes
Accounts are subject to request-rate and concurrency controls, and the gateway is subject to shared capacity limits. Applicable limits may be communicated through the dashboard, documentation, or API responses. We may adjust controls to manage capacity, security, or service stability.
The Service is provided on an "as is" and "as available" basis to the extent permitted by law. Maintenance, network failures, upstream outages, capacity constraints, and third-party changes may delay or prevent requests. We do not guarantee uninterrupted operation or a response to every request.
Features, model aliases, supported parameters, and routing may change or be withdrawn. Where reasonably practicable, we will communicate material planned changes affecting ordinary use. Immediate changes may be necessary for security, legal compliance, or an upstream event outside our control.
Keep copies of information needed for your own work and design integrations to handle failures. No service credit, automatic refund, or uptime compensation is promised solely because of an interruption, except where required by law or separately agreed in writing.
Free model fair usage
Certain model aliases are made available at no charge ("Free Models"). Free Models are a limited benefit intended for evaluation, learning, and ordinary individual use, and are subject to the fair usage controls in this section.
From 31 October 2026, monthly tiers are based on verified, fulfilled purchased base credits in the current Malaysia calendar month (MYT, UTC+8): Lite below 1B; Pro at least 1B; Max at least 3B; Ultra at least 6B. Bonus credits, coupon or wallet grants, remaining balances and RM amounts do not count as purchased qualification. An audited administrative upgrade may establish a month-scoped qualification baseline; later qualifying purchases add to that baseline. Qualification resets on the first day of each month at 00:00 MYT, without changing wallet balances or their existing expiry.
The daily Free Model allowance is Lite: 555; Pro: 888; Max: 1,288; Ultra: 1,888 accepted requests per account across all Free Models and API keys. Every accepted Free Model request counts once, including requests that later fail or whose connection closes early; a request rejected before admission does not count. Existing usage is preserved when a tier changes: remaining allowance is the new daily limit minus requests already used, with a minimum of zero.
The shared total concurrency ceiling for paid and Free Model requests together is Lite 7, Pro 7, Max 14 and Ultra 21. Free Models have a sub-cap of 7 within that total, not an additional pool. Admission is first-come-first-served, not reserved capacity, a priority queue or a service-level guarantee. Provider, global and request-rate limits may be lower and still apply.
Eligibility is limited to accounts that hold credits available at the time of the request and not yet expired. Free Model requests do not debit, consume, reserve, or reduce your credits, and no charge, top-up, refund, or service credit arises from them. Temporary paid-request holds do not remove eligibility while positive, unexpired credits remain. Accounts without available credits are not eligible, and their Free Model requests are rejected.
The allowance resets at 00:00 Malaysia time (UTC+8) each day. Allowances do not accumulate, roll over, or transfer between accounts. Unused requests have no monetary value and cannot be exchanged for credits, refunded, or carried forward.
When an allowance is exhausted, further Free Model requests are rejected with a quota or rate-limit error until the next daily reset or a tier change provides remaining allowance. We may also apply separate request-rate and concurrency controls.
Usage that we reasonably consider automated beyond ordinary interactive use, scripted in a manner that defeats the allowance, resold, shared across unrelated parties, or otherwise inconsistent with ordinary individual use may be limited, suspended, or excluded from Free Models.
Free Models depend on third-party capacity and may be changed, limited, or withdrawn at any time. Where reasonably practicable we will give notice of material changes in accordance with Section 17. Free Models are provided on an "as is" and "as available" basis without any service level, and the remainder of this Section 13 applies to them.
14. Service Intellectual Property
Fibonacci Ventures and its licensors retain their respective rights in the Service's software, branding, interfaces, documentation, and other materials, excluding rights you retain in your Inputs and any rights in Outputs addressed in Section 10.
While you comply with these Terms, you may access the Service and use its documented interfaces for permitted purposes. This permission does not transfer ownership of the Service or authorise resale, copying of non-public software, or use of our branding in a way that suggests an unauthorised affiliation.
Feedback may be provided voluntarily. Do not include confidential third-party material in a suggestion unless you have authority to disclose it. We may consider suggestions without an obligation to implement them or provide compensation, unless separately agreed.
15. Suspension, Termination, and Closure
We may restrict a key, feature, transaction, or account where reasonably necessary to address a breach of these Terms, suspected fraud, unauthorised access, payment irregularities, abuse, a legal obligation, or a material risk to the Service or others.
Where appropriate, we may request clarification or corrective action. Notice may be delayed or omitted where giving it would increase a security risk, prejudice an investigation, or conflict with a legal requirement. You may contact us to ask for a review of a restriction and provide relevant information; reinstatement is not guaranteed.
We may terminate an account for a serious breach or an issue that remains unresolved. You may stop using the Service at any time and request account closure by contacting us. Merely stopping API requests does not necessarily close the account or delete its records.
Upon closure or termination, access may cease and associated keys may be revoked. Valid charges and unresolved payment issues remain subject to reconciliation. Voluntary closure does not automatically entitle you to a refund; Section 8 applies. Suspension alone does not state that all remaining credits are forfeited. Any decision concerning a remaining balance must take account of the circumstances and applicable law.
If we permanently discontinue the Service, we will communicate closure arrangements where reasonably practicable and address remaining balances consistently with applicable law. The ordinary non-refund wording is not intended to remove a remedy required because of permanent non-delivery.
Provisions that by their nature need to continue after closure, including accrued payment obligations, intellectual-property provisions, liability limitations, and dispute provisions, continue to the extent relevant. Data retention after closure is addressed in the Privacy Policy.
16. Disclaimers, Liability, and Mandatory Rights
To the maximum extent permitted by applicable law, Fibonacci Ventures excludes implied warranties and conditions concerning the Service, including merchantability, fitness for a particular purpose, and non-infringement, except for commitments expressly made in these Terms or separately agreed in writing.
To the maximum extent permitted by applicable law, Fibonacci Ventures is not liable for indirect, incidental, special, consequential, or punitive damages, or loss of profits, business, opportunities, or data arising from the use of or inability to use the Service, including reliance on AI Outputs.
These exclusions are subject to applicable law and do not exclude liability, statutory guarantees, or remedies that cannot lawfully be excluded or restricted. Nothing in these Terms excludes liability for fraud or any other matter where exclusion is prohibited. The Terms do not impose a fixed monetary cap on liability that remains legally recoverable.
You remain responsible for your own unlawful conduct and for reasonable precautions within your control, including protecting credentials and reviewing Outputs. This does not make you responsible for losses that the law requires us to bear.
17. Notices and Changes to These Terms
We may communicate service-related notices through your registered email, the dashboard, or official service channels, as appropriate to the notice. Keep your contact information current. Ordinary support correspondence does not amend these Terms unless an authorised written agreement expressly does so.
We may update these Terms to reflect changes to the Service, commercial arrangements, or legal requirements. Material changes will be announced through the dashboard or official channels, and the revised Terms will identify their effective date.
Continued use after revised Terms take effect constitutes acceptance to the extent permitted by law. Where additional notice, consent, or another procedure is legally required, that requirement applies. If you disagree with a revision, stop using the Service and contact us about account closure and any outstanding balance. Revisions do not retrospectively eliminate an accrued mandatory right.
18. Governing Law and Disputes
These Terms are governed by the laws of Malaysia. Subject to any mandatory right to bring a claim in another competent forum, disputes arising from these Terms or the Service are subject to the exclusive jurisdiction of the courts of Malaysia.
Before commencing proceedings, you are encouraged to contact us with a clear description of the issue, relevant non-secret records, and the resolution requested so that we can attempt to resolve it. This is not a compulsory arbitration clause and does not prevent urgent relief, a complaint to an authority, or action required to preserve a legal deadline.
19. General Provisions
These Terms, together with documents expressly incorporated into them and any applicable written agreement, describe the agreement concerning the Service. A general description, informal message, or marketing statement does not create an undisclosed uptime or performance guarantee. This provision does not exclude responsibility for representations where applicable law prevents that exclusion.
If a provision is held invalid or unenforceable, it should be limited or severed to the extent necessary, and the remaining provisions continue where legally possible. A delay in enforcing a provision is not a waiver of the right to enforce it later.
Neither party is relieved of a mandatory legal obligation merely because an event is outside its reasonable control. Operational consequences of third-party outages and similar events are addressed in the availability and liability provisions above.
No partnership, employment relationship, or agency is created merely by using the Service. You may not represent that you can bind Fibonacci Ventures or make commitments on its behalf.
20. Contact
Questions about these Terms, account closure, payment issues, or complaints should be sent to:
Fibonacci Ventures
D-15, Endah Promenade, Sri Petaling, 57100 Kuala Lumpur, Malaysia
Email: [email protected]
Include your account email and relevant non-secret references. Never send your password, complete API key, or banking authentication code.