AI inside your apps

Ask for an AI feature in your own words, for example “add an assistant that answers questions about our menu” or “summarize each review”. Craftkite builds it on Craftkite AI: you don’t need an account or API key with an AI provider, and the app’s AI calls are paid with your credits.

How it works

• Craftkite gives each app its own private key and a small helper in the app’s server code. The browser never sees the key.
• Each answer costs at least the price in the credit table; longer answers cost their measured share more. AI images (on plans with AI images) have a set price. See the credit table.
• Mobile apps use AI through their backend, so add a database or sign-in to a mobile app first.

Control spending

Open the Publish tab and find AI in your app (on the phone: AI in your app on the project page).

• Craftkite AI switches the app’s AI on or off. When it is off, the app shows a friendly “not available” message instead of an answer.
• Monthly limit (credits) caps what the app may spend in a month. Leave it empty for the default. You get a notification when the app reaches the alert level and when it reaches the limit; then its AI pauses until next month or until you raise the limit.
• This month shows the credits used, answers and images.
• Replace the app’s AI key makes the old key stop working at once. The preview and the live app get the new key when they restart or are published again.

Fair use

Requests that break the acceptable use policy are refused before any AI model sees them. If an app keeps sending such requests, its AI is paused and our team reviews it; make the app filter those requests, then switch it back on.

Using your own AI provider key

Prefer your own provider account? Add an AI integration in the Publish tab (see Secrets and integrations) and ask Craftkite to use it. Calls then go to your provider and are billed by them, not in credits.