AI app builder
Create and refine web app experiences from natural-language instructions, with a live preview to help you review each iteration.
For prototypes, internal tools, and product ideas.
Services
The building blocks for your app.
Build the experience, then connect the capabilities behind it. Negatify brings app generation and supported project services together in one workflow.
Project database
Connect your app to project-scoped data operations for creating, reading, updating, and deleting records through the database API.
Structured data for app features and workflows.
File storage
Upload and retrieve project files through a consistent API, including images and other assets your application needs.
Assets and files organised by project path.
AI chat API
Add conversational AI to your app using the chat endpoint, with JSON responses or streaming output where supported.
Useful for assistants, Q&A, and guided experiences.
Email service
Send application emails such as welcome messages and verification emails through the project email service.
Keep communication connected to your app workflow.
Project isolation
Use project identifiers and credentials to scope service access to the intended project. Protect passwords and server credentials as secrets.
Follow the security guidance in the developer docs.
Build with the APIs
Read the endpoint reference, authentication requirements, request examples, and common error responses before integrating a service into your app.
Service guide
What each Negatify service does
Services are building blocks for different parts of an application. They share project-scoped credentials and, where metered, draw from the same credit wallet. See the Pricing page for rates and the Docs page for exact endpoints, headers, and request examples.
AI app builder
Use natural-language instructions to create and refine an application's screens, components, and interactions. Builder spend varies with the selected model, usage tier, context size, generated output, and agent steps. Check per-run usage details rather than relying on a fixed per-app estimate.
Project database
Persist application records such as profiles, settings, catalogue items, and workflow state. The API supports reading collections and documents and creating, replacing, patching, or deleting records. Requests are scoped to the project; choose clear paths and validate input in your application.
File storage
Store files used by your app, including images and generated assets. Upload, list, download, replace, and delete operations are available through the documented API. Costs depend on stored data volume and downloaded bytes; keep access controls and file validation in mind.
AI chat
Add conversational experiences such as document Q&A, support assistants, or guided workflows. Send messages to the chat endpoint and use standard JSON or streaming responses where supported. Input and output tokens are charged separately, so long context and long responses affect usage differently.
Send transactional messages such as welcome notes, alerts, or verification emails from the project email API. Each recipient counts as a message. Current configured pricing is 1 credit per 25 email messages, with per-project rate limits and successful-send accounting.
Project isolation and credentials
Use the project identifier together with the project key and password headers to scope API requests. Keep passwords and other secrets in trusted server-side environments; do not expose them in public frontend bundles, repositories, or client logs.
Recommended implementation sequence
- Read the quick start and create project credentials.
- Integrate one service at a time and test success and error responses.
- Store secrets securely and validate user input on your server.
- Check usage metadata and the dashboard during development.
- Review the service rate card before launching high-volume workflows.