An API frameworkfor Node wherethe docscan't lie.

印 one contract

Write it once. Everything else follows.

Params, query, body, responses and a few examples, next to the handler. inkan reads them and does the rest, so the docs, the types and the tests are never three things that drift apart.

app.get("/teas/:id", {
  params: t.object({ id: t.int() }),
  response: { 200: Tea, 404: t.problem() },
  examples: [
    { name: "found", params: { id: 1 } },
    { name: "missing", params: { id: 99 }, status: 404 },
  ],
}, ({ params }) => findTea(params.id));

印 live

Talk to a real inkan app.

This site runs on inkan, through @inkanjs/next. Send it something, or break it on purpose. Its own docs are at /api/docs.

印 under the hood

Fast, and still honest.

印 how fast

All of that, level with Fastify or a little ahead.

Requests per second, with plain node:http as 100. Every server runs at once and the measurements take turns, so a slow moment of the machine hits everyone alike.

and every one of those inkan requests was validated, typed and trimmed to its contract. how it is measured →

印 integrations

inkan where you already are.

One package each, all in inkanjs/integrations. Nuxt, SvelteKit, Astro and Remix need none: app.fetch is enough.

import inkan from "@inkanjs/vite";

export default {
  plugins: [inkan({ entry: "src/server/app.ts" })],
};
// npm run dev → the frontend, /api, /api/docs, one port