Create and manage applications.
Give BuildNinja or another integration its own application. See its status, credentials, usage allowance, and activity in one place.
Create application credentials for BuildNinja, choose Economy, Balanced, or Best, set how many credits the application can use, and inspect usage from one portal.
Economy, Balanced, and Best change the analysis depth and credit use for the same supported AI features. A separate application allowance controls how much BuildNinja can consume from the shared account pool. Use the sample to see both controls work together.
Open your dashboardOne application. Three quality settings. Two levels of credit control.
More context for everyday build investigations and reviews.
Two controls, two jobs. The app limit contains one integration. The account pool pays for every application. Resetting an app allowance never returns credits to the account pool.
Illustrative request values only. Actual credit use varies with the selected quality setting, input context, and response size.
Give BuildNinja or another integration its own application. See its status, credentials, usage allowance, and activity in one place.
Create an App ID/API key and App Secret for each application. Store the secret securely and regenerate it when the connection must change.
Choose the analysis quality, set a maximum of at least 10,000 credits, and reset the application allowance manually, daily, weekly, or monthly.
Review requests, sessions, credit trends, and request-level activity. Filter usage by application, period, model tier, task type, or credit amount.
Three steps to get your AI access ready.
Use your GrapeHub account to open the developer portal. Activate kenzoAI access and make sure credits are available. Eligible accounts can claim free credits, with prepaid top-ups available when needed.
Open the developer portalOpen Applications and choose Create application. Name the integration, set its credit limit, and choose the available model tier and reset frequency. Save the App ID and the App Secret shown after creation.
Read the application guideIn BuildNinja, an administrator adds the credentials under Settings → AI Configurations. For your own integration, start with the kenzoAI documentation. Return to the portal to monitor usage.
Follow the BuildNinja setup guideBuildNinja comes with AI. The developer portal is where you create the application credentials and manage its usage. BuildNinja is where your team analyzes logs, explains configurations, and reviews AI build reports.
Explore kenzoAIAn administrator saves these credentials in Settings → AI Configurations. An AI Runner step has its own documented credential and execution settings.
Read the configuration guideAI requests consume credits from the account pool and count toward the application’s usage limit. Resetting an application’s consumption allowance does not refund credits or refill the account pool.
Building your own integration? Start with applications, credentials, and the platform model.
It is the place to create kenzoAI applications, manage their credentials and credit limits, and inspect usage. BuildNinja uses those application credentials to connect its AI features to kenzoAI.
Sign in to the developer portal and create an application. kenzoAI provides an App ID, also called an API key, plus an App Secret. Save both securely and use them to connect your integration.
Yes. The portal calls the application identifier App ID or API key. BuildNinja’s AI Configurations screen labels the corresponding field App Key. The App Secret goes in the App Secret field.
The App Secret is shown once after creation. Store it securely. If you need a new secret, regenerate it in the application details; the previous secret becomes invalid, so update the connected integration.
No. A reset renews the application’s consumption allowance for its reset cycle. It does not restore credits already consumed from the account pool.
They are quality settings for the same supported AI features. Economy gives concise help with the lowest credit use, Balanced is the recommended default for everyday investigations, and Best applies the deepest analysis to complex failures and code-change risk. Actual usage also depends on the context and response size.
AI requests from that application pause until you increase its Max Credits or reset its consumed allowance. Other applications can continue if their own allowance and the shared account balance are still available. The minimum configurable application limit is 10,000 credits.
The kenzoAI portal is a hosted service accessed in a browser. BuildNinja runs on your infrastructure and needs network access to kenzoAI for its AI requests.
Open the kenzoAI portal to create credentials and manage your AI usage.