API Gateway Skill: Connect to 100+ APIs With Managed OAuth in One Step

36,000+ downloads and 182 stars — api-gateway by @byungkyu is one of the most-installed integration skills on ClawHub. It solves what's arguably the most tedious part of building AI agent workflows with external services: OAuth setup.

Instead of registering a developer app, managing client IDs and secrets, implementing token refresh logic, and storing credentials for every API you want to use — you connect once through Maton, and the skill handles the rest. One key, 100+ services.

The OAuth Problem

Every major SaaS API requires OAuth when you want to act on behalf of a user. The setup is nearly identical everywhere: register an app, get a client ID and secret, implement the authorization flow, store tokens, handle refresh. It's 1-2 hours of yak-shaving per API, and you do it over again for every new service.

For AI agent workflows, this overhead is compounded. You're often connecting to 5-10 services in a single automation (pull data from Notion, create a ticket in Linear, send to Slack, update a spreadsheet). Each one is a separate OAuth dance.

api-gateway replaces all of this with a single passthrough proxy. Maton manages the OAuth connections to each service; the skill exposes those connections as a simple authenticated HTTP layer your agent can call directly.

How It Works

The architecture is a passthrough proxy:

Your AI Agent
     ↓
api-gateway skill (MATON_API_KEY)
     ↓
Maton.ai proxy
     ↓
Target API (Google, Notion, GitHub, etc.)

Key security property: Your MATON_API_KEY authenticates with Maton only — it grants zero access to any third-party service on its own. Each service requires explicit OAuth authorization through Maton's connect flow. This means losing or rotating your Maton key doesn't expose your Google or Slack access.

Supported Services

The skill covers 100+ APIs across major categories:

Productivity & Communication

• Google Workspace (Gmail, Drive, Calendar, Sheets, Docs, Meet)
• Microsoft 365 (Outlook, OneDrive, Teams, Excel)
• Slack, Notion, Airtable, Asana

Development & DevOps

• GitHub, GitLab, Jira, Linear
• PagerDuty, Datadog

CRM & Sales

• HubSpot, Salesforce, Pipedrive
• Apollo, ActiveCampaign

And more: Stripe, Shopify, Twilio, SendGrid, Zoom, and dozens of others.

Getting Started

Step 1: Get a Maton API Key

Sign up at Maton.ai and create an API key. Add it to your environment:

export MATON_API_KEY="your-maton-key"

Step 2: Install the Skill

clawhub install api-gateway

Step 3: Connect Your Services

Through Maton's dashboard, authorize each service you want to use via OAuth. This is the one-time setup per service — you go through the standard OAuth flow in your browser, and Maton stores the tokens.

Step 4: Call APIs

Once connected, your agent can make API calls through the gateway. The skill acts as a proxy, forwarding requests to the target service with your OAuth token automatically attached.

Example Workflows

Cross-Platform Data Sync

Pull a list of tasks from Notion and create corresponding issues in Linear:

Agent: Get all Notion pages tagged "Q2 milestone" → create Linear issues for each

Without the gateway, this would require separate OAuth setups for both Notion and Linear. With it, both calls go through a single authenticated proxy.

Email + CRM Automation

Read new Gmail messages from important contacts, extract action items, and update the relevant HubSpot contact record:

Agent: Check Gmail for emails from @domain.com → parse action items →
       update HubSpot contact with summary and next steps

Report Generation

Pull data from multiple sources into a Google Sheets report:

Agent: Get GitHub PR stats → get Jira closed tickets → get Slack channel metrics →
       write summary to Google Sheets → send Slack notification with link

Each of these services requires separate OAuth — but through the gateway, the agent doesn't need to manage any of it.

Comparison: api-gateway vs Individual API Skills

The individual skills (like byungkyu/gmail, byungkyu/github-api) give you more tailored commands for specific services — they're worth using if you work primarily with one API. The gateway is the right choice when you need multiple services in the same workflow.

Practical Tips

1. Authorize services before you need them — OAuth flows require browser interaction. Do the Maton connect setup for all the services you plan to use during initial setup, not mid-workflow.

2. Use for multi-service automation — The gateway's value compounds with every additional service. For single-service use, a dedicated skill is usually simpler.

3. MATON_API_KEY is not a secret per se — It authenticates with Maton but doesn't grant third-party access. Still keep it out of version control; treat it like any API key.

4. Check Maton's service list before planning — The 100+ number grows, but not every niche API is supported. Verify your target service is on the list before designing a workflow around the gateway.

5. JSON output for agent parsing — When calling APIs, request JSON responses for easier agent processing. The gateway passes through whatever format the target API returns.

Considerations

• Maton dependency — The skill is a proxy through Maton.ai. If Maton has downtime, the gateway is unavailable. This is the key tradeoff vs self-managed OAuth.
• Maton pricing — Maton operates as a commercial service. Check current pricing for your expected API call volume.
• Not for all APIs — Niche or internal APIs won't be in Maton's catalog. For those, you'll need direct integration.
• No server-side actions — The skill is a passthrough proxy, not an automation platform. Logic and orchestration still happen in your agent's workflow.
• Token refresh is automatic — Maton handles OAuth token refresh transparently, which is one of the bigger pain points in self-managed OAuth flows.

The Bigger Picture

The credential management problem is one of the most underrated obstacles to building useful AI agent workflows. Most tutorials for "connect your agent to Slack" skip over the 30 minutes of OAuth setup required to even get started.

api-gateway doesn't solve the underlying complexity — OAuth tokens still exist, third-party apps still need to be authorized. But it moves that complexity to a managed layer, so your agent can focus on the actual workflow logic rather than token refresh scheduling.

With 36,000+ downloads and 182 stars, it's clearly addressing a real friction point in how developers build agentic integrations.

View the skill on ClawHub: api-gateway