api-gateway

Connect external APIs through a centralized OAuth-driven gateway.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/Kushtrvedi/openclaw-standard --skill api-gateway-kushtrvedi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-gateway
Source: https://github.com/Kushtrvedi/openclaw-standard/tree/main/skills/api-gateway
Command: npx skills add https://github.com/Kushtrvedi/openclaw-standard --skill api-gateway-kushtrvedi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Connects to external APIs securely through a centralized gateway that abstracts OAuth and token handling, reducing integration complexity and risk.

Core Features & Use Cases

  • Unified API access: call Google, GitHub, Slack, Notion, HubSpot, and more via a single proxy with managed OAuth connections.
  • Security & compliance: enforces per-service OAuth flows, explicit user authorization, and scoped access control to protect credentials.
  • Reliability & automation: includes deterministic startup/repair flow and script-driven tasks for self-healing and predictable deployments.

Quick Start

Authenticate once, then invoke the gateway to proxy a protected API call and verify OAuth routing.

Frequently Asked Questions about api-gateway

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage OAuth tokens for multiple external APIs without hardcoding credentials?

Managed OAuth handles token lifecycle for external APIs by abstracting authorization into a centralized gateway. Users authenticate once per service, and the gateway enforces scoped access control to protect credentials.

Can I automate Google Workspace, GitHub, and Slack API calls through a single proxy?

Yes, a single proxy routes automated API calls to Google Workspace, GitHub, and Slack. It enforces deterministic script-driven tasks for repeatable automation across 100+ supported services via Maton.

What's the best way to route protected API requests for repeatable automation workflows?

The best way to route protected API requests is through a centralized OAuth-driven gateway. It provides deterministic startup and repair flows, ensuring self-healing and predictable deployments for script-driven automation tasks.

Does this API gateway proxy support scoped access control for third-party integrations?

Yes, the API gateway proxy supports scoped access control for third-party integrations. It enforces per-service OAuth flows and requires explicit user authorization to ensure secure, compliant connections to external APIs.

Why use a centralized gateway instead of direct OAuth integration for external services?

A centralized gateway reduces integration complexity and risk by abstracting token management. Direct OAuth integration requires handling per-service authorization flows independently, whereas the gateway unifies access and enforces scoped security.

How do I connect Notion and HubSpot APIs with explicit user consent for automation?

To connect Notion and HubSpot APIs with user consent, authenticate through the gateway's per-service OAuth flows. It ensures explicit user authorization and scoped access before proxying any protected automation calls.