API Gateway Integration Routing

Problem

In agent workflows, teams often need to operate across multiple third-party APIs: listing Slack channels, reading Gmail, or querying Stripe customers. Each integration brings its own auth state, connection management, event listening, and write-side risk. Manually managing connections and token state is easy to botch, while silent write operations can cause irreversible side effects.

How It Works And Where It Stops

This skill routes those calls through a hosted gateway at https://api.maton.ai/, giving one entry point for apps such as Slack, Gmail, and Stripe. Key capabilities include:

• Connection management: create, list, fetch, and delete connections, with --connection used to target a specific account.
• Read-first flow: run GET first to verify account, resource, and state before proposing changes.
• Write approval: before POST, PUT, PATCH, or DELETE, show the connection ID, endpoint, request body, and expected result, then wait for explicit approval.
• Triggers and checkpoints: listen for events and replay them; after interruption, resume from the last processed event to avoid duplicate side effects.
• Multiple call styles: maton CLI, JavaScript fetch, and Python requests are supported.

A practical flow starts with auth verification, then lists connections and runs read-only checks. For high-risk actions such as sending messages, deleting records, changing billing, or creating Webhook flows, confirm external impact step by step. It does not replace private API proxies, OAuth server deployment, or API key distribution, requires MATON_API_KEY, and is subject to account rate limits.