Use cases

Wherever your users talk to AI, your API is there.

One published project serves AI apps, coding agents and your own site, all with your login and your roles.

B2B SaaS

Your customers run your product from Claude and ChatGPT

A project-management, CRM or billing product publishes its API once. Customers add one URL to their AI app, sign in with their existing account, and ask for things in plain language: "create a task for Priya due Friday", "which invoices are overdue?".

Sign-in with your login, so no new accounts
Each customer sees only what their role allows
Deletes and other marked operations ask before they run

Developer platforms

A CLI and skill your users' coding agents pick up

Developers working in Claude Code, Codex or Cursor install your branded CLI or Claude plugin. The generated skill tells their agent when and how to call your API, and ask_docs answers questions from your reference with citations.

One install command for macOS, Linux and Windows
Plugin adds the endpoint and the skill in one step
Answers cited to your docs, not guessed

Your own app

An assistant inside your product, without building one

Drop the widget script on your site. Signed-in users chat with an agent that calls your API as them. If your site already has the user's token, the widget exchanges it for ours with no popup.

One script tag, limited to the origins you list
Your branding: name, logo, colours, theme
Your own model key, or ours paid with points

Internal tools

Give your team AI access to internal APIs, safely

Connect an internal API behind your company SSO (Google, Microsoft Entra ID, Okta, Auth0, Keycloak or any OIDC issuer). Staff use it from the AI apps they already have, with roles from your identity provider's claims.

SSO via OIDC
Role claims map to the operations each team may call
Sessions visible and revocable

Put your API where your users already work.

Access is invite-only while we onboard publishers. Bring a spec URL and your login page.

Request access Read the docs