One UI for your skills and your integrations

Your agents, every app you use, one gateway.

Agezero Connect is the dashboard for AI-powered integrations. Connect Gmail, Slack, HubSpot, Stripe and 20+ more apps in seconds, then drive them from Claude Code, Codex, or any HTTP client — with managed auth and per-tenant API keys.

curl -X POST https://connect.agezero.io/{service}/api/{endpoint}

{
  "providerConfigKey": "slack",
  "connectionId":      "demo-user",
  "method":            "POST",
  "endpoint":          "/chat.postMessage",
  "data":              { "channel": "C0123", "text": "Hello from Agezero" }
}

Features

Everything you need to run an integration tier.

🗂️

24 apps, one inbox

Gmail, Slack, Notion, HubSpot, Stripe, GitHub, OpenAI, Anthropic — connected once, called anywhere.

🔌

Managed auth, zero plumbing

OAuth, API keys, token refresh and storage are all handled by Nango. You ship features, not credential code.

🧠

Drives any agent

Same endpoint pattern as the Maton gateway — works with Claude Code, Codex, OpenCode, or your own scripts.

🪪

Per-tenant API keys

Each user gets their own bearer token. Mint, copy, reset, done. The plaintext is shown exactly once.

📋

Connections table

See every tenant's connection at a glance — app, account, method, status, created. Filter, paginate, audit.

🔒

Auth-gated by default

NextAuth credentials with bcrypt. JWT sessions. Every API route checks the session before doing anything.

How it works

From sign-in to first call in under a minute.

1
Sign in
Use the seed account from your env, or wire a real provider (Google, GitHub) in lib/auth.ts.
2
Connect an app
Hit + Connect on any provider. Nango opens its managed OAuth/API-key flow in a popup.
3
Call via the gateway
POST to /api/nango/proxy from your own code, or use the in-app Playground to test endpoints live.
4
Drive any agent
Pass your API key to the Maton agent toolkit or any MCP-compatible client. Same gateway, same shape.

FAQ

Common questions

Is this the same as Maton?+

Same UX patterns (sidebar + integrations grid + connections table + tasks) and same gateway shape, but you own the deployment. The backend is Nango instead of Maton's managed layer.

Can I deploy on Vercel?+

Yes — that's the default. Push to GitHub, import on Vercel, set NEXTAUTH_SECRET + seed user env vars, deploy. The full README walks through it.

Why is the file store not persistent on Vercel?+

Serverless functions have a read-only filesystem. The auth flow falls back to an env-only seed user so the demo keeps working. For production persistence, swap lib/users.ts and lib/tasks-store.ts for Vercel KV or Postgres — the public function signatures stay the same.

How do I add a new provider?+

Edit lib/catalog.ts and add an entry with a Nango provider slug, then register the integration in your Nango dashboard. The UI updates automatically.

Ready to ship?

Sign in with the demo account and try the playground. Or fork the repo, plug in your Nango keys, and deploy to your own Vercel.

Create free account →Sign in GitHub ↗