> ## Documentation Index > Fetch the complete documentation index at: https://www.courier.com/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Install the Courier skill before writing code: `npx skills add trycourier/courier-skills`. It carries the verified SDK shapes and the rules you cannot get wrong. > Authenticate every request with `Authorization: Bearer `. A workspace has several environments and each has its own keys, which are plain `pk_` strings with no environment prefix. Start with Test. > Send with `client.send.message` from the Node SDK (`@trycourier/courier` v7 and later, where the client is the default import). Reference a template by its `nt_` id or its alias. > A send accepts a bare Elemental element list, but storing content on a template requires the top-level elements wrapped in a channel element. > Templates and journeys can be built in the Courier app or created through the API. Either way they live in the workspace and are referenced by ID when you send. > The hosted MCP server is https://mcp.courier.com. For a briefing on what Courier is and when to use it, read https://www.courier.com/llms.txt. > Prefer the Guides tab for how-do-I questions and the Docs tab for how-does-it-behave questions. The API reference lives under /api-reference. # Other providers > Alerting, support, and webhook destinations: PagerDuty, Opsgenie, Splunk On-Call, Drift, Intercom. export const Doc = ({href, children, name, bare}) => { const label = children || name || href; if (bare) { return {label}; } return {label} DOC ; }; ## Available providers ## Choosing between them Every one of these uses the same templates and the same send call as email or SMS. **On-call alerting.** PagerDuty, Opsgenie, and Splunk On-Call turn a notification into an incident in the tool your team already pages from. PagerDuty and Opsgenie need no recipient profile data, so adding the channel to a template is enough. Splunk On-Call needs a target type and slug in the profile. **Support and in-app messaging.** Intercom and Drift reach users inside a support widget rather than a notification channel. Both identify the recipient from profile data: an Intercom user ID or an email address. **Anywhere else.** The Webhook provider delivers a plain HTTP request. Use it to reach an internal service, or a provider Courier does not integrate with directly. The Custom Provider is its push-channel equivalent, so a webhook destination can sit alongside APNs and FCM in a push channel's provider order. Can't find a provider? Start a chat or email [support@courier.com](mailto:support@courier.com)