API first. All of Qik, open to your code and your AI.

We build every feature into the API before it reaches the dashboard, so nothing is held back: 100% of the platform is there to call. Connect ChatGPT, Claude, Codex or Cursor in a couple of minutes and they work with your real records, under your own permissions.

No credit card. Qikbot is included.

Why it's different

A backend you would have spent the first six months building.

AI can write your screens in an afternoon. The slow, risky part is everything underneath: accounts, permissions, payments, audit history and hosting. That part already exists here, and your AI tools can drive it directly.

Most toolsQik

The API

A subset of what the product itself can do.

100% coverage. We build the API first and the dashboard on top of it, so if you can click it, you can call it.

Working with AI

Paste the documentation into a chat and copy code back out.

Connect Claude, ChatGPT or Cursor to your organisation's own MCP server. It signs in as you, works under your permissions, and builds on real records.

Your own data model

Custom objects that work in some places and not others.

Define a type and it has the same endpoints, permissions, lists and history as the built-in ones from the first request.

Server-side code

Stand up your own server for anything the platform can't do.

Your JavaScript runs on Qik: on a schedule, when a record changes, or as its own endpoint. Secrets stay on the server and each job gets only the access you grant it.

Bring your own AI

Connect your AI in two minutes.

Every organisation gets its own hosted MCP server. Paste one address into your AI tool, sign in as yourself, and it can read, build and change things across the whole platform, with exactly the permissions you have.

https://api.qik.dev/mcp/official

Claude

Add Qik as a connector in Claude or claude.ai, or run one command in Claude Code.

ChatGPT

Add Qik as a connector and ask for what you need in plain language.

Codex, Cursor and other editors

Add the address to your editor's MCP settings and build against real records while you code.

The whole platform as tools

Hundreds of tools covering people, forms, payments, workflows, websites, email and more. If the API can do it, your AI can too.

Signed in as you

Sign in through your browser, with no keys to copy. The assistant sees and does only what your login allows, and every change is in the history.

Built to get it right

Guides, checks and previews inside the tools steer the AI to the right way of building, so forms, workflows and pages work the first time.

How it works

01

Get a token

Create an API token that carries exactly the access it needs.

02

Call anything

Every record type, including the ones you define, uses the same endpoints.

03

Or connect an AI

Point Claude, ChatGPT or Cursor at your organisation's server address and sign in as yourself.

With or without a developer

Write only the part that's yours.

Your data is already sitting somewhere with two-factor sign-in, field-level permissions, audit history and hosting around it. That is the part you would otherwise build for the fourth time. If you don't write code, ask for what you need and it gets built: the integration connected, the permissions set, deployed while you're still in the conversation. If you do write code, the same complete API is waiting, which is why anything you can do in Qik, Qikbot can do too.

  • API-first - everything you can click, you can call, and so can Qikbot.
  • Any AI, any client - the whole platform is exposed as tools for ChatGPT, Claude, Grok and any other MCP client, as well as Qikbot, the assistant built in.
  • The idea is the qualification - describe an integration in plain language and Qik reads the other system's API, writes to it, configures the permissions and deploys it.
  • Your own code, run for you - drop in JavaScript for custom logic, integrations and webhooks. Run it on a schedule, when a record changes, or as your own endpoint. No hosting or assembling different products required.
Read the docs →

The basics, covered

A complete platform underneath

Sign-in, permissions, hosting and audit history are already there, so your code only has to do the part that's yours.

One API for everything

The dashboard is built on the same API you call, so nothing is held back.

Hundreds of AI tools

A hosted MCP server exposes the whole platform to any compatible AI client, under your own permissions.

Sign in with Qik

Use Qik as the sign-in provider for your own apps.

Your code, hosted

JavaScript runs in a sandbox on a schedule, when a record changes, or as an endpoint of its own.

Scoped tokens

Tokens carry their own permissions and can be rotated.

Integrations with their secrets kept safe

Connect other systems from the server, so keys never reach the browser.

Live updates

Screens can stay current as records change, without polling.

Your own record types

Define a type and it gets the same API, permissions and history as the built-in ones.

Documented

A full reference for every endpoint at docs.qik.dev.

Start today

The hard parts are already done.

Start a free trial and tell Qikbot what you need, or talk to the people who build it. Either way you begin with something that works.

No credit card. Your data stays yours, and you can export it any time.