canonical: https://jentic.com/apis/fastn.ai/fastn # Fastn Send Notification API The Fastn Send Notification API lets AI agents push structured content through the Fastn integration platform to downstream systems. An agent submits events, topical reports, story references, or article lists, and Fastn routes that payload to connected CRM, messaging, productivity, and workflow platforms according to each platform's notification rules. It gives an agent one entry point to fan a single notification out to many enterprise destinations. Requests carry an API key. ## For AI agents Send structured notifications through Fastn to connected CRM, messaging, and workflow platforms. Authenticates with an API key. ## Scope Does not read back delivery status or manage the connected platforms themselves. Use for sending structured notifications only. ## Capabilities - Send a structured notification into Fastn-connected downstream platforms - Deliver signals, events, and topical reports to CRM and messaging tools - Route curated article and story references into productivity and workflow systems - Transmit structured metadata that Fastn distributes per each platform's rules ## Use cases ### Agent-Sent Notifications via Jentic AI agents send Fastn notifications through Jentic without holding the API key in context. An agent searches by intent, receives the send-notification schema, and submits a structured payload that Fastn fans out to connected platforms. Jentic injects the key at execution time, so the agent never sees the secret while it delivers content downstream. Example prompt: Search Jentic for 'send a Fastn notification', load the POST /sendNotification schema, and submit the payload with Jentic-managed credentials ### Fan-Out Content Distribution An agent packages an event or a curated article list once and sends it to Fastn, which distributes it to every connected destination such as a CRM, a chat tool, and a workflow system. The agent avoids integrating each platform directly, since Fastn handles routing and per-platform notification rules from a single call. Example prompt: Call POST /sendNotification with the structured content and let Fastn route it to the connected platforms ### Event-Driven Downstream Delivery When an upstream system produces a signal or report, an agent forwards it to Fastn as a structured notification so it reaches the right downstream tools. This turns raw events into delivered notifications without the agent knowing the details of each destination platform. Example prompt: Call POST /sendNotification whenever an upstream event fires, passing the event and its metadata for Fastn to deliver ## Key resources - **Notifications** — Send structured content that Fastn routes to connected downstream platforms ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 52 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 67 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 28 / 100 - Agent Usability: 94 / 100 - Security: 55 / 100 - AI Discoverability: 100 / 100 - **View full report:** https://jentic.com/apis/fastn.ai/fastn/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Fastn Send Notification API by hand means setting the x-fastn-api-key header and shaping the notification payload for Fastn's routing rules yourself. Through Jentic you install once, import the Fastn Send Notification API from the API Directory, store the key, and your agent calls it. - **Permission scoping:** This API exposes a single send-notification operation, so you decide whether your agent may call it, and Jentic runs only the operations you approve. Nothing else is reachable without your grant. - **Credential handling:** Your Fastn API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'send a notification', and Jentic returns the Fastn send-notification operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Slack** — Complementary chat platform as a notification destination - **SendGrid** — Complementary email delivery for outbound notifications - **Twilio** — Complementary SMS and voice delivery for notifications ## FAQ ### What authentication does the Fastn Send Notification API use? The Fastn Send Notification API authenticates requests with an API key sent in the `x-fastn-api-key` header, per its OpenAPI spec. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs. ### What can I do with the Fastn Send Notification API? You can send a structured notification with POST /sendNotification, transmitting events, topical reports, story references, or article lists that Fastn routes to your connected CRM, messaging, and workflow platforms. ### What are the rate limits for the Fastn Send Notification API? The OpenAPI spec does not specify rate limits; check the Fastn documentation for current limits. Through Jentic, requests run from your own instance, so you control the pacing of the agent's calls. ### How do I send a notification with the Fastn Send Notification API through Jentic? Search Jentic for 'send a Fastn notification', load the returned POST /sendNotification operation with its input schema, and your agent submits the payload with credentials injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Is there a Fastn MCP server? You don't need an MCP server to give your agent the Fastn Send Notification API. Jentic connects it directly from the API Directory: import it, store your key, and your agent calls it, discovering the operation on demand instead of loading a separate server's tool definitions into its context. ### Can I limit what my agent is allowed to do with the Fastn Send Notification API? Yes. This API exposes a single send-notification operation, so scoping is straightforward: you decide whether your agent may call it at all, and Jentic runs only the operations you approve. The agent cannot reach any operation you have not granted.