Skip to content

Choose your path ​

Every path leads to the same platform. What changes is how you connect.

Create apps without code ​

The dashboard covers day-to-day operations without writing a line: model the data with the Entity Manager and build the application with the Application DSL. It is the shortest path when what you need already has a dashboard UI.

→ Dashboard

Use our MCP ​

An AI agent operates the platform on your behalf. The MCP server ships two transports: a local stdio process for your own machine, and a hosted Streamable HTTP endpoint with OAuth for everything else.

→ MCP server

Use our SDK ​

The recommended path when you write code. Pick server (sk_) if the integration runs in your backend — it wraps the whole API, paginates, and maps errors to typed exceptions — or browser (pk_) if the user's own browser has to read their data. The browser SDK includes the embeddable launcher: a mounted component, so your users never leave your app.

→ SDK · TypeScript SDK

Use our API ​

Direct REST, for when your stack has no official SDK or you need an endpoint the SDK does not wrap yet. Every SDK is a thin layer over these endpoints, so anything an SDK does is reachable from here; the first-request example lives in the API guide.

→ API

The rule that decides almost everything ​

A secret key never leaves a server. If the code runs in a browser, a mobile app, or anything a user can inspect, it uses pk_ — and a publishable key is deliberately narrow: reads on users, companies and settings; invoices, entitlements and their check; billing checkout and portal; and notifications, which also require a user JWT. Everything else answers 403.

See API Keys for the full matrix.

What every surface shares ​

  • The same contract version. The version lives in the URL (/v1/…), so what you read here is what the SDK calls. The contract your client consumes is chosen with the version option; if you omit it, the client uses the latest published version, as Environments explains.
  • The same permissions. Every credential carries its own role and operation list, and no surface lets you do more than that credential allows: the publishable key is deliberately narrower than the secret one. See API Keys.
  • The same tenant boundary. The active company comes from the credential; X-Company-Id only picks among companies already linked and never widens access, so a company never sees another's data. See Multi-tenancy.