Skip to main content

​
What It Does

Your app talks to external services — Stripe for payments, Auth0 for authentication, SendGrid for emails, Twilio for SMS. These aren’t infrastructure you run. They’re third-party APIs your code depends on. Monk doesn’t just detect that you’re using Stripe. It provisions Stripe resources, injects credentials into your app, and updates webhook URLs when your deployment changes. You provide credentials once. Monk handles the rest.

​
How It Works

​
API Orchestration

Monk treats third-party APIs as first-class resources, same as containers and cloud infrastructure. Example: Auth0 Integration
  1. During code analysis, Monk detects Auth0 SDK usage
  2. You provide Auth0 management API credentials
  3. Monk provisions an Auth0 application for your deployment
  4. Monk obtains the client ID and secret, configures callback URLs (e.g., https://yourapp.com/auth/callback)
  5. Monk injects credentials into your app via Configuration & Wiring
  6. When you redeploy or move clouds, Monk updates callback URLs automatically
Your code just initiates Auth0 login. Monk handles the rest. Example: Stripe Integration
  1. Monk detects Stripe SDK usage in your code
  2. You provide Stripe API credentials
  3. Monk creates webhook endpoints pointing to your API, configures signing secrets
  4. Monk injects publishable and secret keys into frontend/backend
  5. When you scale or redeploy, Monk updates webhook URLs to match

​
Automatic Detection

During code analysis, Monk identifies your third-party API integrations — SDKs, API key references, webhook handlers, OAuth flows, and redirect URLs. It understands your API dependencies before you configure anything.

​
Unified System Map

Monk maintains a complete map of your system: your containers, cloud infrastructure, databases, essential services, and third-party API resources. It tracks the relationships between all of them. No more bouncing between the Stripe dashboard, Auth0 dashboard, AWS console, and DNS provider. It’s all in one place.

​
Dynamic Configuration Updates

When your deployment changes, API configurations need to follow. Monk handles this automatically — webhook URLs, OAuth callback URLs, CORS origins, API endpoint references, and signing secret rotation. Without Monk, a redeployment means logging into every provider dashboard and updating URLs by hand. With Monk, you deploy and everything stays in sync.

​
Authorization & Credentials

You provide API credentials for each service (API keys, OAuth tokens, management API access). Monk provisions resources, obtains necessary secrets, and updates configurations throughout the lifecycle.
Credentials are encrypted at rest in your IDE’s secret storage and on your Monk cluster using your cloud provider’s KMS. They are never sent to Monk servers and never exposed to the LLM. Monk needs these because it manages your accounts with third-party providers on your behalf (BYOI). See Security for details.

​
Supported Integrations

Monk supports several third-party API providers via integrations:
  • Identity & Authentication: Auth0, AWS Cognito, AWS IAM
  • Payments: Stripe (payment processing, subscriptions, webhooks)
Don’t see your API? Let us know. Any API with a management interface can potentially be orchestrated by Monk.

​
Next Steps

Configuration & Wiring

How Monk injects credentials and connects your services.

Integrations

Full list of supported APIs and providers.