AI API credits, explained.

01 / At a glance

At a glance

Available today

Waitlist applications and review. No API key or daily credit is issued by this website yet.

Who it is for

Developers, lawyers, finance professionals, artists, screenwriters, and other creators in Southeast Asia. Detailed eligibility is still to be published.

Planned daily limit

Up to US$10 in API usage after approval, service launch, and activation. Usage depends on the models and rates published at launch.

Unused credits and cash

Unused daily credits do not roll over. Credits cannot be withdrawn as cash.

Application information

Email, field, project idea, and selected language are sent to the review team through Feishu.

API data agreement

Applying is not consent to API data reuse. Activation will require a separate, active agreement.

02 / The program

Different crafts. Room to experiment.

Start with a small, useful project. These are possible experiments, not demonstrations of currently available models or tools.

Other fields are welcome to apply. Describe your idea so the review team can understand it. Admission is not guaranteed.

03 / How credits work

A daily allowance, with clear limits.

The planned benefit is up to US$10 in API usage each day for approved, activated participants once access is available. A 30-day illustration reaches US$300 only when the full allowance is used every day.

• The credits are intended to refresh daily; the exact schedule and any claim requirement are not yet published.
• Unused daily credits do not carry over to the next day.
• Credits cannot be withdrawn as cash and are not a cash grant.
• The local-currency calculator shows an indicative exchange-rate conversion, not a balance in that currency.

A simple usage example

Using the full allowance on 10 days could cover up to US$100 in API usage. Skipping a day would not add its unused allowance to a later day. This is an illustration of the planned rules, not usage already available.

04 / Joining the waitlist

One email. One small idea.

1. Send a request

   Enter your email, choose your field, and describe what you would like to make. Your selected website language accompanies the application.

2. Wait for review

   Your application is sent to the review team through Feishu. If you are invited, the team plans to contact you by email. An approval timetable has not been published.

3. Activate when access is available

   The planned next step is registration with your application email and a separate data-use agreement. A waitlist request does not activate credits or create an API key.

05 / Plan your first experiment

Make your first experiment easy to assess.

You can prepare a useful application before API access is available. A focused description is easier to review than a promise to build everything.

1. Describe one task

   Name the intended user, the language, and one outcome: for example, answer common questions from a public community resource.

2. Choose material you can use

   Start with original, licensed, public, or synthetic examples. Leave personal data, credentials, and confidential client records out.

3. Define a small success check

   Write several expected answers or quality criteria. Note where a person should review an answer and what a failed answer would look like.

4. Budget after rates are published

   Estimate calls and input/output size using the actual supported models and prices when they become available. A dollar allowance alone does not determine a token or request count.

06 / Your data

Applying and activating are separate.

Your application today

Your email, field, project idea, and selected language are sent to Feishu for admission review and related updates. Successfully delivered applications are kept as messages in the review group; there is no separate application database or applicant dashboard.

Applying does not authorize training on or sale of your application details, subscribe you to VibeMorrow Club, or provide consent to reuse future API inputs and outputs.

The future API agreement

Before activation, you will need to separately read and actively agree to the API data-use terms. The current proposal covers de-identified API inputs and outputs for service improvement, model training, and external sharing, commercial licensing, or sale.

Use only material you are allowed to contribute. Keep confidential client records, credentials, and personal financial information out. De-identification does not guarantee anonymity.

The operating legal entity, retention periods, recipients, and withdrawal process remain to be published before API activation. This guide describes the current plan; it is not the final API data-use agreement.

07 / Questions & answers

Questions & answers