docs(integrations): Vercel Marketplace page with OIDC resource tokens - #252
Merged
Merged
Conversation
…e tokens Installing from the Marketplace, the two credentials a Vercel project can use (short-lived OIDC resource tokens minted from the deployment's VERCEL_OIDC_TOKEN, and the provisioned AGENTMAIL_API_KEY), the mint snippet for both SDKs using their token-supplier option, and troubleshooting for the token flow.
sidharth0612
approved these changes
Sep 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
integrations/vercel: the Vercel Marketplace integration had no docs page, and the new OIDC resource-token flow (live in production as of agentmail-api #1310) had no customer-facing instructions anywhere.Page contents
vercel integration add agentmail, one resource = one organization,vercel env pull.AGENTMAIL_RESOURCE_ID= the Vercelir_id, mint + pass as the API key), and a troubleshooting table.AGENTMAIL_API_KEY: unchanged path, with the Production-only recommendation.Snippets
Both SDKs accept a function as the API key (Node
apiKey?: Supplier<string>resolved per request inBearerAuthProvider; Pythonapi_key: str | Callable[[], str]), so the examples pass a minting function that caches the token until a minute before expiry. The TypeScript flow is the same one verified end to end against production from a Vercel function on our own team (mint →GET /v0/inboxes→ 200).The Python inbox-create example uses
create(request=CreateInboxRequest(...)), which is the signature of the released SDK (0.4.15). Several existing pages (integrate-livekit-agents,custom-domains) use keyword arguments that this signature does not accept; left for a separate fix.fern check: 0 errors.