GenieOS · Integrations

Works with the stack you already run.

GenieOS is not a rip and replace. It works with the delivery providers and lifecycle platforms you have, and gives your agents one surface across all of them. The call your code makes never names the provider, which means the day you migrate is the day nothing in your codebase changes.

agent.tsts
// the provider is a setting, not a parametersend_transactional({  template: "directory-launch",  to: "[email protected]",  variables: { first_name: "Alex" },})// routes through the delivery provider this// workspace connected. swap it later; this// call does not change
The surface
  • send_transactionalOne branded send through whichever delivery provider the workspace connected.
  • send_testProve the template renders and delivers through your provider before anything real ships.
  • read_sendDelivery state and events for one send, as data.
  • list_social_networksWhich networks this workspace can publish to, and the state of each.
  • refresh_social_networksRe-sync network state when something changes on the other side.
  • create_webhookPush deliveries, identified links and loop events to any endpoint you run.
  • list_webhooksWhat is already wired, so your agent checks before it adds.
IntegrationsFueld

Marketing & lifecycle platforms

— Keep your CDP, replace the editor

IterableNOT CONNECTED

Your CDP-grade lifecycle platform — we push templates, you keep the profile.

Targeted sendEvent streamUnsubscribe push
LiveBYONo sandbox
KlaviyoNOT CONNECTED

Commerce-native lifecycle for Shopify-and-friends storefronts.

Flow triggerEvent streamUnsubscribe push
LiveBYOFlow-driven
Mailchimp TransactionalNOT CONNECTED

Mailchimp's transactional API (formerly Mandrill) — render & send.

Outbound sendActivity webhooksSuppression push
LiveMandrill APIBYO
Customer.ioNOT CONNECTED

Workflow-first lifecycle for product-led B2C and B2B teams.

Outbound sendReporting webhooksSuppression push
LiveUS + EU regionsBYO
BrazeNOT CONNECTED

Enterprise multi-channel engagement — email is one of many lanes.

Outbound sendCurrents eventsSubscription push
LiveEnterpriseRegional REST
ActiveCampaignNOT CONNECTED

SMB marketing automation with a heavy email habit.

Event triggerEvent hooksUnsubscribe push
LiveBYOEvent-driven
The lifecycle shelf: Live and BYO, a capability claim rather than a wizard.

Works with

  • Klaviyo
  • Customer.io
  • Braze
  • Iterable
  • Mailchimp
  • ActiveCampaign
  • Segment
  • HubSpot

Keep your CDP. Replace the editor.

That line is the product's own. It is printed on the integrations shelf in the app, and it is the honest shape of the relationship: the platforms on this shelf keep the profile store and the workflows you have already built, and GenieOS becomes the place the artefacts are made. The editor, the brand memory, and the loop that decides what to make next.

Works with, not instead of. Your agents compose and render in GenieOS, the finished template is pushed to the platform you keep, and the events stream back so the loop can learn from what happened.

IntegrationsFueld

Transactional ESPs

— Bring your own delivery API

MailerSendNOT CONNECTED

Transactional + marketing send, with deliverability built in.

Outbound sendActivity webhooksSuppressions
RecommendedLiveEU region
SMTP relayNOT CONNECTED

Generic SMTP for self-hosted or legacy mail infrastructure.

Outbound send
Live
PostmarkNOT CONNECTED

Lightning-fast transactional delivery with great inbox placement.

Outbound sendActivity webhooksSuppression sync
Live
ResendNOT CONNECTED

Developer-first email API. Modern SDKs, React Email native.

Outbound sendActivity webhooks
Live
SendGridNOT CONNECTED

Enterprise-scale delivery with regional sending pools.

Outbound sendEvent webhooksSuppression sync
Live
MailgunNOT CONNECTED

Reliable transactional + marketing send with strong analytics.

Outbound sendActivity webhooksSuppressions
LiveUS + EU regions
The transactional shelf: connect the delivery API you already run.

Delivery providers

  • Postmark
  • Resend
  • Mailgun
  • MailerSend
  • SendGrid

Bring your own delivery.

Delivery is bring your own. Connect the transactional provider you already trust and every send routes through it: same call, same template, same deterministic brand checks. GenieOS carries the memory and the rendering, your provider carries the mail, and suppressions and activity webhooks stay in sync between them.

Switching providers later is a settings change, not a rewrite. The tool surface your agents call never mentions the provider at all, so the migration your future self dreads is one afternoon and zero diffs.

Two minutes in a browser, once.

You cannot OAuth from a terminal. Two minutes in a browser, once, and everything after it is a call.

That is the entire manual surface of this page. Social networks are the same shape: authorise the accounts once in the workspace, then your agents list the connected networks, publish to them, and read the analytics back without leaving the codebase. If a token expires or a network wobbles, one refresh call reports the new state instead of a silent failure.

hooks.tsts
// once, from wherever your agents livecreate_webhook({  url: "https://api.fueld.ai/hooks/genieos",  events: [    "send.delivered",    "link.identified",    "kpi.progress",  ],})

Everything it learns comes back as data.

Integration is a two way claim, and the second direction is the one the loop depends on. Deliveries, opens, clicks and conversions come back as webhooks and as tool results, so the numbers land where your agents already are, in the same session that shipped the send.

Link analytics carries the attribution primitive underneath it: a link sent to a known contact comes back IDENTIFIED, tying the result to a person, a campaign and the artefact that produced it. What your stack ships, GenieOS can measure. What GenieOS measures, your stack can hear.

Prefer to click? The same thing, in the app.Integrations for marketers

Keep the stack. Gain the loop.

Join the Beta Connect over MCP