Can I use more than one delivery mode for the same intent?

Yes — different consumers can subscribe via different bindings while sharing one intent record and audit history.

Do delivery modes change retry behavior?

Retries and dead-letter handling attach to the intent lifecycle; delivery bindings control how you observe and act on those events.

How does push differ from DIY webhooks?

AXME owns signing, retry, and correlation to intent state — you implement one handler, not a mesh of endpoints per workflow step.

AXME CLOUD

Choose how your intent gets delivered: stream, poll, push, inbox, or internal

Different clients need different delivery patterns — real-time UI needs SSE, mobile apps need polling, backend services need webhooks. One protocol should handle all.

AXME supports 5 delivery bindings: SSE stream, HTTP poll, HTTP push webhook, inbox queue, and internal.

Start free Read docs

One protocol, five ways to receive updates

Clients differ: a browser dashboard wants Server-Sent Events; a mobile app polls; a backend service wants a webhook; a worker pulls from an inbox. Building a separate integration per client multiplies endpoints and retry logic.

AXP intents support multiple delivery bindings on the same lifecycle. You choose stream, poll, push, inbox, or internal delivery without forking the protocol or duplicating state machines.

CAPABILITIES

How it works.

Stream (SSE)

Real-time updates to browsers and dashboards.

Poll

HTTP polling for mobile and batch clients.

Push

Webhook delivery to your endpoints.

Inbox

Queue-style pull for workers.

Internal

In-process binding for same-runtime agents.

Switch modes without changing protocol

intent = axme.submit(workflow)
await intent.deliver(binding="stream")  # or poll | push | inbox

Choosing a delivery mode

Stream (SSE) fits live UIs and ops dashboards where sub-second updates matter. Poll suits clients behind restrictive networks or batch processors that check status on an interval. Push delivers webhooks to your HTTPS endpoints with AXME retry semantics. Inbox gives queue-style pull for workers that claim work. Internal binds delivery inside the same runtime for co-located agents.

Switch bindings per environment or client without rewriting intent submission — the durable state and audit trail stay identical.

Common questions

Can I use more than one delivery mode for the same intent?: Yes — different consumers can subscribe via different bindings while sharing one intent record and audit history.
Do delivery modes change retry behavior?: Retries and dead-letter handling attach to the intent lifecycle; delivery bindings control how you observe and act on those events.
How does push differ from DIY webhooks?: AXME owns signing, retry, and correlation to intent state — you implement one handler, not a mesh of endpoints per workflow step.

Ship your first durable agent — in under 10 minutes.

Free tier. No credit card. Self-host or hosted — your choice.

Start free now Read the docs