
Api Gateway
Route agent requests to third-party apps (Slack, etc.) through Maton’s managed API gateway after the user specifies app, account, and task.
Overview
API Gateway is an agent skill for the Build phase that connects agents to third-party apps via Maton-managed routes after the user defines app, account, and task.
Install
npx skills add https://github.com/maton-ai/api-gateway-skill --skill api-gatewayWhat is this skill?
- Maton CLI and REST entrypoints at https://api.maton.ai/ with app-prefixed paths
- Protocol: user must name exact app, account, and task before any call
- Read-only GET calls first to verify account and resource IDs
- Non-GET requests gated behind documented safety steps in app references
- Python and curl examples using MATON_API_KEY Bearer auth
- Skill metadata version 1.0
Adoption & trust: 1.2k installs on skills.sh; 28 GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent needs to hit Slack or other SaaS APIs but you lack a consistent, authenticated routing layer and safe exploration protocol.
Who is it for?
Solo builders with a Maton account who want one gateway pattern for agent-driven SaaS automation.
Skip if: Greenfield projects with no named third-party app, or integrations that must bypass Maton entirely.
When should I use this skill?
Use only after the user names the target app, account, and task; start with read/list when possible.
What do I get? / Deliverables
You run verified read/list calls through Maton’s gateway, then proceed to change operations only per app-specific reference guidance.
- Successful GET/list responses and agent-guided follow-up API actions per app docs
Recommended Skills
Journey fit
How it compares
Managed Maton routing skill—not a self-hosted API proxy or generic REST tutorial.
Common Questions / FAQ
Who is api-gateway for?
Indie developers and agent users on Maton who need repeatable, authenticated calls into supported external apps from the terminal or agent.
When should I use api-gateway?
In Build integrations when the user has named the app and task; use GET/list first, then writes per the app reference.
Is api-gateway safe to install?
Review Security Audits on this page; the skill requires network and API keys—never run destructive calls without confirming account and IDs via read calls.
SKILL.md
READMESKILL.md - Api Gateway
# API Gateway Managed API routing for third-party services, provided by [Maton](https://maton.ai). Use this only for a user-requested app, account, and task. ## Quick Start **CLI:** ```bash maton slack channel list --types public_channel --limit 10 ``` ```bash maton api '/slack/api/conversations.list?types=public_channel&limit=10' ``` **Python:** ```bash python <<'EOF' import urllib.request, os, json req = urllib.request.Request('https://api.maton.ai/slack/api/conversations.list?types=public_channel&limit=10') req.add_header('Authorization', f'Bearer {os.environ["MATON_API_KEY"]}') print(json.dumps(json.load(urllib.request.urlopen(req)), indent=2)) EOF ``` ## Routing Use `https://api.maton.ai/` with the app-prefixed routes documented in the examples below or in the matching reference file. **Usage protocol:** 1. Only invoke after the user specifies the exact app, account, and task. 2. Always start with read-only (GET) calls to verify the target account, resource identifiers, and current state. 3. **All non-GET requests are denied unless the user explicitly approves each one.** Before any POST, PUT, PATCH, or DELETE call, present the user with: the exact connection ID, the full endpoint path, the request body, and the expected outcome — then wait for approval. 4. If the user's request implies a non-GET operation, first show them what you intend to call and ask for confirmation. Do not infer approval from the original request. Read-only route examples: ```text https://api.maton.ai/slack/api/conversations.list?types=public_channel&limit=10 https://api.maton.ai/google-mail/gmail/v1/users/me/messages ``` The first path segment is the app identifier listed in Supported Services. For Gmail, use `/google-mail/gmail/v1/users/me/messages`. ## Installation **NPM:** ```bash npm install -g @maton-ai/cli ``` **Homebrew:** ```bash brew install maton-ai/cli/maton ``` ## Authentication **IMPORTANT — Credential Safety:** - Treat `MATON_API_KEY` as a secret. Never log it, echo it, paste it into prompts, or expose it in shared files, command output, or tool results. - **Connection creation requires explicit user approval.** Before creating any connection, ask the user to confirm the specific service and confirm they intend to authorize access. Never create connections on the agent's own initiative. - **Least-privilege scopes:** When a service offers scope selection during OAuth, select only the scopes the current task requires. Do not accept broader scopes for convenience. - Remove connections immediately after the task is complete if they are no longer needed (`maton connection delete {id}`). - If the key may have been exposed (logs, screenshots, shared terminals), rotate it immediately at [maton.ai/settings](https://maton.ai/settings). - Never share the key across users, workflows, or environments that do not require it. **CLI:** ```bash maton login # Opens browser for API key maton login --interactive # Skip browser, paste API key directly maton whoami # Show current auth state ``` **Manual:** 1. Sign in or create an account at [maton.ai](https://maton.ai) 2. Go to [maton.ai/settings](https://maton.ai/settings) 3. Click the copy button on the right side of API Key section to copy it 4. Set your API key as `MATON_API_KEY`: ```bash export MATON_API_KEY="YOUR_API_KEY" ``` ## Connection Management Connection management uses a separate base URL: `https://api.maton.ai` ### List Connections **CLI:** ```bash maton connectio