Xano’s API builder: your coding agent writes REST APIs in TypeScript with the Xano SDK. Run them on the Xano Engine on your machine, then deploy them to Xano, documented, tested and observable under your team’s rules.
An API builder is a tool for creating the endpoints your apps, services and agents call, without hand-assembling servers, routing and documentation. On Xano, the API builder is part of one backend platform: your coding agent writes each endpoint in TypeScript, and Xano runs, documents, tests and observes it alongside your database.
Your coding agent writes the endpoint in TypeScript with the Xano SDK, you run it on the Xano Engine on your machine, then deploy it to Xano.
In Claude Code, Codex or Cursor, ask for what you need in plain words, for example: “Add a POST /posts endpoint to the blog API that saves a post with a required title and returns the new row.” The agent writes it with the Xano SDK, grounded in the SDK’s llms.txt and the AGENTS.md that init put in your project.
// xano/index.ts
export const post = table({
name: "post",
schema: {
title: f.text({ required: true }),
published: f.bool({ default: false }),
author: f.tableRef(user), // type-checked
},
});
const createPost = query({
verb: "POST", apiGroup: blog, name: "posts",
input: { title: input.text({ required: true }) },
stack: [s.db.add({ table: post, row: { title: inp("title") }, as: "row" })],
response: ref("row"),
});Adapted from the Xano SDK README.
npm run xano:deploy typechecks the code and runs it on the Xano Engine: a single binary with Postgres built in, with no account and no network. Call the endpoint, run the tests with npx xanosdk test run-all, and open the builder link the deploy prints to see what your code compiled to.
npm run xano:deploy When it is ready to share, one command deploys the same code to a disposable ephemeral on Xano’s cloud and runs its tests. Only a release that came up and answered can be promoted, so what you tested locally is what serves production traffic.
$npx xanosdk deploy --ephemeral --test Your agent writes each endpoint; Xano documents, gates and observes it, and your whole team sees what got built in one place.
Your coding agent writes API groups and queries in TypeScript with the Xano SDK, against your workspace rules, with your docs and skills as standing context. You run them on the Xano Engine on your machine, and the Xano editor shows the whole team what got built, endpoint by endpoint.
The Xano SDKAutogenerated OpenAPI (Swagger) documentation for everything, always current, because it's generated from the live system.
Unit and workflow tests attach to endpoints; the release gate checks them before anything promotes to production.
Request history on every endpoint, error logs with stack snapshots, audit trails for who or what changed anything.
ObservabilitySecurity controls are set once and reused everywhere, so every endpoint your agent writes is protected the same way as the rest of the workspace.
API keys, OAuth and JWT, roles and scopes. Your team sets the approved auth patterns once as workspace rules, and every endpoint the agent writes follows them.
The Free plan is rate limited (10 requests per 20 seconds); Essential plans and above have no platform-enforced API rate limit. Paid plans add API response caching, and Pro and Custom add Redis data caching for faster responses and rate limiting of your own.
Middleware and JavaScript lambdas reach any service with an API (payment providers, messaging, internal systems) from inside governed logic, with the same review gates and audit trail as everything else. Tests attach to queries, functions and middleware alike.
Every endpoint ships with autogenerated OpenAPI (Swagger) documentation. It is generated from the running system, so what is documented always matches what runs, including the endpoint your agent added an hour ago. Your services, your partners and other AI agents read the same spec, and nobody keeps a separate document in sync by hand.
How your stack consumes Xano APIsYour coding agent writes it. You describe the endpoint, the agent writes it in TypeScript with the Xano SDK, and you run it locally before deploying. Anyone on the team can read what was built in the Xano editor without reading the code.
Yes. Every endpoint ships with autogenerated OpenAPI (Swagger) documentation, generated from the live system, so it is always current. Your services, partners and AI agents can consume the same spec without anyone maintaining it by hand.
Yes, on paid plans. Custom domains replace the Xano base URL with your own domain on the Essential, Pro and Custom plans. The Free plan uses the Xano base URL. See the full plan comparison for what each plan includes.
Only on the Free plan. Rate limiting applies to Free plan workspaces; Essential plans and above are not subject to platform-enforced API rate limits. Each plan’s limits on records, storage, workspaces and seats are listed in the full plan comparison.
Claude Code, Codex and Cursor, plus Copilot, Gemini CLI and OpenCode. Install the agent skill once with npx @xano/sdk agent-skill install and every coding agent on your machine knows how to write valid Xano code with the SDK. See how coding agents build on Xano.
One platform to build, run and govern AI-built software.