AI assistants and companion apps

What is the AI assistants and companion apps example app?

A user talks to an assistant built for one job: tutoring, planning, reflection, or coaching. Replies stream in as they are written. The conversation is saved so the user can return to it. Free users get a small daily allowance, and paying users get more.

This category is a design target. It is not a claim that Edict already supports a complete assistant app.

What backend does the AI assistants and companion apps example need?

• Authentication.
• Conversation history.
• An AI gateway.
• Usage quotas.
• Subscription entitlements.
• Streaming and background operations.

How do the planned modules compose in the AI assistants and companion apps example?

Authentication is designed to identify the person, and the database to store conversations as records they own. The AI gateway is designed to keep the provider credentials on the backend and stream the reply to the client. Subscriptions would provide the entitlement, and the quota rule would decide how many messages each plan can send.

Authentication, Subscriptions, and the AI gateway together are the core pattern of subscription-gated AI. Each request is designed to be checked in the same order: identity, plan, quota, then the provider call.

Some work does not suit a live connection, such as summarizing a long conversation overnight. Background jobs are planned to run that work and store the result.

What would an illustrative rule look like in the AI assistants and companion apps example?

The configuration above sets a different daily allowance for each plan and turns on streaming. The numbers are placeholders chosen for the example, and the syntax is not final.

What is example and what is planned in the AI assistants and companion apps example?

Every module named here is planned and in development. Your app owns the prompts, the personality of the assistant, the safety approach for sensitive topics, and the choice of provider. The initial model favors customers bringing their own provider credentials, and supported providers are not committed yet.

See the AI gateway and Subscriptions module pages for the planned design. Join the beta waitlist to follow progress.