OAuth Ready: will this integration take an hour, or eight weeks of review?
Before your agent can act for users in another app, you need a provider OAuth app, and sometimes the provider has to approve it. Look up an app to see the gate, the wait, what an agent can do for you, and where you take over.
Five apps, five kinds of gate
GitHubNo approval gate. Register in about 10 minutes and any GitHub user can connect right away. The real decision is OAuth app vs GitHub App.
NotionCreate a public connection and OAuth works for any workspace. Marketplace listing needs a security review. The real surprise: your agent only sees pages users pick at consent.
SlackBuild and install in under an hour. Selling to other companies means Marketplace approval, which requires 10 active workspaces before you can even submit and up to ~10 weeks of review. Unlisted apps get 1 req/min on message history.
LinkedInSign-in and posting as a member are instant. Anything with company pages, ads or analytics requires LinkedIn to vet your business, and a rejection means starting over with a new app.
Gmail (Google)Working in an hour for up to 100 test users. Reading mail in production needs restricted-scope verification plus an annual third-party security assessment (CASA). Plan for weeks and start early.
Investigated live
Amazon Payments (Login with Amazon / Amazon Pay)Login with Amazon OAuth is live and self-serve (security profile + privacy URL, ~20–30 min); Amazon Pay money movement is a separate merchant onboarding gate not detailed in these sources.
Apple PayApple Pay has no third-party OAuth, so agents cannot get delegated payment authority; merchant integration instead needs the $99/yr Apple Developer Program, a Merchant ID, certificates/domain verification, and user Face ID/Touch ID at checkout, plus App Review for public apps.
AsanaOAuth is self-serve: create an app in the developer console, register scopes, and run the authorization-code flow in an afternoon. The one real gate is Manage distribution — leave 'Specific workspaces' empty and every user hits 'This app is not available to your Asana workspace'.
BoxOAuth 2.0 is self-serve in your own developer account (under ~90 minutes), but reaching other enterprises' users is gated by a Box Admin authorizing your Client ID in Platform Apps Manager — and on-request scopes (legal holds, GCM) need a support ticket on a paid enterprise plan.
OAuth 2.0 is self-serve: create an app under Settings → Developer and it works unverified immediately — only the trust badge/directory listing needs review (3–5 business days). The real gate is identity: cashless.co publishes no OAuth metadata (both .well-known paths return HTML), while the live /oauth/authorize endpoint and all OAuth docs sit on app.cashpanel.io.
A real OAuth 2.0 authorization server is live at api.dashx.com with six scopes, but there is no registration endpoint and no docs, so the gate is a manual client_id request plus an unknown review wait — and there is no OIDC and no payments scope.
EthereumThere is no Ethereum OAuth app registration to wait on — users sign an EIP-4361 (SIWE) message with their own wallet and you verify it server-side in roughly an afternoon. If your stack insists on OAuth-shaped tokens, a third-party bridge (oidc.login.xyz) mints a client_id and secret from one curl, still with no review.
Google PayNo OAuth to authorize Google Pay: it is a merchant-side API where the payment sheet returns a gateway token, and going live needs a Google Pay & Wallet Console business profile plus manual website review (AI screenshot pre-check, then human; duration undocumented).
IntercomThird-party OAuth exists and is self-serve for your own workspace, but any app reaching other customers' Intercom data — even unlisted — must pass Intercom review (7–14 days per docs, up to 7 business days per the console) with a recorded install/uninstall video and scope-by-scope justification.
No OAuth surface at all: all six OIDC/OAuth discovery probes on developer., auth. and api.navi.com failed, so there is nothing self-serve to build against; delegated UPI access realistically requires a PSP-bank + NPCI partner track — months, discretionary (inferred, no Navi source found).
PaytmPaytm has no self-serve 'Sign in with Paytm' OAuth — user login exists only inside the Mini App platform (business KYC + partner approval), and the documented 'OAuth Token API' is a merchant server token, not user delegation.
PayUPayU has OAuth only for merchant server-to-server calls (client_credentials) — no consent screen, no third-party app registration, no scopes — so 'act for your user' needs PayU's partner program (business vetting, weeks), and getting even the merchant credentials means company KYC and a signed contract.
PhonePeNo user-delegated OAuth: the only published flow is a merchant client_credentials token (self-serve once your Business account and V2 keys exist), while acting for PhonePe users means Switch partner onboarding plus app review, with no published timeline.
PinterestOAuth 2 authorization-code is real (authorize at https://www.pinterest.com/oauth/, token at POST /v5/oauth/token), but you get no app secret until Pinterest manually approves your Trial request, and shipping to other users needs a second, video-gated Standard review. No OIDC discovery exists, so endpoints are hand-configured.
SalesforceOAuth works self-serve in minutes via an External Client App in Setup — Connected Apps now need a Salesforce Support ticket to re-enable creation — but there is no global app registration, so every customer org's admin must install and pre-authorize your app before the agent can act for their users.
Self-serve OAuth: register an app in Calendly's Developer tools in minutes with no review gate, but PKCE S256 is mandatory, each app gets exactly one redirect URI, and Production requires HTTPS.
SolanaSolana runs no OAuth provider for third-party apps — you borrow OAuth from Phantom's embedded wallet (Google/Apple, needs a Phantom Portal App ID that may be paused) and public distribution then costs Solana dApp Store KYC/KYB plus ~3–4 business days of app review.
StripeStripe's OAuth is Connect account-linking for Standard accounts, not a "Sign in with Stripe": there is no discovery document (both well-knowns 404 or return the SPA's HTML), so you hardcode https://connect.stripe.com/oauth/authorize, and your only scopes are read_write for everyone or read_only for Extensions only.
ZoomWorks in your own Zoom account in about an hour - General app, redirect URL, allow list, code exchange - but installing for anyone outside your account means Marketplace review with an OWASP-facing security audit and scope-by-scope least-privilege justification.
An hour, or eight weeks?
- Calendlyagent45 min – 1.9 h
- Ethereumagent3.3 h – 9 h
- GitHub1.1 h – 3 days
- Stripeagent1 day – 3 days
- Salesforceagent1 day – 5 days
- Cashlessagent5 days – 8 days
- Google Payagent2 days – 8 days
- Solanaagent4 days – 9 days
- Intercomagent8 days – 2 weeks
- Apple Payagent8 days – 2 weeks
- Amazon Payments (Login with Amazon / Amazon Pay)agent3 days – 3 weeks
- Notion7 days – 4 weeks
- Asanaagent2.3 h – 4 weeks
- Boxagent2 weeks – 4 weeks
- Paytmagent8 days – 5 weeks
- DashX Paymentsagent9 days – 5 weeks
- Pinterestagent8 days – 5 weeks
- Zoomagent2 weeks – 6 weeks
- PayUagent9 days – 7 weeks
- PhonePeagent2 weeks – 10 weeks
- Gmail (Google)2 weeks – 13 weeks
- LinkedIn4 weeks – 13 weeks
- Slack5 weeks – 20 weeks
- Navi (UPI, India)agent8 weeks – 24 weeks