Intelligence on demand · In the cloud

Add an intelligent interface to any application

Your software, in the chat your team already uses.

Your application already does the work. api0 lets people talk to it: import your API, and your team uses it from Teams, WhatsApp, Telegram or Claude, in plain language. Every action runs as the person asking.

No rewrite, no new frontend, nothing to host. Live in under five minutes.

Import your API See how auth works

What people do with it

One API, imported once. Each team uses it from the chat it already lives in.

Teams

Software vendors

Your customers use your product from Teams, as your own app.

Put your product in your customers' Microsoft Teams chat without building a chatbot. Each user signs in once and acts with their own permissions.

Field service

Technicians close jobs from WhatsApp.

No new app to roll out. A technician writes “job 4711 done” and the job is closed in your field-service system, recorded as done by them.

Three steps to your first agent call

Import your API → send your team one link → every call governed, attributed and metered.

STEP 1

Import your endpoints

Paste an OpenAPI spec, or describe endpoints in plain English. api0 turns each one into an MCP tool, and a built-in test calls it before it counts as configured.

POST /api/invoices
  creates an invoice
  required:
    customer_id, amount

STEP 2

Send your team one link

Your tenant gets its own Get started page. Each person signs in once, then adds it to Claude or Teams, or links their WhatsApp or Telegram to your own bot.

app.api0.ai/link/acme

  ✓ Claude connector
  ✓ Acme in Teams chat
  ✓ WhatsApp
  ✓ @acme_bot on Telegram

STEP 3

Govern execution

Every call passes the gateway: it checks who is calling, attaches the credential your application expects, deducts credits, and logs the call.

tools/call create_invoice
  ✓ caller: jane@acme.com
  ✓ credential attached
  ✓ credits checked
  → POST /api/invoices

Follow the five-minute quickstart

What your application receives

You choose how api0 authenticates to your application. The credential lives in api0 and is attached on every call, along with who the call is for.

Google identity token

Proves the call came from api0. Verify it like any service-account OIDC token.

Fixed bearer token or headers

A static token or custom API-key header, stored in api0. Claude never sees it.

OAuth client credentials

api0 fetches and refreshes a token from your identity provider.

Per-user secret

Each person stores their own key, and their calls carry it.

Per-user OAuth account

Each person connects their own account once, and acts as themselves.

Who is calling

OAuth 2.1 with PKCE for Claude connectors
API keys for the SDK, CLI and CI jobs
Your own identity provider: Entra ID or any OIDC

The connection test in the dashboard runs the same logic as a real call, so a passing test means a working setup.

Why api0

Where your team already is

Microsoft Teams chat, your own WhatsApp and Telegram bots, Claude on web, desktop and mobile, and any MCP-compatible client. No SDK to embed, no model to host.

One place for identity

Who is calling, what they may do and which credential your application gets are decided at one gateway, whichever client they came from.

Built in Rust

The gateway and every api0 service are written in Rust, for predictable latency and a small attack surface.

A plan per tenant

Seats and credits included, extra members per seat, overage on the next invoice. No enterprise sales call to get started.

How api0 compares

Where api0 stands out.

Feature	Microsoft Copilot Studio	Cloudflare MCP Server Portals	agentgateway	Composio
Your REST API as MCP tools	In preview	Your MCP servers only	YAML config	Code or your own server
Chat in Teams, signed in				Agent actions only
Chat in WhatsApp	Closed since Oct 2026			Agent actions only
Chat in your own Telegram bot	Via Azure, with code			Agent actions only
One onboarding link per tenant	Per channel	Portal URL		One per app
Five credential modes, per-user OAuth included	Three modes	Up to each server	Policies to write	Catalogue apps only
Nothing to host			Self-hosted

Public docs, November 2026.

From tool call to real API call

tools/call: search {"dept": "eng"}

→

GET /users/search?dept=eng

tools/call: create_invoice {"customer_id": "acme"}

→

POST /api/invoices {"customer_id": "acme"}

tools/call: update {"id": "1", "em": "x@y.z"}

→

PUT /users/1/update {"em": "x@y.z"}

The gateway injects parameters into URLs and bodies with the right HTTP verb, then returns the result to the model.

See the whole architecture on one page

Make your application intelligent this week

Get started